ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Regis Dargent <regis.dargent@gmail.com>, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH]: watchdog: Allow watchdog to remain enabled after probe
Date: Tue, 4 Feb 2025 10:27:50 +0000	[thread overview]
Message-ID: <5c2f4f75-d49e-4514-80d1-bfd250b99d11@arm.com> (raw)
In-Reply-To: <20250203171955.5858-1-regis.dargent@gmail.com>

Hi Regis,

first: can you say which version of U-Boot this should apply against? I 
cannot find a struct watchdog_info anywhere in the mainline source.

But more importantly:

On 03/02/2025 17:19, Regis Dargent wrote:
> ---
> The sunxi_wdt watchdog unconditionally stops the watchdog during probe (on my Allwinner H616).

This is expected. The probe routine does this to reset the watchdog.
The reason it stays disabled is CONFIG_WATCHDOG_AUTOSTART, which 
defaults to "n" on sunxi, see commit 86798ee0c148 for the reasons.
Also there were mailing list threads with more background info:

https://lore.kernel.org/u-boot/20211109220953.57b94ce8@slackpad.fritz.box/
https://lore.kernel.org/u-boot/20211109101901.24015-1-heinrich.schuchardt@canonical.com/

So long story short: if you really want to enable the watchdog in your 
particular case, you should just configure CONFIG_WATCHDOG_AUTOSTART to 
"y", in your local config.

Cheers,
Andre

> This avoids automatic reboot in case a problem occurs during boot (and for example handling in the bootloader).
> 
> The driver should detect if the HW watchdog is already running during probe and set its appropriate status bit to allow the kernel to handle the watchdog pings itself.
> The call to sunxi_wdt_start/stop allows for proper driver and device configuration.
> By default, the kernel will then ping the HW watchdog at apropriate frequency, but the user can have it stop after a time with open_timeout parameter.
> 
>   drivers/watchdog/sunxi_wdt.c | 20 +++++++++++++++++++-
>   1 file changed, 19 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/watchdog/sunxi_wdt.c b/drivers/watchdog/sunxi_wdt.c
> index b85354a99582..20fe7da445ea 100644
> --- a/drivers/watchdog/sunxi_wdt.c
> +++ b/drivers/watchdog/sunxi_wdt.c
> @@ -192,6 +192,16 @@ static int sunxi_wdt_start(struct watchdog_device *wdt_dev)
>   	return 0;
>   }
>   
> +static int sunxi_wdt_enabled(struct sunxi_wdt_dev *wdt)
> +{
> +	u32 reg;
> +	void __iomem *wdt_base = wdt->wdt_base;
> +	const struct sunxi_wdt_reg *regs = wdt->wdt_regs;
> +
> +	reg = readl(wdt_base + regs->wdt_mode);
> +	return (reg & WDT_MODE_EN);
> +}
> +
>   static const struct watchdog_info sunxi_wdt_info = {
>   	.identity	= DRV_NAME,
>   	.options	= WDIOF_SETTIMEOUT |
> @@ -268,6 +278,11 @@ static int sunxi_wdt_probe(struct platform_device *pdev)
>   	sunxi_wdt->wdt_dev.max_timeout = WDT_MAX_TIMEOUT;
>   	sunxi_wdt->wdt_dev.min_timeout = WDT_MIN_TIMEOUT;
>   	sunxi_wdt->wdt_dev.parent = dev;
> +	if (sunxi_wdt_enabled(sunxi_wdt)) {
> +		set_bit(WDOG_HW_RUNNING, &sunxi_wdt->wdt_dev.status);
> +	} else {
> +		clear_bit(WDOG_HW_RUNNING, &sunxi_wdt->wdt_dev.status);
> +	}
>   
>   	watchdog_init_timeout(&sunxi_wdt->wdt_dev, timeout, dev);
>   	watchdog_set_nowayout(&sunxi_wdt->wdt_dev, nowayout);
> @@ -275,7 +290,10 @@ static int sunxi_wdt_probe(struct platform_device *pdev)
>   
>   	watchdog_set_drvdata(&sunxi_wdt->wdt_dev, sunxi_wdt);
>   
> -	sunxi_wdt_stop(&sunxi_wdt->wdt_dev);
> +	if (watchdog_hw_running(&sunxi_wdt->wdt_dev))
> +		sunxi_wdt_start(&sunxi_wdt->wdt_dev);
> +	else
> +		sunxi_wdt_stop(&sunxi_wdt->wdt_dev);
>   
>   	watchdog_stop_on_reboot(&sunxi_wdt->wdt_dev);
>   	err = devm_watchdog_register_device(dev, &sunxi_wdt->wdt_dev);


  reply	other threads:[~2025-02-04 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 17:19 [PATCH]: watchdog: Allow watchdog to remain enabled after probe Regis Dargent
2025-02-04 10:27 ` Andre Przywara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-06  9:39 Regis Dargent
2025-02-06 10:14 ` Chen-Yu Tsai

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=5c2f4f75-d49e-4514-80d1-bfd250b99d11@arm.com \
    --to=andre.przywara@arm.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=regis.dargent@gmail.com \
    /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