On Oct 30, 2013, at 2:01 AM, Leela Krishna Amudala wrote: > The syscon regmap interface is used to configure AUTOMATIC_WDT_RESET_DISABLE > and MASK_WDT_RESET_REQUEST registers of PMU to mask/unmask enable/disable of > watchdog in probe and s2r scenarios. > > Signed-off-by: Leela Krishna Amudala <l.krishna@xxxxxxxxxxx> > --- > .../devicetree/bindings/watchdog/samsung-wdt.txt | 13 ++- > drivers/watchdog/s3c2410_wdt.c | 114 ++++++++++++++++++-- > 2 files changed, 118 insertions(+), 9 deletions(-) > > diff --git a/Documentation/devicetree/bindings/watchdog/samsung-wdt.txt b/Documentation/devicetree/bindings/watchdog/samsung-wdt.txt > index 2aa486c..c46c7ce 100644 > --- a/Documentation/devicetree/bindings/watchdog/samsung-wdt.txt > +++ b/Documentation/devicetree/bindings/watchdog/samsung-wdt.txt > @@ -5,10 +5,21 @@ after a preset amount of time during which the WDT reset event has not > occurred. > > Required properties: > -- compatible : should be "samsung,s3c2410-wdt" > +- compatible : should be "samsung,s3c2410-wdt" or "samsung,s3c5250-wdt" or "samsung,s3c5420-wdt" > - reg : base physical address of the controller and length of memory mapped > region. > - interrupts : interrupt number to the cpu. > +- samsung,pmusysreg : reference node to pmu sysreg (required only in case of Exynos5250 and 5420) Rather than saying required only on Exynos5250 and 5420, how about saying required only in case of compatible being "samsung,s3c5250-wdt" or "samsung,s3c5420-wdt" > > Optional properties: > - timeout-sec : contains the watchdog timeout in seconds. > + > +watchdog@101D0000 { > + compatible = "samsung,s3c5250-wdt"; > + reg = <0x101D0000 0x100>; > + interrupts = <0 42 0>; > + clocks = <&clock 336>; > + clock-names = "watchdog"; > + samsung,sysreg = <&pmu_sys_reg>; > + status = "okay"; > +}; -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html