devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shantur Rathore <i@shantur.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: "Heiko Stübner" <heiko@sntech.de>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dts: rockpro64: Remove usb regulator-always-on
Date: Mon, 8 Jan 2024 12:11:17 +0000	[thread overview]
Message-ID: <CABEcMwWEru2DYnd-Y3qWbEp25unVd96TogSnQ+-L+NXKS3_pZQ@mail.gmail.com> (raw)
In-Reply-To: <72f608668d619bda1cc620ce11eb3e40@manjaro.org>

Hi Dragan,

On Thu, Jan 4, 2024 at 9:50 AM Dragan Simic <dsimic@manjaro.org> wrote:
>
> On 2024-01-04 10:44, Shantur Rathore wrote:
> > On Fri, Dec 29, 2023 at 10:08 PM Heiko Stübner <heiko@sntech.de> wrote:
> >> Am Freitag, 22. Dezember 2023, 15:16:16 CET schrieb Shantur Rathore:
> >> > USB port regulators should be controlled by PHYs
> >> > so we remove always-on property and let PHYs manage the
> >> > regulator.
> >> >
> >> > phy-supply isn't sconfugred for the TypeC port and now that we are
> >>                 ^^ configured ?
> >>
> >> > removing regulator-always-on, we need to fix the phy-supply
> >> > so the PHYs are able to turn power to type-c port.
> >> >
> >> > Series-version: 2
> >> >
> >> > Signed-off-by: Shantur Rathore <i@shantur.com>
> >> > ---
> >> >  arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi | 3 +--
> >> >  1 file changed, 1 insertion(+), 2 deletions(-)
> >> >
> >> > diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
> >> > index bca2b50e0a..f7273f7990 100644
> >> > --- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
> >> > +++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi
> >> > @@ -192,7 +192,6 @@ vcc5v0_host: vcc5v0-host-regulator {
> >> >               pinctrl-names = "default";
> >> >               pinctrl-0 = <&vcc5v0_host_en>;
> >> >               regulator-name = "vcc5v0_host";
> >> > -             regulator-always-on;
> >> >               vin-supply = <&vcc5v0_usb>;
> >> >       };
> >> >
> >> > @@ -203,7 +202,6 @@ vcc5v0_typec: vcc5v0-typec-regulator {
> >> >               pinctrl-names = "default";
> >> >               pinctrl-0 = <&vcc5v0_typec_en>;
> >> >               regulator-name = "vcc5v0_typec";
> >> > -             regulator-always-on;
> >> >               vin-supply = <&vcc5v0_usb>;
> >> >       };
> >> >
> >> > @@ -859,6 +857,7 @@ &u2phy0 {
> >> >       status = "okay";
> >> >
> >> >       u2phy0_otg: otg-port {
> >> > +             phy-supply = <&vcc5v0_typec>;
> >> >               status = "okay";
> >> >       };
> >>
> >> Just to explain for me, what is supplying the "other" OTG port
> >>         u2phy1_otg: otg-port {}
> >>
> >> in u2phy1 ... this one is status okay, but does not have any phy
> >> supply?
> >>
> > In RockPro64 there is only 1 USB-C OTG port and the other port
> > is a USB-3.0 port.
> > To be honest, I am not 100% sure how this all works, as I understand
> > the USB3.0 port is wired to the second TypeC Phy.
> >
> > Maybe Dragan has more info on this.
>
> I'll have it checked and tested in detail, of course, but I have to
> recover from this nasty flu first.  Unfortunately, it has rendeded me
> unable to even think straight.

Hope you feel better soon.
It would be awesome if we can get this in while the current merge
window is open.

Kind regards,
Shantur

  reply	other threads:[~2024-01-08 12:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 14:16 [PATCH v2] dts: rockpro64: Remove usb regulator-always-on Shantur Rathore
2023-12-29 22:08 ` Heiko Stübner
2024-01-04  9:44   ` Shantur Rathore
2024-01-04  9:50     ` Dragan Simic
2024-01-08 12:11       ` Shantur Rathore [this message]
2024-01-08 12:29         ` Heiko Stübner
2024-01-08 14:47           ` Dragan Simic
2024-01-21 22:12             ` Shantur Rathore
2024-01-21 22:24               ` Dragan Simic
2024-01-21 22:56                 ` Shantur Rathore
2024-01-08 14:40         ` 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=CABEcMwWEru2DYnd-Y3qWbEp25unVd96TogSnQ+-L+NXKS3_pZQ@mail.gmail.com \
    --to=i@shantur.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=linux-rockchip@lists.infradead.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).