From: Jon Hunter <jonathanh@nvidia.com>
To: 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>
Cc: 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>,
Jon Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH v2 00/12] usb: Add support for Tegra238 and device support for Tegra264
Date: Mon, 16 Nov 2026 15:23:57 +0000 [thread overview]
Message-ID: <20261116-tegra-usb-v2-0-42efc03a9700@nvidia.com> (raw)
Add USB device and host support for the Tegra238 device and add
USB device support for the Tegra264 device. USB host support for
Tegra264 is already present in the base tree.
The series adds the necessary device-tree binding updates for these
devices and adds the SoC data to the USB drivers. For the Tegra264 USB
device, the register offsets and default settings differ from previous
generations and so the driver has been updated accordingly.
The series also fixes CNT65 register programming and preserves runtime
PM state across system suspend in the Tegra XUDC driver, and replaces an
unintended comma with a semicolon in the Tegra XHCI driver.
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
Changes in v2:
- Added a patch documenting required properties for the Tegra234 XUSB
binding.
- Updated Tegra238 XHCI and XUDC bindings to require resets instead of
power domains.
- Limited Tegra238 XHCI bindings to eight interrupts and one IOMMU entry,
and clarified the PHY counts in the binding commit messages.
- Updated Tegra238 XHCI and XUDC drivers to manage resets directly.
- Added a patch replacing an unintended comma with a semicolon in the
XHCI driver.
- Extended the CNT65 fix to cover both limiting and restoring port speed.
- Added a patch preserving XUDC runtime PM state across system suspend.
- Link to v1: https://patch.msgid.link/20260921-tegra-usb-v1-0-74a925a35d82@nvidia.com
---
Jon Hunter (12):
dt-bindings: usb: tegra234-xusb: Add required properties
dt-bindings: usb: Add Tegra238 XUSB host controller support
dt-bindings: usb: tegra-xudc: Add Tegra238 XUDC support
dt-bindings: usb: tegra-xudc: Add Tegra264 XUDC support
usb: xhci: tegra: Fix missing semi-colon
usb: xhci: tegra: Add support for Tegra238
usb: gadget: tegra-xudc: Fix CNT65 configuration
usb: gadget: tegra-xudc: Preserve runtime PM across system suspend
usb: gadget: tegra-xudc: Add support for Tegra238
usb: gadget: tegra-xudc: Add SSPX register offset to SoC data
usb: gadget: tegra-xudc: Add default settings to SoC data
usb: gadget: tegra-xudc: Add support for Tegra264
.../devicetree/bindings/usb/nvidia,tegra-xudc.yaml | 38 ++-
.../bindings/usb/nvidia,tegra234-xusb.yaml | 57 ++++
drivers/usb/gadget/udc/tegra-xudc.c | 339 ++++++++++++++++-----
drivers/usb/host/xhci-tegra.c | 115 +++++--
4 files changed, 449 insertions(+), 100 deletions(-)
---
base-commit: 84abb955b1015477aa11a96e2f3ac1b938b77f48
change-id: 20260918-tegra-usb-58d1d80e4797
Best regards,
--
Jon Hunter <jonathanh@nvidia.com>
next reply other threads:[~2026-11-16 15:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 15:23 Jon Hunter [this message]
2026-11-16 15:23 ` [PATCH v2 01/12] dt-bindings: usb: tegra234-xusb: Add required properties Jon Hunter
2026-11-16 15:33 ` sashiko-bot
2026-11-16 15:23 ` [PATCH v2 02/12] dt-bindings: usb: Add Tegra238 XUSB host controller support Jon Hunter
2026-11-16 15:38 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 03/12] dt-bindings: usb: tegra-xudc: Add Tegra238 XUDC support Jon Hunter
2026-11-16 15:32 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 04/12] dt-bindings: usb: tegra-xudc: Add Tegra264 " Jon Hunter
2026-11-16 15:32 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 05/12] usb: xhci: tegra: Fix missing semi-colon Jon Hunter
2026-11-16 15:30 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 06/12] usb: xhci: tegra: Add support for Tegra238 Jon Hunter
2026-11-16 15:36 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 07/12] usb: gadget: tegra-xudc: Fix CNT65 configuration Jon Hunter
2026-11-16 15:29 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 08/12] usb: gadget: tegra-xudc: Preserve runtime PM across system suspend Jon Hunter
2026-11-16 15:36 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 09/12] usb: gadget: tegra-xudc: Add support for Tegra238 Jon Hunter
2026-11-16 15:24 ` [PATCH v2 10/12] usb: gadget: tegra-xudc: Add SSPX register offset to SoC data Jon Hunter
2026-11-16 15:32 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 11/12] usb: gadget: tegra-xudc: Add default settings " Jon Hunter
2026-11-16 15:34 ` sashiko-bot
2026-11-16 15:24 ` [PATCH v2 12/12] usb: gadget: tegra-xudc: Add support for Tegra264 Jon Hunter
2026-11-16 15:35 ` 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=20261116-tegra-usb-v2-0-42efc03a9700@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=krzysztof.kozlowski@oss.qualcomm.com \
--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