Introduce a new user of the watchdog framework. This is a rewritten driver for STMP and imx23/28: Quoting Patch 2/3 for the motivation of a rewrite: === Replace the existing STMP3xxx driver because it has enough drawbacks that a rewrite is apropriate. The new driver is designed to use the watchdog framework which makes it a lot smaller. It now uses an exported function from the RTC driver to set up its registers (the old driver silently reused the hopefully already remapped RTC registers). Also, this driver is mach independent, while the old one still depends on a removed mach. === The first patch adds an accessor routine to the RTC-driver which can hopefully go via the watchdog-tree as well (asking for Andrew's ack here). The second patch adds the new driver, the third removes the old one. After missing the last merge window, I really hope we can get it into 3.4. The old driver was broken (= not compilable) anyhow, so there cannot be any regression. Tested on a MX28EVK. Regards, Wolfram Changes since V1: * don't use EXPORT_SYMBOL for the callback into the RTC anymore. Now, the callback is provided via platform_data to make sure it is private between RTC and watchdog. * use more helpers to reduce driver size (module_platform_driver, pm_ops) Wolfram Sang (3): rtc: stmp3xxx: add wdt-accessor function watchdog: add new driver for STMP3xxx and i.MX23/28 watchdog: remove old STMP3XXX driver drivers/rtc/rtc-stmp3xxx.c | 64 ++++++++ drivers/watchdog/Kconfig | 13 +- drivers/watchdog/Makefile | 2 +- drivers/watchdog/stmp3xxx_rtc_wdt.c | 139 +++++++++++++++++ drivers/watchdog/stmp3xxx_wdt.c | 286 ----------------------------------- include/linux/stmp3xxx_rtc_wdt.h | 15 ++ 6 files changed, 226 insertions(+), 293 deletions(-) create mode 100644 drivers/watchdog/stmp3xxx_rtc_wdt.c delete mode 100644 drivers/watchdog/stmp3xxx_wdt.c create mode 100644 include/linux/stmp3xxx_rtc_wdt.h -- 1.7.2.5 -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html