Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-08-01 Thread Wim Van Sebroeck
Hi All, > On 07/27/2016 01:17 PM, Rasmus Villemoes wrote: > >On 2016-07-21 02:31, Guenter Roeck wrote: > >>On Thu, Jul 21, 2016 at 12:08:52AM +0200, Rasmus Villemoes wrote: > >> > >>I hear you. "configure hardware" is a slippery term, though. After all, > >>one would typically configure the initia

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-31 Thread Guenter Roeck
On 07/27/2016 01:17 PM, Rasmus Villemoes wrote: On 2016-07-21 02:31, Guenter Roeck wrote: On Thu, Jul 21, 2016 at 12:08:52AM +0200, Rasmus Villemoes wrote: I hear you. "configure hardware" is a slippery term, though. After all, one would typically configure the initial timeout in hardware, just

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-27 Thread Rasmus Villemoes
On 2016-07-21 02:31, Guenter Roeck wrote: On Thu, Jul 21, 2016 at 12:08:52AM +0200, Rasmus Villemoes wrote: I hear you. "configure hardware" is a slippery term, though. After all, one would typically configure the initial timeout in hardware, just as any "normal" timeout. In many cases, this wil

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-20 Thread Guenter Roeck
On Thu, Jul 21, 2016 at 12:08:52AM +0200, Rasmus Villemoes wrote: > On 2016-07-15 16:29, Guenter Roeck wrote: > >On 07/15/2016 12:32 AM, Rasmus Villemoes wrote: > > > >>>The initial timeout should be specified as module option or as > >>>devicetree parameter, and there should be no additional confi

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-20 Thread Rasmus Villemoes
On 2016-07-15 16:29, Guenter Roeck wrote: On 07/15/2016 12:32 AM, Rasmus Villemoes wrote: The initial timeout should be specified as module option or as devicetree parameter, and there should be no additional configuration option. I was under the impression that device tree was exclusively fo

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-15 Thread Guenter Roeck
On 07/15/2016 12:32 AM, Rasmus Villemoes wrote: On 2016-07-14 16:42, Guenter Roeck wrote: On 07/14/2016 02:16 AM, Rasmus Villemoes wrote: +config WATCHDOG_OPEN_DEADLINE +bool "Allow deadline for opening watchdog device" +help + If a watchdog driver indicates that to the framework

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-15 Thread Rasmus Villemoes
On 2016-07-14 16:42, Guenter Roeck wrote: On 07/14/2016 02:16 AM, Rasmus Villemoes wrote: +config WATCHDOG_OPEN_DEADLINE +bool "Allow deadline for opening watchdog device" +help + If a watchdog driver indicates that to the framework that + the hardware watchdog is running, the

Re: [RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-14 Thread Guenter Roeck
On 07/14/2016 02:16 AM, Rasmus Villemoes wrote: The watchdog framework takes care of feeding a hardware watchdog until userspace opens /dev/watchdogN. If that never happens for some reason (buggy init script, corrupt root filesystem or whatnot) but the kernel itself is fine, the machine stays up

[RFC 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_DEADLINE

2016-07-14 Thread Rasmus Villemoes
The watchdog framework takes care of feeding a hardware watchdog until userspace opens /dev/watchdogN. If that never happens for some reason (buggy init script, corrupt root filesystem or whatnot) but the kernel itself is fine, the machine stays up indefinitely. This patch allows setting an upper l