Re: [PATCH] Add support for always enabled watchdog timers

[Guenter Roeck]

On 08/23/2014 10:25 AM, Alexander Shiyan wrote:
> Sat, 23 Aug 2014 10:16:08 -0700 ÐÑ Guenter Roeck <linux@xxxxxxxxxxxx>:
> > On 08/16/2014 05:45 PM, Evgeny Boger wrote:
> > > From: Evgeny Boger <boger@xxxxxxxxxxxxxx>
> > >
> > > Add option to use with watchdog timers which are always enabled
> > > in hardware, i.e. there is no way to enable/disable it via GPIO pin.
> > > The driver will start pinging WDT immediately upon loading
> > > and will continue to do so even after stopping the watchdog.
> > The headline needs a reference to the affected driver.
> >
> > Also, please copy the dt mailing list and maintainers.
> >
> > > Signed-off-by: Evgeny Boger <boger@xxxxxxxxxxxxxx>
> > > ---
> > >    .../devicetree/bindings/watchdog/gpio-wdt.txt      | 14 ++++++-
> > >    drivers/watchdog/gpio_wdt.c                        | 45 +++++++++++++++++-----
> > >    2 files changed, 48 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt b/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
> > > index 37afec1..1f8ca46 100644
> > > --- a/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
> > > +++ b/Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
> > > @@ -12,8 +12,11 @@ Required Properties:
> > >        the opposite level disables the WDT. Active level is determined
> > >        by the GPIO flags.
> > >    - hw_margin_ms: Maximum time to reset watchdog circuit (milliseconds).
> > > +- always-enabled: Use with wathdog timer which is always enabled
>
> Similar to NOWAYOUT?
I think this one is different. NOWAYOUT is a software flag, while
the flag here is supposed to mean that the hardware watchdog
is always enabled and running, and can not be disabled. Or at least
this is my understanding.

Guenter

--
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/