From: "Heiko Stübner" <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
devicetree@vger.kernel.org, ulf.hansson@linaro.org,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 6/7] arm64: dts: rockchip: add core dtsi for RK3562 Soc
Date: Thu, 01 May 2025 15:28:16 +0200 [thread overview]
Message-ID: <47204993.fMDQidcC6G@diego> (raw)
In-Reply-To: <20250415051855.59740-7-kever.yang@rock-chips.com>
Hi Kever,
Am Dienstag, 15. April 2025, 07:18:54 Mitteleuropäische Sommerzeit schrieb Kever Yang:
> From: Finley Xiao <finley.xiao@rock-chips.com>
>
> RK3562 is a Soc from Rockchip, which embedded with quad
> ARM Cortex-A53.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v4:
> - remove gmac and otp nodes
>
> Changes in v3:
> - remove i2c/serial/spi alias
> - add soc node
>
> Changes in v2:
> - remove grf in cru
> - Update some properties order
>
> + soc {
> + compatible = "simple-bus";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + scmi_shmem: scmi-shmem@10f000 {
> + compatible = "arm,scmi-shmem";
> + reg = <0x0 0x0010f000 0x0 0x100>;
> + };
the scmi shmem is not a soc-device, but instead a piece of main memory.
We recently fixed that for example for the rk3588 [0], so please follow
along for this new soc.
Thanks a lot
Heiko
[0] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=8ecd096d018be8a6bd3bd930f3a41a85db66a67d
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
devicetree@vger.kernel.org, ulf.hansson@linaro.org,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 6/7] arm64: dts: rockchip: add core dtsi for RK3562 Soc
Date: Thu, 01 May 2025 15:28:16 +0200 [thread overview]
Message-ID: <47204993.fMDQidcC6G@diego> (raw)
In-Reply-To: <20250415051855.59740-7-kever.yang@rock-chips.com>
Hi Kever,
Am Dienstag, 15. April 2025, 07:18:54 Mitteleuropäische Sommerzeit schrieb Kever Yang:
> From: Finley Xiao <finley.xiao@rock-chips.com>
>
> RK3562 is a Soc from Rockchip, which embedded with quad
> ARM Cortex-A53.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v4:
> - remove gmac and otp nodes
>
> Changes in v3:
> - remove i2c/serial/spi alias
> - add soc node
>
> Changes in v2:
> - remove grf in cru
> - Update some properties order
>
> + soc {
> + compatible = "simple-bus";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + scmi_shmem: scmi-shmem@10f000 {
> + compatible = "arm,scmi-shmem";
> + reg = <0x0 0x0010f000 0x0 0x100>;
> + };
the scmi shmem is not a soc-device, but instead a piece of main memory.
We recently fixed that for example for the rk3588 [0], so please follow
along for this new soc.
Thanks a lot
Heiko
[0] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?id=8ecd096d018be8a6bd3bd930f3a41a85db66a67d
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-05-01 13:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 5:18 [PATCH v4 0/7] rockchip: Add rk3562 SoC and evb support Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-04-15 5:18 ` [PATCH v4 1/7] dt-bindings: PCI: dwc: rockchip: Add rk3562 support Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-04-19 9:53 ` Manivannan Sadhasivam
2025-04-19 9:53 ` Manivannan Sadhasivam
2025-04-15 5:18 ` [PATCH v4 2/7] dt-bindings: watchdog: Add rk3562 compatible Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-04-15 5:37 ` Guenter Roeck
2025-04-15 5:37 ` Guenter Roeck
2025-04-15 5:18 ` [PATCH v4 3/7] dt-bindings: rockchip: pmu: " Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-04-15 5:18 ` [PATCH v4 4/7] dt-bindings: soc: rockchip: Add rk3562 syscon compatibles Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-04-15 5:18 ` [PATCH v4 5/7] dt-bindings: arm: rockchip: Add rk3562 evb2 board Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-04-15 5:18 ` [PATCH v4 6/7] arm64: dts: rockchip: add core dtsi for RK3562 Soc Kever Yang
2025-04-15 5:18 ` Kever Yang
2025-05-01 13:28 ` Heiko Stübner [this message]
2025-05-01 13:28 ` Heiko Stübner
2025-04-15 5:18 ` [PATCH v4 7/7] arm64: dts: rockchip: Add RK3562 evb2 devicetree Kever Yang
2025-04-15 5:18 ` Kever Yang
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=47204993.fMDQidcC6G@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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.