From: Pawel Laszczak via B4 Relay <devnull+pawell.cadence.com@kernel.org>
To: Peter Chen <peter.chen@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pawel Laszczak <pawell@cadence.com>
Subject: [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property
Date: Tue, 12 May 2026 13:44:24 +0200 [thread overview]
Message-ID: <20260512-b4-no_drd_config-v4-1-7b4e5dc96f81@cadence.com> (raw)
In-Reply-To: <20260512-b4-no_drd_config-v4-0-7b4e5dc96f81@cadence.com>
From: Pawel Laszczak <pawell@cadence.com>
Introduce a new boolean property 'no_drd' for Cadence USBSS/USBSSP
controllers.
Some hardware configurations of this controller are designed without
the Dual-Role Device (DRD) register block or have it inaccessible.
In such cases, the driver must skip all OTG/DRD register accesses
to avoid bus errors and cannot rely on hardware-based role switching.
To accommodate these configurations, also relax the requirements for
the 'reg' and 'interrupts' properties, making the 'otg' resources
optional.
Signed-off-by: Pawel Laszczak <pawell@cadence.com>
---
Documentation/devicetree/bindings/usb/cdns,usb3.yaml | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
index 2d95fb7321af..8c7dc81708fb 100644
--- a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
+++ b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
@@ -20,19 +20,21 @@ properties:
const: cdns,usb3
reg:
+ minItems: 2
items:
- description: OTG controller registers
- description: XHCI Host controller registers
- description: DEVICE controller registers
reg-names:
+ minItems: 2
items:
- const: otg
- const: xhci
- const: dev
interrupts:
- minItems: 3
+ minItems: 2
items:
- description: XHCI host controller interrupt
- description: Device controller interrupt
@@ -41,7 +43,7 @@ properties:
cleared by xhci core, this interrupt is optional
interrupt-names:
- minItems: 3
+ minItems: 2
items:
- const: host
- const: peripheral
@@ -79,6 +81,13 @@ properties:
description: Enable resetting of PHY if Rx fail is detected
type: boolean
+ no_drd:
+ description:
+ Indicates that the Dual-Role Device (DRD) register block is not
+ implemented or is inaccessible. In this case, the controller
+ must operate in a fixed peripheral or host mode.
+ type: boolean
+
dependencies:
port: [ usb-role-switch ]
--
2.43.0
next prev parent reply other threads:[~2026-05-12 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 11:44 [PATCH v4 0/2] usb: cdns3: support configurations without DRD block Pawel Laszczak via B4 Relay
2026-05-12 11:44 ` Pawel Laszczak via B4 Relay [this message]
2026-05-12 17:10 ` [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property Conor Dooley
2026-05-12 11:44 ` [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration Pawel Laszczak via B4 Relay
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=20260512-b4-no_drd_config-v4-1-7b4e5dc96f81@cadence.com \
--to=devnull+pawell.cadence.com@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=peter.chen@kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
/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