From: Kevin Chen <kevin_chen@aspeedtech.com>
To: <lee@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <joel@jms.id.au>,
<andrew@codeconstruct.com.au>, <chiawei_wang@aspeedtech.com>,
<linux-aspeed@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Kevin Chen <kevin_chen@aspeedtech.com>
Subject: [PATCH v1 0/3] Add AST2600 LPC PCC support
Date: Mon, 17 Feb 2025 19:48:28 +0800 [thread overview]
Message-ID: <20250217114831.3225970-1-kevin_chen@aspeedtech.com> (raw)
The AST2600 has PCC controller in LPC, placed in LPC node. As a result,
add LPC PCC controller driver to support POST code capture.
--
v1:
- Change pachset from 1.
- Remove properties in pcc driver.
Kevin Chen (3):
dt-binding: aspeed: Add LPC PCC controller
ARM: dts: aspeed-g6: Add AST2600 LPC PCC support
soc: aspeed: lpc-pcc: Add PCC controller support
.../devicetree/bindings/mfd/aspeed-lpc.yaml | 36 ++
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 7 +
drivers/soc/aspeed/Kconfig | 10 +
drivers/soc/aspeed/Makefile | 1 +
drivers/soc/aspeed/aspeed-lpc-pcc.c | 439 ++++++++++++++++++
5 files changed, 493 insertions(+)
create mode 100644 drivers/soc/aspeed/aspeed-lpc-pcc.c
--
2.34.1
next reply other threads:[~2025-02-17 11:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:48 Kevin Chen [this message]
2025-02-17 11:48 ` [PATCH v1 1/3] dt-binding: aspeed: Add LPC PCC controller Kevin Chen
2025-02-17 11:56 ` Krzysztof Kozlowski
2025-02-17 11:48 ` [PATCH v1 2/3] ARM: dts: aspeed-g6: Add AST2600 LPC PCC support Kevin Chen
2025-02-17 11:48 ` [PATCH v1 3/3] soc: aspeed: lpc-pcc: Add PCC controller support Kevin Chen
2025-02-17 12:00 ` Krzysztof Kozlowski
2025-02-18 0:56 ` Andrew Jeffery
2025-02-18 11:11 ` Kevin Chen
2025-02-19 1:04 ` Andrew Jeffery
2025-02-19 11:59 ` Kevin Chen
2025-02-20 1:22 ` Andrew Jeffery
2025-02-21 0:51 ` Kevin Chen
2025-02-25 4:27 ` Andrew Jeffery
2025-02-25 4:34 ` Mo Elbadry
2025-02-25 23:28 ` Andrew Jeffery
2025-02-26 0:48 ` Mo Elbadry
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=20250217114831.3225970-1-kevin_chen@aspeedtech.com \
--to=kevin_chen@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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