[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250112081204.263216-1-chin-ting_kuo@aspeedtech.com>
Date: Sun, 12 Jan 2025 16:12:03 +0800
From: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>
To: <patrick@...cx.xyz>, <andrew@...econstruct.com.au>, <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: [PATCH v6 0/1] Update ASPEED WDT bootstatus
This patch series inherits the patch submitted by Peter.
https://patchwork.kernel.org/project/linux-watchdog/patch/20240430143114.1323686-2-peteryin.openbmc@gmail.com/
Bootstatus mechanism is reconstructed to the latest
architecture and for all existing ASPEED BMC platforms.
Changes in v2:
- Support SW restart on AST2600 by default without
adding any dts property.
Changes in v3:
- Get watchdog controller index by dividing register
base offset by register size.
Changes in v4:
- Update the commit message for updating bootstatus
handling patch.
- Rename aspeed_wdt_config struct to aspeed_wdt_data.
- Create restart callback function.
Changes in v5:
- Remove SW reset mechanism since there is no consensus
about bootstatus for SW reset currently.
- Correct the method for clearing reset event flag on
AST2400 and AST2500 legacy platforms.
Changes in v6:
- Use resource_size() function to get WDT controller
registers size.
Chin-Ting Kuo (1):
watchdog: aspeed: Update bootstatus handling
drivers/watchdog/aspeed_wdt.c | 81 ++++++++++++++++++++++++++++++++++-
1 file changed, 79 insertions(+), 2 deletions(-)
--
2.34.1
Powered by blists - more mailing lists