[PATCH v1 4/6] watchdog: set some reasonable timeout_max value if no other is available
Sascha Hauer
s.hauer at pengutronix.de
Mon Mar 12 03:37:01 PDT 2018
On Thu, Mar 08, 2018 at 12:05:13PM +0100, Oleksij Rempel wrote:
> Some drivers do not provide timeout_max value.
> Using some value is probbaly better then setting timeout_max to 0.
>
> Signed-off-by: Oleksij Rempel <o.rempel at pengutronix.de>
> ---
> drivers/watchdog/wd_core.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/watchdog/wd_core.c b/drivers/watchdog/wd_core.c
> index 97e2ab568..66dbd790d 100644
> --- a/drivers/watchdog/wd_core.c
> +++ b/drivers/watchdog/wd_core.c
> @@ -41,6 +41,10 @@ int watchdog_register(struct watchdog *wd)
> if (!wd->priority)
> wd->priority = WATCHDOG_DEFAULT_PRIORITY;
>
> + /* set some default sane value */
> + if (!wd->timeout_max)
> + wd->timeout_max = 60 * 4;
4 minutes? Why so low? I would expect something like a few hours.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list