From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Caesar Wang <wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] arm64: dts: rockchip: fix defines in pd_vio node for rk3399
Date: Sun, 22 Mar 2020 19:03:35 +0100 [thread overview]
Message-ID: <48029127.kezn7BFppT@diego> (raw)
In-Reply-To: <1a6f0ba0-c49c-c547-1252-eed404655f43-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Am Sonntag, 22. März 2020, 17:14:54 CET schrieb Johan Jonker:
> Hi,
>
> Why is 'pd_tcpc0, pd_tcpc1' grouped under 'pd_vio' instead of VD_LOGIC?
^^
You'll need to add Rockchip-people for that - I've done that now ;-)
> 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?
We should probably just fix the nodename as you did.
- For one tcpD seems to be appearing way more often than tcpC
- and of course the header is part of the binding itself, so that shouldn't
change without a really good reason
Heiko
> >
> > 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>;
> >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>,
Caesar Wang <wxt@rock-chips.com>,
kever.yang@rock-chips.com
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: fix defines in pd_vio node for rk3399
Date: Sun, 22 Mar 2020 19:03:35 +0100 [thread overview]
Message-ID: <48029127.kezn7BFppT@diego> (raw)
In-Reply-To: <1a6f0ba0-c49c-c547-1252-eed404655f43@gmail.com>
Am Sonntag, 22. März 2020, 17:14:54 CET schrieb Johan Jonker:
> Hi,
>
> Why is 'pd_tcpc0, pd_tcpc1' grouped under 'pd_vio' instead of VD_LOGIC?
^^
You'll need to add Rockchip-people for that - I've done that now ;-)
> 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?
We should probably just fix the nodename as you did.
- For one tcpD seems to be appearing way more often than tcpC
- and of course the header is part of the binding itself, so that shouldn't
change without a really good reason
Heiko
> >
> > 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>;
> >
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>,
Caesar Wang <wxt@rock-chips.com>,
kever.yang@rock-chips.com
Cc: devicetree@vger.kernel.org, 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 19:03:35 +0100 [thread overview]
Message-ID: <48029127.kezn7BFppT@diego> (raw)
In-Reply-To: <1a6f0ba0-c49c-c547-1252-eed404655f43@gmail.com>
Am Sonntag, 22. März 2020, 17:14:54 CET schrieb Johan Jonker:
> Hi,
>
> Why is 'pd_tcpc0, pd_tcpc1' grouped under 'pd_vio' instead of VD_LOGIC?
^^
You'll need to add Rockchip-people for that - I've done that now ;-)
> 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?
We should probably just fix the nodename as you did.
- For one tcpD seems to be appearing way more often than tcpC
- and of course the header is part of the binding itself, so that shouldn't
change without a really good reason
Heiko
> >
> > 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>;
> >
>
>
next prev parent reply other threads:[~2020-03-22 18:03 UTC|newest]
Thread overview: 11+ 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 14:00 ` Johan Jonker
[not found] ` <20200322140046.5824-1-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-22 15:45 ` Johan Jonker
2020-03-22 15:45 ` Johan Jonker
2020-03-22 15:45 ` Johan Jonker
[not found] ` <48a91cc1-7751-4df0-a2cd-940eb829fa16-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-22 16:14 ` Johan Jonker
2020-03-22 16:14 ` Johan Jonker
2020-03-22 16:14 ` Johan Jonker
[not found] ` <1a6f0ba0-c49c-c547-1252-eed404655f43-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-03-22 18:03 ` Heiko Stübner [this message]
2020-03-22 18:03 ` Heiko Stübner
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=48029127.kezn7BFppT@diego \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.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.