From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jon Hunter <jonathanh@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Vinod Koul <vkoul@kernel.org>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-phy@lists.infradead.org,
waynec@nvidia.com, Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH V5 1/6] dt-bindings: usb: Add NVIDIA Tegra234 XUSB host controller binding
Date: Mon, 9 Jan 2023 19:46:35 +0100 [thread overview]
Message-ID: <101fbe16-69f0-d0c1-168a-1e267e22289d@linaro.org> (raw)
In-Reply-To: <73bfb6ca-663e-b73c-b9a1-4727ae7217d1@nvidia.com>
On 09/01/2023 18:00, Jon Hunter wrote:
>
> On 08/01/2023 15:21, Krzysztof Kozlowski wrote:
>
> ...
>
>> On 06/01/2023 16:28, Jon Hunter wrote:
>>> + phys:
>>> + minItems: 1
>>> + maxItems: 8
>>> +
>>> + phy-names:
>>> + minItems: 1
>>> + maxItems: 8
>>> + items:
>>> + enum:
>>> + - usb2-0
>>> + - usb2-1
>>> + - usb2-2
>>> + - usb2-3
>>> + - usb3-0
>>> + - usb3-1
>>> + - usb3-2
>>> + - usb3-3
>>
>> Why do you have so many optional phys? In what case you would put there
>> usb2-0 and usb3-3 together? Or even 8 phys at the same time? IOW, what
>> are the differences between them and why one controller would be
>> connected once to usb3-2 and once to usb3-3 phy? And once to both?
>
>
> Here is the description from the device documentation ...
>
> "The NVIDIA Orin series System-on-Chip (SoC) has one xHCI host
> controller and one USB 3.2 Gen1 x1 device controller. The two
> controllers control a total of up to eight exposed ports. There are up
> to four USB 2.0 ports and up to four USB 3.2 Gen1 x1 ports."
>
> So there are eight phys and we could have 4 USB2 and 4 USB3. Depending
> on which pins you want to use, you could have various combinations. I
> can add these details to the binding doc if that helps.
Yeah, could solve some questions.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-09 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 15:28 [PATCH V5 0/6] Enable USB host on Jetson AGX Orin Jon Hunter
2023-01-06 15:28 ` [PATCH V5 1/6] dt-bindings: usb: Add NVIDIA Tegra234 XUSB host controller binding Jon Hunter
2023-01-08 15:21 ` Krzysztof Kozlowski
2023-01-09 13:22 ` Thierry Reding
2023-01-09 17:00 ` Jon Hunter
2023-01-09 18:46 ` Krzysztof Kozlowski [this message]
2023-01-06 15:28 ` [PATCH V5 2/6] dt-bindings: phy: tegra-xusb: Add support for Tegra234 Jon Hunter
2023-01-08 15:21 ` Krzysztof Kozlowski
2023-01-06 15:28 ` [PATCH V5 3/6] arm64: tegra: Enable XUSB host function on Jetson AGX Orin Jon Hunter
2023-01-06 15:28 ` [PATCH V5 4/6] phy: tegra: xusb: Disable trk clk when not in use Jon Hunter
2023-01-06 15:28 ` [PATCH V5 5/6] phy: tegra: xusb: Add Tegra234 support Jon Hunter
2023-01-06 15:28 ` [PATCH V5 6/6] usb: host: xhci-tegra: Add Tegra234 XHCI support 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=101fbe16-69f0-d0c1-168a-1e267e22289d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=vkoul@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).