RE: [PATCH v4 0/9] Add RZ/G3L USB2.0 host support

[Biju Das]

Hi All,

> -----Original Message-----
> From: Biju Das <biju.das.jz@xxxxxxxxxxxxxx>
> Sent: 22 July 2026 20:15
> Subject: RE: [PATCH v4 0/9] Add RZ/G3L USB2.0 host support
> 
> Hi All,
> 
> > -----Original Message-----
> > From: Biju <biju.das.au@xxxxxxxxx>
> > Sent: 09 July 2026 09:31
> > Subject: [PATCH v4 0/9] Add RZ/G3L USB2.0 host support
> >
> > From: Biju Das <biju.das.jz@xxxxxxxxxxxxxx>
> >
> > Hi All,
> >
> > This patch series aims to add USB2.0 host support for the RZ/G3L SMARC
> > EVK. The RZ/G3L USB PHY block is similar to RZ/G3S, but each port has
> > an OTG controller, unlike RZ/G3S, which has an OTG controller only on
> > port 1. This series migrates regulator driver to use id-table so there is hard dependency between reset
> driver and regulator driver.
> >
> > Merge strategy:
> >   An Ack/Rb tag from Regulator Maintainer for patch#4.
> >   Patch #1,#2,#3,#4 - Reset subsystem
> >   Patch #5,#6,#7 - PHY subsystem
> >   Patch #8,#9 - Renesas SoC
> >
> > v3->v4:
> >  * Updated cover letter with merge strategy
> >  * Reorder the phy binding patch for easy merging.
> >  * Updated the commit description for patch #2,#3, #4.
> >  * Moved the handling of regulator_driver_name to patch #3
> >    in preparation for id_table match.
> >  * Migrated to id_table match using driver_name and reduced the length
> >    < 24.
> >  * Dropped rzg3l specific platform driver.
> >  * Dropped the tag for regulator driver,
> >  * Added id_table handling by introducing a common probe().
> > v2->v3:
> >  * Replaced items->enum in reset controller bindings.
> >  * Collected the tag for reset binding patch.
> >  * Dropped clock patch as it is accepted.
> > v1->v2:
> >  * Dropped patch#6(Introduce helper for regulator registration)
> >  * Passing pointer to an array of regulators to make it scalable.
> >  * Dropped regulator1-vbus and added a regulators group node.
> >  * Updated commit description for patch#1,#4,#6,#7,#8,#9 and #10.
> >  * Added enum instead of const in the compatible section.
> >  * Updated schema check.
> >  * Collected tag for PHY binding patch.
> >    in the regulator driver.
> >  * Added regulators group node and its children in SoC dtsi.
> >
> > Biju Das (9):
> >   dt-bindings: reset: renesas,rzg2l-usbphy-ctrl: Document RZ/G3L support
> >   reset: rzg2l-usbphy-ctrl: Introduce info struct for match data
> >   reset: rzg2l-usbphy-ctrl: Add RZ/G3L support
> >   regulator: renesas-usb-vbus-regulator: Add RZ/G3L VBUS regulator
> >     support
> >   dt-bindings: phy: renesas,usb2-phy: Document RZ/G3L PHY bindings
> >   phy: renesas: phy-rcar-gen3-usb2: Add RZ/G3L support
> >   phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for
> >     disabled VBUS regulator
> >   arm64: dts: renesas: r9a08g046: Add USB2.0 device nodes
> >   arm64: dts: renesas: r9a08g046l48-smarc: Add USB2.0 support
> >
> >  .../bindings/phy/renesas,usb2-phy.yaml        |   2 +
> >  .../reset/renesas,rzg2l-usbphy-ctrl.yaml      |  48 +++++++-
> >  arch/arm64/boot/dts/renesas/r9a08g046.dtsi    | 105 ++++++++++++++++++
> >  .../boot/dts/renesas/r9a08g046l48-smarc.dts   |  49 ++++++++
> >  drivers/phy/renesas/phy-rcar-gen3-usb2.c      |  20 ++--
> >  .../regulator/renesas-usb-vbus-regulator.c    |  74 +++++++++++-
> >  drivers/reset/reset-rzg2l-usbphy-ctrl.c       |  44 +++++---
> >  7 files changed, 316 insertions(+), 26 deletions(-)
> >
> > --
> > 2.43.0
> 
> Gentle ping.

Based on the feedback on [1],

I have modelled pwrrdy signal as power sequence driver and used
with DSI driver and it works fine. So, it should work with USB PHY control
driver as well.

So, there will binding change to dropping renesas,sysc-pwrrdy for RZ/G3L.
and the driver will use Power sequence driver for configuring Power ready signal.

What should I do for RZ/G3S as it uses renesas,sysc-pwrrdy? Should I leave like
as it is to avoid ABI breakage? Or do you want me to add backward compatibility?

Please let me know.

[1] https://lore.kernel.org/all/TY3PR01MB11346892D9619A8D1A6C2DF4A86CF2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/


Cheers,
Biju