[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ea80ec65-8621-453c-4d5b-af38d8afeb70@pengutronix.de>
Date: Fri, 22 Nov 2019 11:28:47 +0100
From: Ahmad Fatoum <a.fatoum@...gutronix.de>
To: Christophe Roullier <christophe.roullier@...com>,
wim@...ux-watchdog.org, linux@...ck-us.net,
mcoquelin.stm32@...il.com, alexandre.torgue@...com
Cc: linux-kernel@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-watchdog@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, kernel@...gutronix.de
Subject: Re: [Linux-stm32] [PATCH v2 1/1] drivers: watchdog: stm32_iwdg: set
WDOG_HW_RUNNING at probe
Hello Christophe,
On 11/22/19 9:24 AM, Christophe Roullier wrote:
> + /*
> + * In case of CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED is set
> + * (Means U-Boot/bootloaders leaves the watchdog running)
> + * When we get here we should make a decision to prevent
> + * any side effects before user space daemon will take care of it.
> + * The best option, taking into consideration that there is no
> + * way to read values back from hardware, is to enforce watchdog
> + * being run with deterministic values.
What about the "ONF: Watchdog enable status bit" in the IWDG_SR register?
Cheers
Ahmad
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists