From: Johan Jonker <jbx6244@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: devicetree@vger.kernel.org, heiko@sntech.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: fix defines in pd_vio node for rk3399
Date: Sun, 22 Mar 2020 17:14:54 +0100 [thread overview]
Message-ID: <1a6f0ba0-c49c-c547-1252-eed404655f43@gmail.com> (raw)
In-Reply-To: <48a91cc1-7751-4df0-a2cd-940eb829fa16@gmail.com>
Hi,
Why is 'pd_tcpc0, pd_tcpc1' grouped under 'pd_vio' instead of VD_LOGIC?
Thanks
On 3/22/20 4:45 PM, Johan Jonker wrote:
> Hi,
>
> The RK3399 TRM uses both
>
> 'pd_tcpc0, pd_tcpc1'
>
> as
>
> 'pd_tcpd0, pd_tcpd1'.
>
> What should we use here?
>
> Thanks.
>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> index 8aac201f0..3dc8fe620 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> @@ -1087,12 +1087,12 @@
>> pm_qos = <&qos_isp1_m0>,
>> <&qos_isp1_m1>;
>> };
>> - pd_tcpc0@RK3399_PD_TCPC0 {
>> + pd_tcpc0@RK3399_PD_TCPD0 {
>> reg = <RK3399_PD_TCPD0>;
>> clocks = <&cru SCLK_UPHY0_TCPDCORE>,
>> <&cru SCLK_UPHY0_TCPDPHY_REF>;
>> };
>> - pd_tcpc1@RK3399_PD_TCPC1 {
>> + pd_tcpc1@RK3399_PD_TCPD1 {
>> reg = <RK3399_PD_TCPD1>;
>> clocks = <&cru SCLK_UPHY1_TCPDCORE>,
>> <&cru SCLK_UPHY1_TCPDPHY_REF>;
>> --
>> 2.11.0
>
next prev parent reply other threads:[~2020-03-22 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 14:00 [PATCH] arm64: dts: rockchip: fix defines in pd_vio node for rk3399 Johan Jonker
2020-03-22 15:45 ` Johan Jonker
2020-03-22 16:14 ` Johan Jonker [this message]
2020-03-22 18:03 ` Heiko Stübner
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=1a6f0ba0-c49c-c547-1252-eed404655f43@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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).