From: Patrick Williams <patrick@stwcx.xyz>
To: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
Cc: joel@jms.id.au, andrew@codeconstruct.com.au,
wim@linux-watchdog.org, linux@roeck-us.net,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, Peter.Yin@quantatw.com,
Patrick_NC_Lin@wiwynn.com, Bonnie_Lo@wiwynn.com,
DELPHINE_CHIU@wiwynn.com, bmc-sw@aspeedtech.com,
chnguyen@amperecomputing.com
Subject: Re: [PATCH v4 1/3] watchdog: aspeed: Update bootstatus handling
Date: Fri, 1 Nov 2024 14:21:20 -0400 [thread overview]
Message-ID: <ZyUcIIb1dtoNhX00@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <20241101121201.2464091-2-chin-ting_kuo@aspeedtech.com>
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
On Fri, Nov 01, 2024 at 08:11:59PM +0800, Chin-Ting Kuo wrote:
> The boot status mapping rule follows the latest design guide from
> the OpenBMC shown as below.
> https://github.com/openbmc/docs/blob/master/designs/bmc-reboot-cause-update.md#proposed-design
> - WDIOF_EXTERN1 => system is reset by Software
> - WDIOF_CARDRESET => system is reset by WDT SoC reset
> - Others => other reset events, e.g., power on reset.
I'm quite surprised that the above is relevant for a kernel driver at
all. Isn't "EXTERN1" a name of a real watchdog signal from your
hardware (my recollection is that there are 2 external watchdogs). I
think the point of this referenced design document was that most users
of BMCs have "EXTERN1" used a for software reset conditions.
`CARDRESET` should be representing resets by the watchdog itself.
The purpose of this design proposal was not to require very specific
changes to individual watchdog drivers, but to align the userspace use
with the best practices already from other watchdog drivers. I don't
think the kernel driver should be bending to match a particular
userspace implementation; you should be exposing the information
available to your hardware.
Having said that, it was known that there would need to be changes to
the driver because some of these conditions were not adequately exposed
at all. I'm just still surprised that we're needing to reference that
document as part of these changes.
>
> On ASPEED platform, the boot status is recorded in the SCU registers.
> - AST2400: Only a bit represents for any WDT reset.
> - AST2500: The reset triggered by different WDT controllers can be
> distinguished by different SCU bits. But, WDIOF_EXTERN1 or
> WDIOF_CARDRESET still cannot be identified due to
> HW limitation.
> - AST2600: Different from AST2500, additional HW bits are added for
> distinguishing WDIOF_EXTERN1 and WDIOF_CARDRESET.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-01 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 12:11 [PATCH v4 0/3] Update ASPEED WDT bootstatus Chin-Ting Kuo
2024-11-01 12:11 ` [PATCH v4 1/3] watchdog: aspeed: Update bootstatus handling Chin-Ting Kuo
2024-11-01 18:21 ` Patrick Williams [this message]
2024-11-04 0:01 ` Andrew Jeffery
2024-11-07 5:35 ` Chin-Ting Kuo
2024-11-07 23:49 ` Andrew Jeffery
2024-11-08 5:42 ` Chin-Ting Kuo
2024-11-08 14:07 ` Guenter Roeck
2024-11-18 12:46 ` Chin-Ting Kuo
2024-11-18 20:50 ` Guenter Roeck
2024-11-18 23:00 ` Andrew Jeffery
2024-11-19 1:27 ` Guenter Roeck
2024-11-20 4:54 ` Andrew Jeffery
2024-12-17 2:15 ` Chin-Ting Kuo
2024-11-07 5:34 ` Chin-Ting Kuo
2024-11-01 22:16 ` Guenter Roeck
2024-11-07 5:35 ` Chin-Ting Kuo
2024-11-01 12:12 ` [PATCH v4 2/3] watchdog: aspeed: Change aspeed_wdt_config struct name to aspeed_wdt_data Chin-Ting Kuo
2024-11-01 22:19 ` Guenter Roeck
2024-11-01 12:12 ` [PATCH v4 3/3] watchdog: aspeed: Update restart implementations Chin-Ting Kuo
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=ZyUcIIb1dtoNhX00@heinlein.vulture-banana.ts.net \
--to=patrick@stwcx.xyz \
--cc=Bonnie_Lo@wiwynn.com \
--cc=DELPHINE_CHIU@wiwynn.com \
--cc=Patrick_NC_Lin@wiwynn.com \
--cc=Peter.Yin@quantatw.com \
--cc=andrew@codeconstruct.com.au \
--cc=bmc-sw@aspeedtech.com \
--cc=chin-ting_kuo@aspeedtech.com \
--cc=chnguyen@amperecomputing.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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