[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42008fe4-8046-424c-9f12-e95a0471928d@roeck-us.net>
Date: Sun, 12 Jan 2025 07:20:38 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>, patrick@...cx.xyz,
andrew@...econstruct.com.au, wim@...ux-watchdog.org, joel@....id.au,
linux-watchdog@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Cc: Peter.Yin@...ntatw.com, Patrick_NC_Lin@...ynn.com, BMC-SW@...eedtech.com,
chnguyen@...erecomputing.com, aaron_lee@...eedtech.com
Subject: Re: [PATCH v6 1/1] watchdog: aspeed: Update bootstatus handling
On 1/12/25 00:12, Chin-Ting Kuo wrote:
> The boot status in the watchdog device struct is updated during
> controller probe stage. Application layer can get the boot status
> through the command, cat /sys/class/watchdog/watchdogX/bootstatus.
> The bootstatus can be,
> WDIOF_CARDRESET => the system is reset by WDT SoC reset.
> Others => other reset events, e.g., power on reset.
>
> On ASPEED platform, the boot status is recorded in the SCU registers.
> - AST2400: Only a bit represents for any WDT reset.
> - AST2500/AST2600: The reset triggered by different WDT controllers
> can be distinguished by different SCU bits.
>
> Besides, on AST2400 and AST2500, since alternating boot event is
> triggered by WDT SoC reset, it is classified as WDIOF_CARDRESET.
>
> Signed-off-by: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>
Reviewed-by: Guenter Roeck <linux@...ck-us.net>
Powered by blists - more mailing lists