From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Dragan Simic" <dsimic@manjaro.org>,
<linux-rockchip@lists.infradead.org>
Cc: <heiko@sntech.de>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: rockchip: Prepare RK356x SoC dtsi files for per-variant OPPs
Date: Sat, 19 Oct 2024 20:09:02 +0200 [thread overview]
Message-ID: <D4ZZFL98AMFI.1TDPL2DJPSQ3D@cknow.org> (raw)
In-Reply-To: <D4U30AUOH6UR.1QPH47KN5EWE4@cknow.org>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
Hi Dragan,
On Sat Oct 12, 2024 at 9:41 PM CEST, Diederik de Haas wrote:
> On Sat Oct 12, 2024 at 7:04 PM CEST, Dragan Simic wrote:
> >
> > -&pipegrf {
> > - compatible = "rockchip,rk3566-pipe-grf", "syscon";
>
> This seems unrelated?
>
> > +&cpu0 {
> > + operating-points-v2 = <&cpu0_opp_table>;
> > };
> >
> > -&power {
> > - power-domain@RK3568_PD_PIPE {
> > - reg = <RK3568_PD_PIPE>;
> > - clocks = <&cru PCLK_PIPE>;
> > - pm_qos = <&qos_pcie2x1>,
> > - <&qos_sata1>,
> > - <&qos_sata2>,
> > - <&qos_usb3_0>,
> > - <&qos_usb3_1>;
> > - #power-domain-cells = <0>;
> > - };
>
> This seems unrelated to me and possibly a functional change?
> If this was intended, then a description in the commit message would be
> nice why this is appropriate and possibly moved to a separate patch?
>
> > +&cpu1 {
> > + operating-points-v2 = <&cpu0_opp_table>;
> > +};
> > +
> > +&cpu2 {
> > + operating-points-v2 = <&cpu0_opp_table>;
> > };
> >
> > -&usb_host0_xhci {
> > - phys = <&usb2phy0_otg>;
> > - phy-names = "usb2-phy";
> > - extcon = <&usb2phy0>;
> > - maximum-speed = "high-speed";
>
> This also looks unrelated and a functional change?
>
> > +&cpu3 {
> > + operating-points-v2 = <&cpu0_opp_table>;
> > };
> >
> > -&vop {
> > - compatible = "rockchip,rk3566-vop";
>
> This also looks unrelated?
It turns out I was wrong.
The elements I thought were removed, aren't removed.
Sorry for the noise.
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-19 18:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 17:04 [PATCH 0/3] Update, encapsulate and expand the RK356x SoC dtsi files Dragan Simic
2024-10-12 17:04 ` [PATCH 1/3] arm64: dts: rockchip: Update CPU OPP voltages in RK356x SoC dtsi Dragan Simic
2024-10-12 19:27 ` Diederik de Haas
2024-10-12 19:45 ` Dragan Simic
2024-10-12 20:02 ` Diederik de Haas
2024-10-12 20:20 ` Dragan Simic
2024-10-12 17:04 ` [PATCH 2/3] arm64: dts: rockchip: Prepare RK356x SoC dtsi files for per-variant OPPs Dragan Simic
2024-10-12 19:41 ` Diederik de Haas
2024-10-12 20:01 ` Dragan Simic
2024-10-19 18:09 ` Diederik de Haas [this message]
2024-10-20 18:04 ` Dragan Simic
2024-10-12 17:04 ` [PATCH 3/3] arm64: dts: rockchip: Add new SoC dtsi for the RK3566T variant Dragan Simic
2024-10-12 19:42 ` Diederik de Haas
2024-10-12 20:07 ` Dragan Simic
2024-10-14 4:38 ` FUKAUMI Naoki
2024-10-14 5:16 ` Dragan Simic
2024-10-22 20:13 ` Dragan Simic
2024-10-22 23:30 ` FUKAUMI Naoki
2024-10-23 0:38 ` Dragan Simic
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=D4ZZFL98AMFI.1TDPL2DJPSQ3D@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--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 \
/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).