[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150804112431.GK9999@pengutronix.de>
Date: Tue, 4 Aug 2015 13:24:31 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-watchdog@...r.kernel.org, Wim Van Sebroeck <wim@...ana.be>,
linux-kernel@...r.kernel.org,
Timo Kokkonen <timo.kokkonen@...code.fi>,
linux-doc@...r.kernel.org, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH 0/8] watchdog: Add support for keepalives triggered by
infrastructure
Hello Guenter,
On Mon, Aug 03, 2015 at 07:13:26PM -0700, Guenter Roeck wrote:
> This patch set does not solve all limitations of the watchdog subsystem.
> Specifically, it does not add support for the following features.
>
> - It is desirable to be able to specify a maximum early timeout,
> from booting the system to opening the watchdog device.
> - Some watchdogs may require a minimum period of time between
> heartbeats. Examples are DA9062 and possibly AT91SAM9x.
Other things that come to my mind:
- move handling of nowayout into the core
- some drivers use a reboot notifier. Not sure what they are intended
to do there. For i.MX2x it triggers a reboot; for gpio-wdt it tries
to stop the watchdog.
Of course this doesn't mean this should addressed here. I like the
series in general.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists