From: Jon Hunter <jonathanh@nvidia.com>
To: 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>
Cc: 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>,
Jon Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH v2 0/3] phy: tegra: xusb: Add Tegra238 support
Date: Thu, 1 Oct 2026 14:28:17 +0100 [thread overview]
Message-ID: <20261001-tegra-phy-v2-0-3e453b1fb271@nvidia.com> (raw)
Add support for the Tegra238 device to the Tegra XUSB PHY driver and
add the necessary device-tree binding documentation for this device.
This series also includes a trivial clean-up patch to use the
dev_err_probe() function in the Tegra XUSB PHY driver instead of open
coding this function.
This series is based on top of the series that adds support for the
Tegra264 device to the Tegra XUSB PHY driver [0].
[0] https://lore.kernel.org/linux-tegra/20260903071937.533646-1-waynec@nvidia.com/
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
Changes in v2:
- Dropped extra 'err' variable from patch that migrates to dev_err_probe
- Added Krzysztof's Reviewed-by for device-tree binding.
- Link to v1: https://patch.msgid.link/20260921-tegra-phy-v1-0-83466bf9a7cd@nvidia.com
---
Jon Hunter (3):
dt-bindings: phy: tegra194: Add compatible for Tegra238
phy: tegra: xusb: Use dev_err_probe()
phy: tegra: Add support for Tegra238 XUSB pad controller
.../bindings/phy/nvidia,tegra194-xusb-padctl.yaml | 38 ++++++++++++++++++++++
drivers/phy/tegra/xusb-tegra186.c | 29 +++++++++++++----
drivers/phy/tegra/xusb.c | 14 ++++----
drivers/phy/tegra/xusb.h | 3 ++
4 files changed, 71 insertions(+), 13 deletions(-)
---
base-commit: e657a464aba873f5eaf3ca821b6e4016674492d6
change-id: 20260918-tegra-phy-1611f1d54afa
prerequisite-message-id: <20260903071937.533646-1-waynec@nvidia.com>
prerequisite-patch-id: 4d5aee86ddf39567e3751c3e3067d9381635de46
prerequisite-patch-id: 532f630446505f9258dee65ab43887fc3cf877e0
prerequisite-patch-id: 4660a52fe6277f5d91ee70cee0b74280a8ce927e
prerequisite-patch-id: d58ecf03061a3c26f4f0a71f2dd5c97a673e23eb
Best regards,
--
Jon Hunter <jonathanh@nvidia.com>
next reply other threads:[~2026-10-01 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:28 Jon Hunter [this message]
2026-10-01 13:28 ` [PATCH v2 1/3] dt-bindings: phy: tegra194: Add compatible for Tegra238 Jon Hunter
2026-10-01 13:28 ` [PATCH v2 2/3] phy: tegra: xusb: Use dev_err_probe() Jon Hunter
2026-10-01 13:28 ` [PATCH v2 3/3] phy: tegra: Add support for Tegra238 XUSB pad controller Jon Hunter
2026-10-03 14:31 ` [PATCH v2 0/3] phy: tegra: xusb: Add Tegra238 support Vinod Koul
2026-10-07 14:46 ` 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=20261001-tegra-phy-v2-0-3e453b1fb271@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jckuo@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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