Re: [PATCH v1 1/2] dt-bindings: usb: Move Tegra-specific Chipidea USB properties into a dedicated schema
From: Svyatoslav Ryhel
Date: Wed Nov 18 2026 - 03:52:30 EST
вт, 17 лист. 2026 р. о 14:40 Thierry Reding <thierry.reding@xxxxxxxxxx> пише:
>
> On Tue, Oct 27, 2026 at 10:51:52AM +0200, Svyatoslav Ryhel wrote:
> > вт, 27 жовт. 2026 р. о 00:29 Rob Herring <robh@xxxxxxxxxx> пише:
> > >
> > > On Sun, Oct 04, 2026 at 07:52:03PM +0300, Svyatoslav Ryhel wrote:
> > > > Move all Tegra-specific Chipidea devices and their properties into a
> > > > dedicated schema file, by analogy with i.MX.
> > >
> > > I don't really see the point given it is only 2 deprecated properties.
> > > Maybe those can be removed? Depends if they are deprecated and still
> > > used or deprecated and removed from .dts files years ago.
> > >
> >
> > The ci-hdrc-usb2.yaml schema contains properties that are not
> > applicable to Tegra, and conversely, Tegra-specific properties are not
> > applicable to qcom, nxp, nuvoton, etc.
> >
> > The 'nvidia,needs-double-reset' property is required for Tegra20 and
> > Tegra30, and it is still actively in use, as you can see here [1]. Its
> > marked deprecated state appears to be incorrect, as it should simply
> > be restricted to Tegra20 and Tegra30.
>
> For what it's worth, I looked into this a little bit to find out why
> this is only needed on USB1, whereas USB2 and USB3 don't seem to be
> affected. Turns out that USB1 is a different controller than USB2 and
> USB3 and it has this errata. In retrospect it would've been more correct
> to assign a different compatible string for it and derive the quirks
> from that, but given the ABI stability it's probably not worth
> correcting it at this point.
>
> Thierry
Thank you for the explanation. Having a common schema for many cases
is great, but IMHO mixing different SoCs in a basically SoC specific
schema is not the right approach. Having a dedicated Tegra version
like i.MX has seems beneficial.