[PATCH v2 0/6] Update Davinci watchdog driver
From: Ivan Khoronzhuk
Date: Mon Nov 18 2013 - 12:20:45 EST
These patches are intended to update Davinci watchdog to use WDT core
and reuse driver for keystone arch, because Keystone uses the similar
IP like Davinci.
See Documentation:
Davinci DM646x - http://www.ti.com/lit/ug/spruer5b/spruer5b.pdf
Keystone - http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
Also:
- improved to support GET_TIMELEFT option.
- added "clocks" and "timeout-sec" properties to DT.
Based on
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
keystone/master
v1..v2:
- watchdog: davinci: change driver to use WDT core
corrected 2011 -> 2006-2013
removed useless function comment
corrected initialization of heartbeat
switched on CONFIG_WATCHDOG_NOWAYOUT option
- watchdog: davinci: use davinci_wdt_device structure to hold device data
substituted wdd to watchdog device in commit message
- watchdog: davinci: add GET_TIMELEFT option support
corrected comment (is -> has)
removed redundant error message "clock freq is not set"
- watchdog: davinci: add GET_STATUS option support
dropped
- watchdog: davinci: add "timeout-sec" property
use consistent formatting
- watchdog: davinci: reuse driver for keystone arch
use consistent formatting
- watchdog: davinci: add "clocks" property
merged with above patch
Ivan Khoronzhuk (6):
watchdog: davinci: change driver to use WDT core
watchdog: davinci: use davinci_wdt_device structure to hold device
data
watchdog: davinci: add GET_TIMELEFT option support
watchdog: davinci: add "timeout-sec" property
watchdog: davinci: reuse driver for keystone arch
arm: dts: keystone: add watchdog entry
.../devicetree/bindings/watchdog/davinci-wdt.txt | 15 +-
arch/arm/boot/dts/keystone.dts | 6 +
drivers/watchdog/Kconfig | 6 +-
drivers/watchdog/davinci_wdt.c | 227 +++++++++-----------
4 files changed, 122 insertions(+), 132 deletions(-)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/