[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1bc83ee73545f9aab6e0a931cda8f5ffe41cb445.camel@codeconstruct.com.au>
Date: Wed, 20 Nov 2024 15:24:18 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Guenter Roeck <linux@...ck-us.net>, Chin-Ting Kuo
<chin-ting_kuo@...eedtech.com>, Patrick Williams <patrick@...cx.xyz>,
"wim@...ux-watchdog.org"
<wim@...ux-watchdog.org>
Cc: "joel@....id.au" <joel@....id.au>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-aspeed@...ts.ozlabs.org"
<linux-aspeed@...ts.ozlabs.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-watchdog@...r.kernel.org"
<linux-watchdog@...r.kernel.org>, "Peter.Yin@...ntatw.com"
<Peter.Yin@...ntatw.com>, "Patrick_NC_Lin@...ynn.com"
<Patrick_NC_Lin@...ynn.com>, "Bonnie_Lo@...ynn.com" <Bonnie_Lo@...ynn.com>,
"DELPHINE_CHIU@...ynn.com" <DELPHINE_CHIU@...ynn.com>, BMC-SW
<BMC-SW@...eedtech.com>, "chnguyen@...erecomputing.com"
<chnguyen@...erecomputing.com>
Subject: Re: [PATCH v4 1/3] watchdog: aspeed: Update bootstatus handling
On Mon, 2024-11-18 at 17:27 -0800, Guenter Roeck wrote:
> So, again, what exactly would userspace do with the information that
> this
> was a watchdog triggered warm reboot ? Why would it need that
> information ?
I'll defer to the others on To/Cc to answer that.
My only position is I don't think changing behaviour of existing
drivers to exploit WDIOF_EXTERN1 as a graceful-reboot indicator is a
good idea either. Obviously I don't have much skin in the game with
watchdog maintenance, so my thoughts shouldn't have much influence
beyond the Aspeed-specifics, but I just didn't want to see some fun new
confusion or incompatibility arise as a result.
Andrew
Powered by blists - more mailing lists