From: Thierry Reding <thierry.reding@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Jordan Viknar <jordanviknar@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: usb: Move Tegra-specific Chipidea USB properties into a dedicated schema
Date: Tue, 17 Nov 2026 13:40:32 +0100 [thread overview]
Message-ID: <avxHzF-uiOAhwXIW@orome> (raw)
In-Reply-To: <CAPVz0n2rkWikz1CZhkKiZnX5P+NdDH0RfJi69AyVTEV7qw_VXg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
On Tue, Oct 27, 2026 at 10:51:52AM +0200, Svyatoslav Ryhel wrote:
> вт, 27 жовт. 2026 р. о 00:29 Rob Herring <robh@kernel.org> пише:
> >
> > 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-17 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 16:52 [PATCH v1 0/2] usb: tegra: separate schema and adjust OTG logic Svyatoslav Ryhel
2026-10-04 16:52 ` [PATCH v1 1/2] dt-bindings: usb: Move Tegra-specific Chipidea USB properties into a dedicated schema Svyatoslav Ryhel
2026-10-26 22:29 ` Rob Herring
2026-10-27 8:51 ` Svyatoslav Ryhel
2026-10-27 11:50 ` Rob Herring
2026-11-17 12:40 ` Thierry Reding [this message]
2026-10-04 16:52 ` [PATCH v1 2/2] usb: phy: tegra: Disable internal USB sensing if extcon is used Svyatoslav Ryhel
2026-10-04 17:05 ` sashiko-bot
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=avxHzF-uiOAhwXIW@orome \
--to=thierry.reding@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=jordanviknar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh@kernel.org \
/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.