From: Guenter Roeck <linux@roeck-us.net>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Malin Jonsson <malin.jonsson@ericsson.com>,
john.jacques@intel.com, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2] watchdog: iTCO_wdt: No need to stop the timer in probe
Date: Tue, 21 Sep 2021 05:31:56 -0700 [thread overview]
Message-ID: <20210921123156.GA1864238@roeck-us.net> (raw)
In-Reply-To: <20210921102900.61586-1-mika.westerberg@linux.intel.com>
On Tue, Sep 21, 2021 at 01:29:00PM +0300, Mika Westerberg wrote:
> The watchdog core can handle pinging of the watchdog before userspace
> opens the device. For this reason instead of stopping the timer, just
> mark it as running and let the watchdog core take care of it.
>
> Cc: Malin Jonsson <malin.jonsson@ericsson.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Changes from v1:
>
> - Only set the WDOG_HW_RUNNING flag.
>
> drivers/watchdog/iTCO_wdt.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/watchdog/iTCO_wdt.c b/drivers/watchdog/iTCO_wdt.c
> index 643c6c2d0b72..a0e8ad3901a4 100644
> --- a/drivers/watchdog/iTCO_wdt.c
> +++ b/drivers/watchdog/iTCO_wdt.c
> @@ -430,6 +430,16 @@ static unsigned int iTCO_wdt_get_timeleft(struct watchdog_device *wd_dev)
> return time_left;
> }
>
> +static void iTCO_wdt_set_running(struct iTCO_wdt_private *p)
> +{
> + u16 val;
> +
> + /* Bit 11: TCO Timer Halt -> 0 = The TCO timer is * enabled */
> + val = inw(TCO1_CNT(p));
> + if (!(val & BIT(11)))
> + set_bit(WDOG_HW_RUNNING, &p->wddev.status);
> +}
> +
> /*
> * Kernel Interfaces
> */
> @@ -572,8 +582,7 @@ static int iTCO_wdt_probe(struct platform_device *pdev)
> watchdog_set_drvdata(&p->wddev, p);
> platform_set_drvdata(pdev, p);
>
> - /* Make sure the watchdog is not running */
> - iTCO_wdt_stop(&p->wddev);
> + iTCO_wdt_set_running(p);
>
> /* Check that the heartbeat value is within it's range;
> if not reset to the default */
> --
> 2.33.0
>
next prev parent reply other threads:[~2021-09-21 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 10:29 [PATCH v2] watchdog: iTCO_wdt: No need to stop the timer in probe Mika Westerberg
2021-09-21 12:31 ` Guenter Roeck [this message]
2023-07-05 11:22 ` Jan Kiszka
2023-07-11 7:09 ` Jan Kiszka
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=20210921123156.GA1864238@roeck-us.net \
--to=linux@roeck-us.net \
--cc=john.jacques@intel.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=malin.jonsson@ericsson.com \
--cc=mika.westerberg@linux.intel.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