Re: [PATCH v24 1/2] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub

[Matthias Kaehlcke <mka@chromium.org>]

On Tue, Sep 06, 2022 at 03:02:23PM -0700, Doug Anderson wrote:
> Hi,
> 
> On Thu, Aug 18, 2022 at 2:31 PM Doug Anderson <dianders@chromium.org> wrote:
> >
> > Hi,
> >
> > On Fri, Jul 22, 2022 at 9:32 AM Matthias Kaehlcke <mka@chromium.org> wrote:
> > >
> > > Add nodes for the onboard USB hub on trogdor devices. Remove the
> > > 'always-on' property from the hub regulator, since the regulator
> > > is now managed by the onboard_usb_hub driver.
> > >
> > > For anyone using trogdor-based devices on Linux, it should be
> > > noted that this requires "CONFIG_USB_ONBOARD_HUB=y".
> > >
> > > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > > Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> > > Reviewed-by: Douglas Anderson <dianders@chromium.org>
> > > ---
> > > This series depends on 3a6bf4a08142 ("usb: core: hub: Create platform
> > > devices for onboard hubs in hub_probe()") which landed in -next [1].
> > >
> > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=3a6bf4a08142826698121bef16b244dcf50a6431
> > >
> > > Changes in v24:
> > > - renamed 'companion-hub' to 'peer-hub' according to the change
> > >   in the binding
> > >
> > > Changes in v23:
> > > - added note about enabling CONFIG_USB_ONBOARD_HUB to the commit
> > >   message
> > >
> > > Changes in v22:
> > > - none
> > >
> > > Changes in v21:
> > > - patch dropped from onboard_usb_hub series
> > >
> > > Changes in v20:
> > > - renamed hub labels to 'usb_hub_2/3_x'
> > > - added comment for 'regulator-boot-on' of 'pp3300_hub'
> > > - added 'Reviewed-by' tags from Stephen and Doug
> > >
> > > Changes in v19:
> > > - none
> > >
> > > Changes in v18:
> > > - also adjust config for pompom rev1
> > >
> > > Changes in v17:
> > > - none
> > >
> > > Changes in v16:
> > > - none
> > >
> > > Changes in v15:
> > > - none
> > >
> > > Changes in v14:
> > > - none
> > >
> > > Changes in v13:
> > > - none
> > >
> > > Changes in v12:
> > > - none
> > >
> > > Changes in v11:
> > > - rebased on qcom/arm64-for-5.14 (with the rest of the series)
> > >
> > > Changes in v10:
> > > - keep 'regulator-boot-on' property
> > > - updated commit message
> > >
> > > Changes in v9:
> > > - none
> > >
> > > Changes in v8:
> > > - none
> > >
> > > Changes in v7:
> > > - rebased on qcom/arm64-for-5.13 (with the rest of the series)
> > >
> > > Changes in v6:
> > > - added 'companion-hub' entry to both USB devices
> > > - added 'vdd-supply' also to hub@2
> > >
> > > Changes in v5:
> > > - patch added to the series
> > >
> > >  .../boot/dts/qcom/sc7180-trogdor-lazor-r0.dts | 19 ++++++++----------
> > >  .../boot/dts/qcom/sc7180-trogdor-lazor-r1.dts | 12 +++++------
> > >  .../dts/qcom/sc7180-trogdor-pompom-r1.dts     | 11 ++++------
> > >  .../arm64/boot/dts/qcom/sc7180-trogdor-r1.dts | 19 ++++++++----------
> > >  arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi  | 20 ++++++++++++++++++-
> > >  5 files changed, 44 insertions(+), 37 deletions(-)
> >
> > The driver changes have landed and stuck. They're in Linus's tree, so
> > I think we're now ready to land these two patches! Hooray!
> >
> > FWIW: I've continued my experiment of landing changes that I'm keeping
> > track of in a github tree:
> >
> > https://github.com/dianders/kernel-staging/commits/qcom/arm64-staging
> 
> I believe this series continues to be ready to land. Perhaps now would
> be a good time for it? ;-)

Ping, can these be landed?