mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sebastian Reichel <sebastian.reichel@collabora.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: dw_wdt: Fix default timeout
Date: Fri, 18 Jul 2025 12:45:18 -0700	[thread overview]
Message-ID: <05d07f4c-a82f-48fe-bac5-e947d0324e98@roeck-us.net> (raw)
In-Reply-To: <20250717-dw-wdt-fix-initial-timeout-v1-1-86dc864d48dd@kernel.org>

On 7/17/25 09:55, Sebastian Reichel wrote:
> The Synopsys Watchdog driver sets the default timeout to 30 seconds,
> but on some devices this is not a valid timeout. E.g. on RK3588 the
> actual timeout being used is 44 seconds instead.
> 
> Once the watchdog is started the value is updated accordingly, but
> it would be better to expose a sensible timeout to userspace without
> the need to first start the watchdog.
> 
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
> This has been found when setting up a CI pipeline, that
> intentionally runs into the watchdog timeout.
> ---
>   drivers/watchdog/dw_wdt.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/watchdog/dw_wdt.c b/drivers/watchdog/dw_wdt.c
> index 26efca9ae0e7d2fea1b2eaf68085a70829b62b3a..c3fbb6068c520133c8a4ca97313706e877857a7f 100644
> --- a/drivers/watchdog/dw_wdt.c
> +++ b/drivers/watchdog/dw_wdt.c
> @@ -644,6 +644,8 @@ static int dw_wdt_drv_probe(struct platform_device *pdev)
>   	} else {
>   		wdd->timeout = DW_WDT_DEFAULT_SECONDS;
>   		watchdog_init_timeout(wdd, 0, dev);
> +		/* Limit timeout value to hardware constraints. */
> +		dw_wdt_set_timeout(wdd, wdd->timeout);
>   	}
>   
>   	platform_set_drvdata(pdev, dw_wdt);
> 
> ---
> base-commit: e2291551827fe5d2d3758c435c191d32b6d1350e
> change-id: 20250717-dw-wdt-fix-initial-timeout-d4b3a2ada6ed
> 
> Best regards,


      reply	other threads:[~2025-07-18 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 16:55 Sebastian Reichel
2025-07-18 19:45 ` 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=05d07f4c-a82f-48fe-bac5-e947d0324e98@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=sebastian.reichel@collabora.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

all inboxes | Powered by JetHome®