From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Chukun Pan <amadeus@jmu.edu.cn>, Yao Zi <ziyao@disroot.org>,
Lee Jones <lee@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add rk3528 QoS register node
Date: Wed, 5 Mar 2025 11:17:24 -0600 [thread overview]
Message-ID: <20250305171724.GA2149138-robh@kernel.org> (raw)
In-Reply-To: <52155b03-20f3-4e64-b636-70042db03ffa@kernel.org>
On Wed, Mar 05, 2025 at 04:41:23PM +0100, Krzysztof Kozlowski wrote:
> On 05/03/2025 15:00, Chukun Pan wrote:
> > Copy QoS nodes and add rk3528 compatible from bsp kernel,
>
> No, don't copy stuff from BSP kernel. It results in terrible DTS.
>
> > these can be used for power-domain.
> >
> > Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> > ---
> > arch/arm64/boot/dts/rockchip/rk3528.dtsi | 160 +++++++++++++++++++++++
> > 1 file changed, 160 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk3528.dtsi b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> > index 5b334690356a..794f35654975 100644
> > --- a/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> > +++ b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> > @@ -122,6 +122,166 @@ gic: interrupt-controller@fed01000 {
> > #interrupt-cells = <3>;
> > };
> >
> > + qos_crypto_a: qos@ff200000 {
> > + compatible = "rockchip,rk3528-qos", "syscon";
> > + reg = <0x0 0xff200000 0x0 0x20>;
> > + };
> > +
> > + qos_crypto_p: qos@ff200080 {
> > + compatible = "rockchip,rk3528-qos", "syscon";
> > + reg = <0x0 0xff200080 0x0 0x20>;
> > + };
>
>
> Did you just define syscon per few registers? Third case last weeks...
> so no, define what is your device here. 8 registers is not a device usually.
Well, it is just a new compatible on top of existing 'qos' compatibles.
And in a quick scan I didn't see other things adjacent.
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Chukun Pan <amadeus@jmu.edu.cn>, Yao Zi <ziyao@disroot.org>,
Lee Jones <lee@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add rk3528 QoS register node
Date: Wed, 5 Mar 2025 11:17:24 -0600 [thread overview]
Message-ID: <20250305171724.GA2149138-robh@kernel.org> (raw)
In-Reply-To: <52155b03-20f3-4e64-b636-70042db03ffa@kernel.org>
On Wed, Mar 05, 2025 at 04:41:23PM +0100, Krzysztof Kozlowski wrote:
> On 05/03/2025 15:00, Chukun Pan wrote:
> > Copy QoS nodes and add rk3528 compatible from bsp kernel,
>
> No, don't copy stuff from BSP kernel. It results in terrible DTS.
>
> > these can be used for power-domain.
> >
> > Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> > ---
> > arch/arm64/boot/dts/rockchip/rk3528.dtsi | 160 +++++++++++++++++++++++
> > 1 file changed, 160 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk3528.dtsi b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> > index 5b334690356a..794f35654975 100644
> > --- a/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> > +++ b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> > @@ -122,6 +122,166 @@ gic: interrupt-controller@fed01000 {
> > #interrupt-cells = <3>;
> > };
> >
> > + qos_crypto_a: qos@ff200000 {
> > + compatible = "rockchip,rk3528-qos", "syscon";
> > + reg = <0x0 0xff200000 0x0 0x20>;
> > + };
> > +
> > + qos_crypto_p: qos@ff200080 {
> > + compatible = "rockchip,rk3528-qos", "syscon";
> > + reg = <0x0 0xff200080 0x0 0x20>;
> > + };
>
>
> Did you just define syscon per few registers? Third case last weeks...
> so no, define what is your device here. 8 registers is not a device usually.
Well, it is just a new compatible on top of existing 'qos' compatibles.
And in a quick scan I didn't see other things adjacent.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-03-05 17:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 14:00 [PATCH 1/2] dt-bindings: mfd: syscon: Add rk3528 QoS register compatible Chukun Pan
2025-03-05 14:00 ` Chukun Pan
2025-03-05 14:00 ` [PATCH 2/2] arm64: dts: rockchip: Add rk3528 QoS register node Chukun Pan
2025-03-05 14:00 ` Chukun Pan
2025-03-05 15:41 ` Krzysztof Kozlowski
2025-03-05 15:41 ` Krzysztof Kozlowski
2025-03-05 17:17 ` Rob Herring [this message]
2025-03-05 17:17 ` Rob Herring
2025-03-05 17:51 ` Heiko Stübner
2025-03-05 17:51 ` Heiko Stübner
2025-03-06 7:15 ` Chukun Pan
2025-03-06 7:15 ` Chukun Pan
2025-03-05 22:19 ` [PATCH 1/2] dt-bindings: mfd: syscon: Add rk3528 QoS register compatible Rob Herring
2025-03-05 22:19 ` Rob Herring
2025-03-05 22:23 ` Rob Herring (Arm)
2025-03-05 22:23 ` Rob Herring (Arm)
2025-03-05 22:23 ` Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-03-08 5:27 [PATCH 2/2] arm64: dts: rockchip: Add rk3528 QoS register node kernel test robot
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=20250305171724.GA2149138-robh@kernel.org \
--to=robh@kernel.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ziyao@disroot.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.