From: Jon Hunter <jonathanh@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Nagarjuna Kristam <nkristam@nvidia.com>,
JC Kuo <jckuo@nvidia.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, Thierry Reding <treding@nvidia.com>,
Wayne Chang <waynec@nvidia.com>
Subject: Re: [PATCH 1/9] dt-bindings: usb: Add Tegra238 XUSB host controller support
Date: Mon, 28 Sep 2026 14:57:34 +0100 [thread overview]
Message-ID: <0c5b19f3-9ac8-452e-97be-0256aa0ccb0e@nvidia.com> (raw)
In-Reply-To: <20260925-alligator-of-authentic-economy-f631fd@quoll>
On 25/09/2026 14:27, Krzysztof Kozlowski wrote:
> On Mon, Sep 21, 2026 at 01:19:01PM +0100, Jon Hunter wrote:
>> Add a compatible string for the Tegra238 XUSB host controller. The
>> Tegra238 XUSB host controller is similar to that found on the Tegra234
>> device but only supports 3 PHYs compared to the 4 PHYs on the Tegra234.
>> Hence, the binding is also updated to limit the number of PHYs that can
>> be specified for the Tegra238 device.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> .../bindings/usb/nvidia,tegra234-xusb.yaml | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml b/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml
>> index 3f56110be915..9d605db7e77f 100644
>> --- a/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml
>> +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml
>> @@ -19,6 +19,7 @@ properties:
>> compatible:
>> enum:
>> - nvidia,tegra234-xusb
>> + - nvidia,tegra238-xusb
>> - nvidia,tegra264-xusb
>>
>> reg:
>> @@ -154,6 +155,25 @@ properties:
>>
>> allOf:
>> - $ref: usb-xhci.yaml
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: nvidia,tegra238-xusb
>> + then:
>> + properties:
>> + phys:
>
> minItems: to be explicit. I would expect minItems: 6, but your phy-names
> is flexible, so probably wording in your commit msg should be "*up to* 3
> PHYs compared to the...."
ACK. I will update the commit message to make this clear that this is
'up to 3 PHYs'.
Jon
--
nvpublic
next prev parent reply other threads:[~2026-09-28 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 12:19 [PATCH 0/9] usb: Add support for Tegra238 and device support for Tegra264 Jon Hunter
2026-09-21 12:19 ` [PATCH 1/9] dt-bindings: usb: Add Tegra238 XUSB host controller support Jon Hunter
2026-09-25 13:27 ` Krzysztof Kozlowski
2026-09-28 13:57 ` Jon Hunter [this message]
2026-10-02 15:21 ` Jon Hunter
2026-09-21 12:19 ` [PATCH 2/9] dt-bindings: usb: tegra-xudc: Add Tegra238 XUDC support Jon Hunter
2026-09-25 13:28 ` Krzysztof Kozlowski
2026-10-02 15:23 ` Jon Hunter
2026-09-21 12:19 ` [PATCH 3/9] dt-bindings: usb: tegra-xudc: Add Tegra264 " Jon Hunter
2026-09-25 13:28 ` Krzysztof Kozlowski
2026-09-21 12:19 ` [PATCH 4/9] usb: xhci: tegra: Add support for Tegra238 Jon Hunter
2026-09-21 12:19 ` [PATCH 5/9] usb: gadget: tegra-xudc: Fix CNT65 configuration Jon Hunter
2026-09-21 12:19 ` [PATCH 6/9] usb: gadget: tegra-xudc: Add support for Tegra238 Jon Hunter
2026-09-21 12:19 ` [PATCH 7/9] usb: gadget: tegra-xudc: Add SSPX register offset to SoC data Jon Hunter
2026-09-21 12:19 ` [PATCH 8/9] usb: gadget: tegra-xudc: Add default settings " Jon Hunter
2026-09-21 12:19 ` [PATCH 9/9] usb: gadget: tegra-xudc: Add support for Tegra264 Jon Hunter
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=0c5b19f3-9ac8-452e-97be-0256aa0ccb0e@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jckuo@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=nkristam@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@kernel.org \
--cc=treding@nvidia.com \
--cc=waynec@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox