From: Guenter Roeck <linux@roeck-us.net>
To: "André Draszik" <git@andred.net>
Cc: linux-kernel@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, John Crispin <john@phrozen.org>
Subject: Re: [PATCH v2 1/2] watchdog: mt7621: set WDOG_HW_RUNNING bit when appropriate
Date: Fri, 12 Jan 2018 15:22:55 -0800 [thread overview]
Message-ID: <20180112232255.GA5974@roeck-us.net> (raw)
In-Reply-To: <20180112094454.5518-1-git@andred.net>
On Fri, Jan 12, 2018 at 09:44:53AM +0000, André Draszik wrote:
> If the watchdog hardware is enabled/running during boot, e.g.
> due to a boot loader configuring it, we must tell the
> watchdog framework about this fact so that it can ping the
> watchdog until userspace opens the device and takes over
> control.
>
> Do so using the WDOG_HW_RUNNING flag that exists for exactly
> that use-case.
>
> Given the watchdog driver core doesn't know what timeout was
> originally set by whoever started the watchdog (boot loader),
> we make sure to update the timeout in the hardware according
> to what the watchdog core thinks it is.
>
> Signed-off-by: André Draszik <git@andred.net>
> Cc: Wim Van Sebroeck <wim@iguana.be>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: linux-watchdog@vger.kernel.org
> Cc: John Crispin <john@phrozen.org>
Reviewed-by: Guenter Roeck <Linux@roeck-us.net>
>
> ---
> Changes in v2:
> - fix typo and proper multi-line comment
> - update commit message to be clearer
> ---
> drivers/watchdog/mt7621_wdt.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/watchdog/mt7621_wdt.c b/drivers/watchdog/mt7621_wdt.c
> index db38f8017218..eec57e5e1eae 100644
> --- a/drivers/watchdog/mt7621_wdt.c
> +++ b/drivers/watchdog/mt7621_wdt.c
> @@ -105,6 +105,11 @@ static int mt7621_wdt_bootcause(void)
> return 0;
> }
>
> +static int mt7621_wdt_is_running(struct watchdog_device *w)
> +{
> + return !!(rt_wdt_r32(TIMER_REG_TMR1CTL) & TMR1CTL_ENABLE);
> +}
> +
> static const struct watchdog_info mt7621_wdt_info = {
> .identity = "Mediatek Watchdog",
> .options = WDIOF_SETTIMEOUT | WDIOF_KEEPALIVEPING | WDIOF_MAGICCLOSE,
> @@ -144,6 +149,20 @@ static int mt7621_wdt_probe(struct platform_device *pdev)
> watchdog_init_timeout(&mt7621_wdt_dev, mt7621_wdt_dev.max_timeout,
> &pdev->dev);
> watchdog_set_nowayout(&mt7621_wdt_dev, nowayout);
> + if (mt7621_wdt_is_running(&mt7621_wdt_dev)) {
> + /*
> + * Make sure to apply timeout from watchdog core, taking
> + * the prescaler of this driver here into account (the
> + * boot loader might be using a different prescaler).
> + *
> + * To avoid spurious resets because of different scaling,
> + * we first disable the watchdog, set the new prescaler
> + * and timeout, and then re-enable the watchdog.
> + */
> + mt7621_wdt_stop(&mt7621_wdt_dev);
> + mt7621_wdt_start(&mt7621_wdt_dev);
> + set_bit(WDOG_HW_RUNNING, &mt7621_wdt_dev.status);
> + }
>
> ret = watchdog_register_device(&mt7621_wdt_dev);
>
> --
> 2.15.1
>
prev parent reply other threads:[~2018-01-12 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 12:13 [PATCH 1/2] watchdog: mt7621: Set WDOG_HW_RUNNING, when watchdog is already running André Draszik
2018-01-10 12:13 ` [PATCH 2/2] watchdog: mt7621: switch to using managed devm_watchdog_register_device() André Draszik
2018-01-11 18:25 ` Guenter Roeck
2018-01-11 18:24 ` [PATCH 1/2] watchdog: mt7621: Set WDOG_HW_RUNNING, when watchdog is already running Guenter Roeck
2018-01-12 9:44 ` [PATCH v2 1/2] watchdog: mt7621: set WDOG_HW_RUNNING bit when appropriate André Draszik
2018-01-12 9:44 ` [PATCH v2 2/2] watchdog: mt7621: switch to using managed devm_watchdog_register_device() André Draszik
2018-01-12 23:22 ` Guenter Roeck [this message]
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=20180112232255.GA5974@roeck-us.net \
--to=linux@roeck-us.net \
--cc=git@andred.net \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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).