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>, <derek.kiernan@amd.com>,
<dragan.cvetic@amd.com>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Cc: Kevin Chen <kevin_chen@aspeedtech.com>
Subject: [PATCH v4 2/3] ARM: dts: aspeed-g6: Add AST2600 LPC PCC support
Date: Fri, 14 Mar 2025 19:21:12 +0800 [thread overview]
Message-ID: <20250314112113.953238-3-kevin_chen@aspeedtech.com> (raw)
In-Reply-To: <20250314112113.953238-1-kevin_chen@aspeedtech.com>
The AST2600 has PCC controller in LPC, placed in LPC node.
Signed-off-by: Kevin Chen <kevin_chen@aspeedtech.com>
---
arch/arm/boot/dts/aspeed/aspeed-g6.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi b/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi
index 8ed715bd53aa..f238337e02da 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi
+++ b/arch/arm/boot/dts/aspeed/aspeed-g6.dtsi
@@ -626,6 +626,14 @@ lpc_snoop: lpc-snoop@80 {
status = "disabled";
};
+ lpc_pcc: lpc-pcc@0 {
+ compatible = "aspeed,ast2600-lpc-pcc";
+ reg = <0x0 0x140>;
+ interrupts = <GIC_SPI 145 IRQ_TYPE_LEVEL_HIGH>;
+ pcc-ports = <0x80>;
+ status = "disabled";
+ };
+
lhc: lhc@a0 {
compatible = "aspeed,ast2600-lhc";
reg = <0xa0 0x24 0xc8 0x8>;
--
2.34.1
next prev parent reply other threads:[~2025-03-14 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 11:21 [PATCH v4 0/3] Add AST2600 LPC PCC support Kevin Chen
2025-03-14 11:21 ` [PATCH v4 1/3] dt-binding: aspeed: Add LPC PCC controller Kevin Chen
2025-03-17 9:12 ` Krzysztof Kozlowski
2025-03-14 11:21 ` Kevin Chen [this message]
2025-03-17 9:13 ` [PATCH v4 2/3] ARM: dts: aspeed-g6: Add AST2600 LPC PCC support Krzysztof Kozlowski
2025-03-14 11:21 ` [PATCH v4 3/3] soc: aspeed: lpc-pcc: Add PCC controller support Kevin Chen
2025-03-18 0:42 ` 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=20250314112113.953238-3-kevin_chen@aspeedtech.com \
--to=kevin_chen@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=derek.kiernan@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@amd.com \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.