From: Sven Peter <sven@svenpeter.dev>
To: Nick Chan <towinchenmi@gmail.com>
Cc: Hector Martin <marcan@marcan.st>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: apple: Increase reset delay to 150ms
Date: Fri, 13 Sep 2024 20:02:14 +0200 [thread overview]
Message-ID: <0F0CD820-4479-4DDB-BA89-CB44F4A190F3@svenpeter.dev> (raw)
In-Reply-To: <20240913174540.45551-1-towinchenmi@gmail.com>
>
> On 13. Sep 2024, at 19:46, Nick Chan <towinchenmi@gmail.com> wrote:
>
> The Apple A8X SoC seems to be slowest at resetting, taking up to around
> 125ms to reset. Wait 150ms to be safe here.
>
> Signed-off-by: Nick Chan <towinchenmi@gmail.com>
> ---
Reviewed-by: Sven Peter <sven@svenpeter.dev>
> drivers/watchdog/apple_wdt.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/watchdog/apple_wdt.c b/drivers/watchdog/apple_wdt.c
> index d4f739932f0b..353ecf0b04dc 100644
> --- a/drivers/watchdog/apple_wdt.c
> +++ b/drivers/watchdog/apple_wdt.c
> @@ -127,11 +127,11 @@ static int apple_wdt_restart(struct watchdog_device *wdd, unsigned long mode,
> /*
> * Flush writes and then wait for the SoC to reset. Even though the
> * reset is queued almost immediately experiments have shown that it
> - * can take up to ~20-25ms until the SoC is actually reset. Just wait
> - * 50ms here to be safe.
> + * can take up to ~120-125ms until the SoC is actually reset. Just
> + * wait 150ms here to be safe.
> */
> (void)readl_relaxed(wdt->regs + APPLE_WDT_WD1_CUR_TIME);
> - mdelay(50);
> + mdelay(150);
>
> return 0;
> }
>
> base-commit: 5acd9952f95fb4b7da6d09a3be39195a80845eb6
> --
> 2.46.0
>
prev parent reply other threads:[~2024-09-13 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 17:45 [PATCH] watchdog: apple: Increase reset delay to 150ms Nick Chan
2024-09-13 18:01 ` Guenter Roeck
2024-09-13 18:02 ` Sven Peter [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=0F0CD820-4479-4DDB-BA89-CB44F4A190F3@svenpeter.dev \
--to=sven@svenpeter.dev \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcan@marcan.st \
--cc=towinchenmi@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