From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Nishanth Menon <nm@ti.com>,
"nfraprado@collabora.com" <nfraprado@collabora.com>,
Taniya Das <quic_tdas@quicinc.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Eric Biggers <ebiggers@google.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"soc@lists.linux.dev" <soc@lists.linux.dev>,
Mo Elbadry <elbadrym@google.com>,
Rom Lemarchand <romlem@google.com>,
William Kennington <wak@google.com>,
Yuxiao Zhang <yuxiaozhang@google.com>,
"wthai@nvidia.com" <wthai@nvidia.com>,
"leohu@nvidia.com" <leohu@nvidia.com>,
"dkodihalli@nvidia.com" <dkodihalli@nvidia.com>,
"spuranik@nvidia.com" <spuranik@nvidia.com>
Subject: Re: [PATCH v0 3/5] arm64: dts: aspeed: Add initial AST2700 SoC device tree
Date: Mon, 16 Jun 2025 08:15:08 +0200 [thread overview]
Message-ID: <e39b5259-db92-4269-84c9-d51e8e4f327e@kernel.org> (raw)
In-Reply-To: <OS8PR06MB7541FFCA9E28E5767791D869F270A@OS8PR06MB7541.apcprd06.prod.outlook.com>
On 16/06/2025 04:24, Ryan Chen wrote:
>> Subject: Re: [PATCH v0 3/5] arm64: dts: aspeed: Add initial AST2700 SoC device
>> tree
>>
>> On 13/06/2025 04:29, Ryan Chen wrote:
>>>> Subject: Re: [PATCH v0 3/5] arm64: dts: aspeed: Add initial AST2700
>>>> SoC device tree
>>>>
>>>> On 12/06/2025 12:09, Ryan Chen wrote:
>>>>> This add the initial device tree support for the ASPEED AST2700 SoC.
>>>>>
>>>>> - Add top-level compatible string "aspeed,ast2700" and set up
>>>>> address-cells/size-cells for 64-bit address space.
>>>>> - Describe a quad-core ARM Cortex-A35 CPU cluster with L2 cache,
>>>>> including cache properties and PSCI enable-method.
>>>>> - Add PMU and ARMv8 timer nodes with correct PPI interrupt wiring.
>>>>> - Model the dual-SoC architecture with two simple-bus nodes:
>>>>> soc0 (@0x10000000) and soc1 (@0x14000000).
>>>>> - Add syscon nodes for both SoCs (syscon0, syscon1) with clock/reset
>>>>> cell definitions and address mapping.
>>>>> - Add GICv3 interrupt controller node under soc0, with full register
>>>>> mapping and interrupt properties.
>>>>> - Hierarchical interrupt controller structure:
>>>>> - intc0 under soc0, with child intc0_11 node.
>>>>> - intc1 under soc1, with child intc1_0~intc1_5 nodes.
>>>>> - Add serial4 node under soc0, others serial node under soc1.
>>>>>
>>>>> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
>>>>> ---
>>>>> arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi | 380
>>>>> ++++++++++++++++++++++
>>>>> 1 file changed, 380 insertions(+)
>>>>> create mode 100644 arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi
>>>>> b/arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi
>>>>> new file mode 100644
>>>>> index 000000000000..d197187bcf9f
>>>>> --- /dev/null
>>>>> +++ b/arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi
>>>>> @@ -0,0 +1,380 @@
>>>>> +// SPDX-License-Identifier: GPL-2.0-or-later #include
>>>>> +<dt-bindings/clock/aspeed,ast2700-scu.h>
>>>>> +#include <dt-bindings/reset/aspeed,ast2700-scu.h>
>>>>> +#include <dt-bindings/interrupt-controller/arm-gic.h>
>>>>> +
>>>>> +/ {
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <1>;
>>>>> + interrupt-parent = <&gic>;
>>>>> +
>>>>> + cpus {
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <0>;
>>>>> +
>>>>> + cpu0: cpu@0 {
>>>>> + device_type = "cpu";
>>>>> + compatible = "arm,cortex-a35";
>>>>> + reg = <0x0 0x0>;
>>>>> + enable-method = "psci";
>>>>> + i-cache-size = <0x8000>;
>>>>> + i-cache-line-size = <64>;
>>>>> + i-cache-sets = <256>;
>>>>> + d-cache-size = <0x8000>;
>>>>> + d-cache-line-size = <64>;
>>>>> + d-cache-sets = <128>;
>>>>> + next-level-cache = <&l2>;
>>>>> + };
>>>>> +
>>>>> + cpu1: cpu@1 {
>>>>> + device_type = "cpu";
>>>>> + compatible = "arm,cortex-a35";
>>>>> + enable-method = "psci";
>>>>> + reg = <0x0 0x1>;
>>>>> + i-cache-size = <0x8000>;
>>>>> + i-cache-line-size = <64>;
>>>>> + i-cache-sets = <256>;
>>>>> + d-cache-size = <0x8000>;
>>>>> + d-cache-line-size = <64>;
>>>>> + d-cache-sets = <128>;
>>>>> + next-level-cache = <&l2>;
>>>>> + };
>>>>> +
>>>>> + cpu2: cpu@2 {
>>>>> + device_type = "cpu";
>>>>> + compatible = "arm,cortex-a35";
>>>>> + enable-method = "psci";
>>>>> + reg = <0x0 0x2>;
>>>>> + i-cache-size = <0x8000>;
>>>>> + i-cache-line-size = <64>;
>>>>> + i-cache-sets = <256>;
>>>>> + d-cache-size = <0x8000>;
>>>>> + d-cache-line-size = <64>;
>>>>> + d-cache-sets = <128>;
>>>>> + next-level-cache = <&l2>;
>>>>> + };
>>>>> +
>>>>> + cpu3: cpu@3 {
>>>>> + device_type = "cpu";
>>>>> + compatible = "arm,cortex-a35";
>>>>> + enable-method = "psci";
>>>>> + reg = <0x0 0x3>;
>>>>> + i-cache-size = <0x8000>;
>>>>> + i-cache-line-size = <64>;
>>>>> + i-cache-sets = <256>;
>>>>> + d-cache-size = <0x8000>;
>>>>> + d-cache-line-size = <64>;
>>>>> + d-cache-sets = <128>;
>>>>> + next-level-cache = <&l2>;
>>>>> + };
>>>>> +
>>>>> + l2: l2-cache0 {
>>>>> + compatible = "cache";
>>>>> + cache-level = <2>;
>>>>> + cache-unified;
>>>>> + cache-size = <0x80000>;
>>>>> + cache-line-size = <64>;
>>>>> + cache-sets = <1024>;
>>>>> + };
>>>>> + };
>>>>> +
>>>>> + arm-pmu {
>>>>> + compatible = "arm,cortex-a35-pmu";
>>>>> + interrupts = <GIC_PPI 7 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_HIGH)>;
>>>>> + };
>>>>> +
>>>>> + psci {
>>>>> + compatible = "arm,psci-1.0";
>>>>> + method = "smc";
>>>>> + };
>>>>> +
>>>>> + timer {
>>>>> + compatible = "arm,armv8-timer";
>>>>> + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_LOW)>,
>>>>> + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_LOW)>,
>>>>> + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_LOW)>,
>>>>> + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_LOW)>;
>>>>> + arm,cpu-registers-not-fw-configured;
>>>>> + always-on;
>>>>> + };
>>>>> +
>>>>> + soc0: soc@10000000 {
>>>>> + compatible = "simple-bus";
>>>>> + reg = <0x0 0x10000000 0x10000000>;
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <1>;
>>>>> + ranges;
>>>>> +
>>>>> + syscon0: syscon@12c02000 {
>>>>> + compatible = "aspeed,ast2700-scu0", "syscon",
>> "simple-mfd";
>>>>> + reg = <0x0 0x12c02000 0x1000>;
>>>>> + ranges = <0x0 0x0 0 0x12c02000 0x1000>;
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <1>;
>>>>> + #clock-cells = <1>;
>>>>> + #reset-cells = <1>;
>>>>> + };
>>>>> +
>>>>> + gic: interrupt-controller@12200000 {
>>>>> + compatible = "arm,gic-v3";
>>>>> + reg = <0 0x12200000 0x10000>, /* GICD */
>>>>> + <0 0x12280000 0x80000>, /* GICR */
>>>>> + <0 0x40440000 0x1000>; /* GICC */
>>>>> + #interrupt-cells = <3>;
>>>>> + interrupt-controller;
>>>>> + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_HIGH)>;
>>>>> + interrupt-parent = <&gic>;
>>>>> + };
>>>>> +
>>>>> + serial4: serial@12c1a000 {
>>>>> + compatible = "ns16550a";
>>>>> + reg = <0x0 0x12c1a000 0x1000>;
>>>>> + clocks = <&syscon0 SCU0_CLK_GATE_UART4CLK>;
>>>>> + interrupts = <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>;
>>>>> + reg-shift = <2>;
>>>>> + status = "disabled";
>>>>> + };
>>>>> + };
>>>>> +
>>>>> + soc1: soc@14000000 {
>>>>> + compatible = "simple-bus";
>>>>> + reg = <0x0 0x14000000 0x10000000>;
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <1>;
>>>>> + ranges;
>>>>> +
>>>>> + syscon1: syscon@14c02000 {
>>>>> + compatible = "aspeed,ast2700-scu1", "syscon",
>> "simple-mfd";
>>>>> + reg = <0x0 0x14c02000 0x1000>;
>>>>> + ranges = <0x0 0x0 0x0 0x14c02000 0x1000>;
>>>>> + #address-cells = <2>;
>>>>> + #size-cells = <1>;
>>>>> + #clock-cells = <1>;
>>>>> + #reset-cells = <1>;
>>>>> + };
>>>>> +
>>>>> + serial12: serial@14c33b00 {
>>>>> + compatible = "ns16550a";
>>>>> + reg = <0x0 0x14c33b00 0x100>;
>>>>> + clocks = <&syscon1 SCU1_CLK_GATE_UART12CLK>;
>>>>> + interrupts-extended =
>>>>> + <&intc1_4 18 (GIC_CPU_MASK_SIMPLE(4) |
>>>> IRQ_TYPE_LEVEL_HIGH)>;
>>>>> + reg-shift = <2>;
>>>>> + status = "disabled";
>>>>> + };
>>>>> + };
>>>>> +};
>>>>> +
>>>>> +&soc0 {
>>>>
>>>> This is the base DTSI, there is no existing node to override. Just
>>>> define complete SoC node in one place like every other vendor.
>>>
>>> My original is use this way, but when I do checkpatch, get
>>> CHECK: line length of 106 exceeds 100 columns.
>>> interrupts = <GIC_SPI 192 (GIC_CPU_MASK_SIMPLE(4) |
>>> IRQ_TYPE_LEVEL_HIGH)>, That the reason modify by this way.
>>
>> Look how other recent, most developed platforms do it and learn from them
>> instead of coming with own, confusing style.
>
> Thanks, I will refer this to modify.
> https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/broadcom/bcm2712.dtsi#L580-L589
>>
>>>
>>>>
>>>>
>>>>> + intc0: interrupt-controller@12100000 {
>>>>> + compatible = "simple-mfd";
>>>>
>>>> NAK, never tested.
>>>>
>>>> Not allowed, see bindings. And test it next time.
>>>
>>> Got it, will update by following.
>>> Intc0: bus@12100000 {
>>> compatible = "simple-bus";
>>> #address-cells = <2>;
>>> #size-cells = <1>;
>>> reg = <0 0x12100000 0x4000>;
>>> ranges = <0x0 0x0 0x0 0x12100000 0x4000>;
>>> #address-cells = <2>;
>>
>> Does not follow DTS coding style and anyway, what sort of bus is this?
>
> Sorry, for miss-lead. intc0 is like the global base for inte0_11 interrupt-controller.
So that's not a bus, thus do not use simple-bus for that. Define
bindings for your device.
> So, I use simple-mfd.
> intc0: interrupt-controller@12100000 {
> compatible = "simple-mfd";
> .....
> intc0_11: interrupt-controller@1b00 {
> ......
> };
> };
>
> But I don't know your previous "NAK, never tested" mean.
> I did make CHECK_DTBS=y arch/arm64/boot/dts/aspeed/ don't see the fail with
> intc0: interrupt-controller@12100000 {
> compatible = "simple-mfd";
>
> So, could you point me more test instruction for this?
See syscon.yaml. And writing bindings or talks on conferences:
simple-mfd cannot be alone.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-16 6:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 10:09 [PATCH v0 0/5] Add initial AST2700 SoC support Ryan Chen
2025-06-12 10:09 ` [PATCH v0 1/5] dt-bindings: arm: aspeed: Add AST2700 board compatible Ryan Chen
2025-06-12 10:15 ` Krzysztof Kozlowski
2025-06-13 2:00 ` Ryan Chen
2025-06-12 10:09 ` [PATCH v0 2/5] arm64: Kconfig: Add Aspeed SoC family (ast2700) platform option Ryan Chen
2025-06-12 10:09 ` [PATCH v0 3/5] arm64: dts: aspeed: Add initial AST2700 SoC device tree Ryan Chen
2025-06-12 10:17 ` Krzysztof Kozlowski
2025-06-13 2:29 ` Ryan Chen
2025-06-13 6:16 ` Krzysztof Kozlowski
2025-06-16 2:24 ` Ryan Chen
2025-06-16 6:15 ` Krzysztof Kozlowski [this message]
2025-06-16 6:32 ` Ryan Chen
2025-06-16 6:43 ` Krzysztof Kozlowski
2025-06-16 6:54 ` Ryan Chen
2025-06-16 7:07 ` Krzysztof Kozlowski
2025-06-16 7:52 ` Ryan Chen
2025-06-16 10:29 ` Krzysztof Kozlowski
2025-06-12 10:20 ` Krzysztof Kozlowski
2025-06-13 2:54 ` Ryan Chen
2025-06-12 10:09 ` [PATCH v0 4/5] arm64: dts: aspeed: Add AST2700 EVB " Ryan Chen
2025-06-12 10:14 ` Krzysztof Kozlowski
2025-06-12 10:14 ` Krzysztof Kozlowski
2025-06-12 10:09 ` [PATCH v0 5/5] arm64: configs: Update defconfig for AST2700 platform support Ryan Chen
2025-06-12 10:18 ` Krzysztof Kozlowski
2025-06-12 20:12 ` [PATCH v0 0/5] Add initial AST2700 SoC support Rob Herring (Arm)
2025-06-13 5:29 ` Andrew Jeffery
2025-06-25 20:42 ` Rob Herring
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=e39b5259-db92-4269-84c9-d51e8e4f327e@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dkodihalli@nvidia.com \
--cc=ebiggers@google.com \
--cc=elbadrym@google.com \
--cc=geert@linux-m68k.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=leohu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=nm@ti.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=romlem@google.com \
--cc=ryan_chen@aspeedtech.com \
--cc=soc@lists.linux.dev \
--cc=spuranik@nvidia.com \
--cc=wak@google.com \
--cc=will@kernel.org \
--cc=wthai@nvidia.com \
--cc=yuxiaozhang@google.com \
/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;
as well as URLs for NNTP newsgroup(s).