From: Rob Herring <robh@kernel.org>
To: Pawel Laszczak <pawell@cadence.com>
Cc: Peter Chen <peter.chen@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] dt-bindings: usb: cdns3: Add cdns,no-drd property
Date: Thu, 14 May 2026 08:39:07 -0500 [thread overview]
Message-ID: <20260514133907.GA173132-robh@kernel.org> (raw)
In-Reply-To: <20260514-b4-no_drd_config-v7-1-18cc40e363fd@cadence.com>
On Thu, May 14, 2026 at 08:00:51AM +0200, Pawel Laszczak wrote:
> Introduce a new boolean property 'cdns,no-drd' for Cadence USBSS/USBSSP
> controllers to support hardware configurations where the Dual-Role
> Device (DRD) register block is missing or inaccessible.
>
> When 'cdns,no-drd' is present:
> - The 'otg' register and interrupt resources are not required.
> - The 'reg' and 'interrupts' properties are restricted to 2 items
> (host and device).
> - 'dr_mode' must be explicitly set to either 'host' or 'peripheral'.
>
> When 'cdns,no-drd' is absent, the binding maintains backward compatibility
> by requiring all 3 resource sets (otg, host, dev).
>
> To achieve this, the schema is updated with an if-then-else logic
> and 'reg-names' use enums to allow flexible
> ordering during validation.
No need for a property here. This should be implied from an SoC specific
compatible. Or perhaps just implied from the lack of 'otg' registers.
Rob
next prev parent reply other threads:[~2026-05-14 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 6:00 [PATCH v7 0/2] usb: cdns3: support configurations without DRD block Pawel Laszczak via B4 Relay
2026-05-14 6:00 ` [PATCH v7 1/2] dt-bindings: usb: cdns3: Add cdns,no-drd property Pawel Laszczak via B4 Relay
2026-05-14 13:39 ` Rob Herring [this message]
2026-05-14 6:00 ` [PATCH v7 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=20260514133907.GA173132-robh@kernel.org \
--to=robh@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=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