From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
JC Kuo <jckuo@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Wayne Chang <waynec@nvidia.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: phy: tegra194: Add compatible for Tegra238
Date: Fri, 25 Sep 2026 15:31:07 +0200 [thread overview]
Message-ID: <20260925-new-academic-lyrebird-ce1a52@quoll> (raw)
In-Reply-To: <20260921-tegra-phy-v1-1-83466bf9a7cd@nvidia.com>
On Mon, Sep 21, 2026 at 01:14:45PM +0100, Jon Hunter wrote:
> The Tegra238 XUSB pad controller is similar to that found on the
> Tegra194 and Tegra234, but only has three USB2 ports and three USB3
> ports.
>
> Add the Tegra238 compatible string for the XUSB pad controller and
> constrain the binding so that a Tegra238 device tree can only have three
> USB2 and three USB3 ports.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> .../bindings/phy/nvidia,tegra194-xusb-padctl.yaml | 38 ++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-25 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 12:14 [PATCH 0/3] phy: tegra: xusb: Add Tegra238 support Jon Hunter
2026-09-21 12:14 ` [PATCH 1/3] dt-bindings: phy: tegra194: Add compatible for Tegra238 Jon Hunter
2026-09-25 13:31 ` Krzysztof Kozlowski [this message]
2026-09-21 12:14 ` [PATCH 2/3] phy: tegra: xusb: Use dev_err_probe() Jon Hunter
2026-09-23 6:36 ` Jon Hunter
2026-09-21 12:14 ` [PATCH 3/3] phy: tegra: Add support for Tegra238 XUSB pad controller 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=20260925-new-academic-lyrebird-ce1a52@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=thierry.reding@kernel.org \
--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