From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Christophe Roullier <christophe.roullier@st.com>,
wim@linux-watchdog.org, linux@roeck-us.net,
mcoquelin.stm32@gmail.com, alexandre.torgue@st.com
Cc: linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-watchdog@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de
Subject: Re: [Linux-stm32] [PATCH v2 1/1] drivers: watchdog: stm32_iwdg: set WDOG_HW_RUNNING at probe
Date: Fri, 22 Nov 2019 11:28:47 +0100 [thread overview]
Message-ID: <ea80ec65-8621-453c-4d5b-af38d8afeb70@pengutronix.de> (raw)
In-Reply-To: <20191122082442.21695-1-christophe.roullier@st.com>
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 |
next prev parent reply other threads:[~2019-11-22 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 8:24 [PATCH v2 1/1] drivers: watchdog: stm32_iwdg: set WDOG_HW_RUNNING at probe Christophe Roullier
2019-11-22 10:28 ` Ahmad Fatoum [this message]
2019-11-22 13:15 ` [Linux-stm32] " Christophe ROULLIER
2019-11-22 13:31 ` Ahmad Fatoum
2019-11-22 10:45 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea80ec65-8621-453c-4d5b-af38d8afeb70@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@st.com \
--cc=christophe.roullier@st.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcoquelin.stm32@gmail.com \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).