From: Icenowy Zheng <uwu@icenowy.me>
To: Andre Przywara <andre.przywara@arm.com>, Hermann.Lauer@uni-heidelberg.de
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: sun8i-r40: remove unused GPIO regulator
Date: Sat, 14 Dec 2024 15:13:23 +0800 [thread overview]
Message-ID: <e61c927a4dfe909f4ede4a07dffd9dcd762875be.camel@icenowy.me> (raw)
In-Reply-To: <20241214011612.4fd9e4bf@minigeek.lan>
在 2024-12-14星期六的 01:16 +0000,Andre Przywara写道:
> On Fri, 13 Dec 2024 20:54:33 +0100
> Hermann.Lauer@uni-heidelberg.de wrote:
>
> Hi,
>
> CC:ing Icenowy, who added the regulator originally, with commit
> 0ca12c1ee43c ("ARM: sun8i: r40: add 5V regulator for Banana Pi M2
> Ultra").
>
> Icenowy: can you clarify what "newer" version this was referring to
> in
> that commit message? That commit in itself doesn't seem to do
> anything,
> as the regulator isn't referenced, and it's not always-on. It's only
> later when the USB nodes were added that it got used?
> So was PH23 really necessary? As Hermann reports, setting PH23 on a
> v1.1
> makes it reboot.
I am not sure, the schematics I have here (which says V1.0) have PH23
as NC... Well, the M2 Berry schematics have PH23 as 5V EN, maybe I
messed up M2U and M2B when developing?
Sorry but I think the data retention situation of my memory looks bad
here, maybe it needs a shorter refresh interval ;-)
>
> > Subject: [PATCH v2] ARM: dts: sun8i-r40: remove unused GPIO
> > regulator
>
> Hermann, this looks like an extra subject line here?
>
> > Banana Pi M2 Ultra V1.1 board resets immediately when the usb core
> > tries
> > to setup PH23 GPIO. It turned out that the V1.0 board USB-A ports
> > are
> > always power supplied and according to the board scheme PH23 is
> > simply
> > not connected.
> >
> > So remove the PH23 setup: Doesn't harm V1.0 (with R40) and let V1.1
> > (with A40i) start.
> >
> > Signed-off-by: Hermann Lauer <Hermann.Lauer@uni-heidelberg.de>
>
> The patch itself looks good to me, but it would be good to clarify
> the
> situation with the "older newer" version.
>
> Just in case:
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
>
> Cheers,
> Andre
>
> > ---
> > V2: shorten subject, rm dangerous PH23 regulator completely
> >
> > diff --git a/arch/arm/boot/dts/allwinner/sun8i-r40-bananapi-m2-
> > ultra.dts b/arch/arm/boot/dts/allwinner/sun8i-r40-bananapi-m2-
> > ultra.dts
> > --- a/arch/arm/boot/dts/allwinner/sun8i-r40-bananapi-m2-ultra.dts
> > +++ b/arch/arm/boot/dts/allwinner/sun8i-r40-bananapi-m2-ultra.dts
> > @@ -91,15 +91,6 @@
> > };
> > };
> >
> > - reg_vcc5v0: vcc5v0 {
> > - compatible = "regulator-fixed";
> > - regulator-name = "vcc5v0";
> > - regulator-min-microvolt = <5000000>;
> > - regulator-max-microvolt = <5000000>;
> > - gpio = <&pio 7 23 GPIO_ACTIVE_HIGH>; /* PH23 */
> > - enable-active-high;
> > - };
> > -
> > wifi_pwrseq: pwrseq {
> > compatible = "mmc-pwrseq-simple";
> > reset-gpios = <&pio 6 10 GPIO_ACTIVE_LOW>; /* PG10
> > WIFI_EN */
> > @@ -347,7 +338,5 @@
> > };
> >
> > &usbphy {
> > - usb1_vbus-supply = <®_vcc5v0>;
> > - usb2_vbus-supply = <®_vcc5v0>;
> > status = "okay";
> > };
> >
>
>
next prev parent reply other threads:[~2024-12-14 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:54 Hermann.Lauer
2024-12-14 1:16 ` Andre Przywara
2024-12-14 7:13 ` Icenowy Zheng [this message]
2024-12-20 17:21 ` Hermann Lauer
2024-12-22 17:18 ` Chen-Yu Tsai
2025-02-14 15:05 ` Hermann.Lauer
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=e61c927a4dfe909f4ede4a07dffd9dcd762875be.camel@icenowy.me \
--to=uwu@icenowy.me \
--cc=Hermann.Lauer@uni-heidelberg.de \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®