[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f01ea3f0184cb598cdfcc22d304ea31ef5b7dbbc.camel@codeconstruct.com.au>
Date: Mon, 03 Feb 2025 14:35:50 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>, patrick@...cx.xyz,
linux@...ck-us.net, 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 v7 1/1] watchdog: aspeed: Update bootstatus handling
On Mon, 2025-01-13 at 17:37 +0800, 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 => System is reset due to WDT timeout occurs.
> Others => Other reset events, e.g., power on reset.
>
> On ASPEED platforms, boot status is recorded in the SCU registers.
> - AST2400: Only a bit is used to represent system reset triggered by
> any WDT controller.
> - AST2500/AST2600: System reset triggered by different WDT
> controllers
> can be distinguished by different SCU bits.
>
> Besides, on AST2400 and AST2500, since alternating boot event is
> also triggered by using WDT timeout mechanism, it is classified
> as WDIOF_CARDRESET.
>
> Signed-off-by: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>
Reviewed-by: Andrew Jeffery <andrew@...econstruct.com.au>
Powered by blists - more mailing lists