From: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
To: <patrick@stwcx.xyz>, <andrew@codeconstruct.com.au>,
<linux@roeck-us.net>, <wim@linux-watchdog.org>, <joel@jms.id.au>,
<linux-watchdog@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Cc: <Peter.Yin@quantatw.com>, <Patrick_NC_Lin@wiwynn.com>,
<BMC-SW@aspeedtech.com>, <chnguyen@amperecomputing.com>,
<aaron_lee@aspeedtech.com>
Subject: [PATCH v6 0/1] Update ASPEED WDT bootstatus
Date: Sun, 12 Jan 2025 16:12:03 +0800 [thread overview]
Message-ID: <20250112081204.263216-1-chin-ting_kuo@aspeedtech.com> (raw)
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
next reply other threads:[~2025-01-12 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 8:12 Chin-Ting Kuo [this message]
2025-01-12 8:12 ` [PATCH v6 1/1] watchdog: aspeed: Update bootstatus handling Chin-Ting Kuo
2025-01-12 15:20 ` Guenter Roeck
2025-01-13 3:28 ` Andrew Jeffery
2025-01-13 3:41 ` Chin-Ting Kuo
2025-01-13 3:59 ` Andrew Jeffery
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=20250112081204.263216-1-chin-ting_kuo@aspeedtech.com \
--to=chin-ting_kuo@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=Patrick_NC_Lin@wiwynn.com \
--cc=Peter.Yin@quantatw.com \
--cc=aaron_lee@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--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=patrick@stwcx.xyz \
--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