From: Hector Martin <marcan@marcan.st>
To: Nick Chan <towinchenmi@gmail.com>,
Sven Peter <sven@svenpeter.dev>,
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 v2 RESEND 0/2] watchdog: apple: Increase reset delay to 150ms
Date: Fri, 1 Nov 2024 22:02:34 +0900 [thread overview]
Message-ID: <2f03a7aa-cd74-45d1-b56c-ab19c19d9632@marcan.st> (raw)
In-Reply-To: <20241029013055.45538-1-towinchenmi@gmail.com>
On 2024/10/29 10:29, Nick Chan wrote:
> Increase the reset delay to 150ms as the Apple A8X SoC can take up to
> 125ms to actually reset.
>
> Since the code is being modified anyways, also fix a bug where watchdog
> writes were not actually getting flushed after requesting reset, depsite
> what the code comments said.
>
> Changes since v1:
> - Fix an existing bug where watchdog writes are not flushed
>
> v1: https://lore.kernel.org/asahi/20240930060653.4024-1-towinchenmi@gmail.com
>
> Nick Chan
> ---
>
> Nick Chan (2):
> watchdog: apple: Actually flush writes after requesting watchdog
> restart
> watchdog: apple: Increase reset delay to 150ms
>
> drivers/watchdog/apple_wdt.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
>
> base-commit: dec9255a128e19c5fcc3bdb18175d78094cc624d
Acked-by: Hector Martin <marcan@marcan.st>
- Hector
prev parent reply other threads:[~2024-11-01 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 1:29 [PATCH v2 RESEND 0/2] watchdog: apple: Increase reset delay to 150ms Nick Chan
2024-10-29 1:29 ` [PATCH v2 RESEND 1/2] watchdog: apple: Actually flush writes after requesting watchdog restart Nick Chan
2024-10-29 1:29 ` [PATCH v2 RESEND 2/2] watchdog: apple: Increase reset delay to 150ms Nick Chan
2024-11-01 13:02 ` Hector Martin [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=2f03a7aa-cd74-45d1-b56c-ab19c19d9632@marcan.st \
--to=marcan@marcan.st \
--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=sven@svenpeter.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.