This patch series ultimately adds watchdog support for tegra30 and later chips. The existing tegra clocksource driver (drivers/clocksource/tegra20_timer.c) sadly does not distinguish between tegra20 and tegra30 (and later), which it should have done since the contents of the timer register base have changed significantly. In particular, tegra30 (and later) has more timers, and also hardware watchdog registers. The first patch adds nvidia,tegra30-timer to the list of compatibilty strings for the tegra timer device tree node, so that we can distinguish between tegra20 and tegra30 (and later). The second patch separates out some macros that are interesting to other drivers (in particular, the tegra watchdog driver), and also adds the the missing timers that are present in tegra30 and later. The third patch adds the actual watchdog driver. This driver configures a single watchdog (watchdog 0), pairs it with timer 5 (defined as TEGRA30_TIMER_WDT_* in the shared header file from the previous patch), and sets it up so that upon timer expiration, will cause the target system to reset. I've decided to encapsulate all related changes into one patch series, since I did not modify any device tree bindings and therefore don't need to review dt changes separately. This way, everything can be seen within its complete context. Andrew Chew (3): clocksource: tegra: Add nvidia,tegra30-timer compat clocksource: tegra: Define timer bases in header file watchdog: Add tegra watchdog Documentation/watchdog/watchdog-parameters.txt | 5 + drivers/clocksource/tegra20_timer.c | 16 +- drivers/watchdog/Kconfig | 11 + drivers/watchdog/Makefile | 1 + drivers/watchdog/tegra_wdt.c | 372 +++++++++++++++++++++++++ include/clocksource/tegra_timer.h | 43 +++ 6 files changed, 439 insertions(+), 9 deletions(-) create mode 100644 drivers/watchdog/tegra_wdt.c create mode 100644 include/clocksource/tegra_timer.h -- 1.8.1.5 -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
