From: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: tomm.merciai@gmail.com, prabhakar.mahadev-lad.rj@bp.renesas.com,
linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] arm64: dts: renesas: r9a09g047e57-smarc: Enable USB2.0 support
Date: Mon, 21 Sep 2026 12:06:55 +0200 [thread overview]
Message-ID: <arEBv5HpjCgx9u4e@tom-desktop> (raw)
In-Reply-To: <CAMuHMdUYC2m3YgayTrCvZHoTVkj4v+7a5cvO1g=UFxR+6dJiJw@mail.gmail.com>
Hi Geert,
Thanks for your review.
On Mon, Sep 14, 2026 at 07:42:34PM +0200, Geert Uytterhoeven wrote:
> Hi Tommaso,
>
> On Wed, 9 Sept 2026 at 10:55, Tommaso Merciai
> <tommaso.merciai.xr@bp.renesas.com> wrote:
> > Enable USB2.0 support on the RZ/G3E EVK board. The USB1B_1A_HOST and
> > USB5_4_HOST connectors support host operation only, while USB0_OTG
> > supports both host and peripheral operation.
> >
> > renesas-smarc2.dtsi is shared by all boards based on the RZ SMARC
> > Carrier II Board. USB2.0 is not yet supported on the RZ/G3L SMARC
> > EVK, so disable the common USB2.0 nodes in its board DTS until proper
> > support is added.
> >
> > Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
>
> Thanks for your patch!
>
> > --- a/arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts
> > +++ b/arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts
> > @@ -298,6 +298,28 @@ sd1-data {
> > };
> > };
> >
> > + usb20_pins: usb20 {
> > + ovc {
> > + pinmux = <RZG3E_PORT_PINMUX(0, 0, 12)>; /* USB20_OVRCURN */
> > + bias-pull-up;
> > + };
> > +
> > + vbus {
> > + pinmux = <RZG3E_PORT_PINMUX(0, 1, 12)>; /* USB20_VBUSEN */
> > + };
> > + };
> > +
> > + usb21_pins: usb21 {
> > + ovc {
> > + pinmux = <RZG3E_PORT_PINMUX(G, 6, 12)>; /* USB21_OVRCURN */
> > + bias-pull-up;
> > + };
> > +
> > + vbus {
> > + pinmux = <RZG3E_PORT_PINMUX(K, 3, 12)>; /* USB21_VBUSEN */
> > + };
>
> While these two signals are wired to the SLG46108, which generates
> USB1_EN_OC# from that, the latter does not seem to be wired on the
> carrier board (SMARC_MODULE_CN P67)?
You are correct, USB1_EN_OC# -> P67 is not wired on the carrier board.
I will drop usb21_pins in v4.
Kind regards,
Tommaso
>
> > + };
> > +
> > usb3_pins: usb3 {
> > pinmux = <RZG3E_PORT_PINMUX(4, 1, 12)>, /* USB30_VBUSEN */
> > <RZG3E_PORT_PINMUX(4, 0, 12)>; /* USB30_OVRCURN */
>
> The rest LGTM.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
next prev parent reply other threads:[~2026-09-21 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 8:54 [PATCH v3 0/4] Add USB2.0 support for RZ/G3E Tommaso Merciai
2026-09-09 8:54 ` [PATCH v3 1/4] arm64: dts: renesas: r9a08g046: Add USB2.0 host/phy device nodes Tommaso Merciai
2026-09-09 9:08 ` sashiko-bot
2026-09-14 17:28 ` Geert Uytterhoeven
2026-09-15 9:40 ` Biju Das
2026-09-09 8:54 ` [PATCH v3 2/4] arm64: dts: renesas: r9a08g046: Add USB2.0 function " Tommaso Merciai
2026-09-09 8:55 ` [PATCH v3 3/4] arm64: dts: renesas: r9a09g047: Add USB2.0 support Tommaso Merciai
2026-09-14 17:34 ` Geert Uytterhoeven
2026-09-09 8:55 ` [PATCH v3 4/4] arm64: dts: renesas: r9a09g047e57-smarc: Enable " Tommaso Merciai
2026-09-14 17:42 ` Geert Uytterhoeven
2026-09-21 10:06 ` Tommaso Merciai [this message]
2026-09-21 9:57 ` [PATCH v3 0/4] Add USB2.0 support for RZ/G3E Tommaso Merciai
2026-09-21 12:31 ` Geert Uytterhoeven
2026-09-21 15:45 ` Biju Das
2026-09-21 16:24 ` Tommaso Merciai
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=arEBv5HpjCgx9u4e@tom-desktop \
--to=tommaso.merciai.xr@bp.renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=tomm.merciai@gmail.com \
/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.