Re: [PATCH v1 1/2] dt-bindings: usb: Move Tegra-specific Chipidea USB properties into a dedicated schema
From: Rob Herring
Date: Tue Oct 27 2026 - 07:57:05 EST
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.
>
> The 'nvidia,phy' property is still used across all ARMv7 Tegra
> generations + Tegra210, as the Chipidea driver has not yet been
> converted to use the generic property. Therefore, while it is marked
> as deprecated, it remains in active use.
>
> The example I added is from Tegra30, which in the real devicetree uses
> both properties, so I've included them here as well. With your
> permission, I can remove the Tegra-specific parts from
> ci-hdrc-usb2.yaml and tailor the proposed schema to better fit the
> current state.
Okay, please add these details to the commit msg.
Rob