* [PATCH v4 0/2] usb: cdns3: support configurations without DRD block
@ 2026-05-12 11:44 Pawel Laszczak via B4 Relay
2026-05-12 11:44 ` [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property Pawel Laszczak via B4 Relay
2026-05-12 11:44 ` [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration Pawel Laszczak via B4 Relay
0 siblings, 2 replies; 6+ messages in thread
From: Pawel Laszczak via B4 Relay @ 2026-05-12 11:44 UTC (permalink / raw)
To: Peter Chen, Roger Quadros, Greg Kroah-Hartman, Rob Herring,
Krzysztof Kozlowski, Conor Dooley
Cc: linux-usb, devicetree, linux-kernel, Pawel Laszczak,
Bjorn Helgaas
usb: cdns3: support configurations without DRD block
This series adds support for Cadence USBSSP controllers in hardware
layouts where the Dual-Role Device (DRD) register block is either
missing or inaccessible.
In such configurations, the controller is hardwired to a single role
(either host or device) and the driver must skip all OTG/DRD register
accesses to avoid bus errors or incorrect role detection.
The solution introduces a new 'no_drd' property that can be passed
via DT or software nodes. When set, the driver:
1. Skips DRD register mapping and IRQ requests.
2. Uses a different BAR indexing logic for PCI-based configurations
(32-bit addressing layout).
3. Hardwires the role based on 'dr_mode'.
Signed-off-by: Pawel Laszczak <pawell@cadence.com>
---
Note: This series is based on current linux-next. I am aware of Peter
Chen's recent refactoring series ("usb: cdns3: plat: Expose platform
core driver as library"). Although there is a minor conflict in
cdns3-plat.c, Peter has already provided an Acked-by for this version.
I am happy to provide a rebased v5 as soon as Peter's changes land in
linux-next if required.
---
v4:
- Added DT binding documentation for the 'no_drd' property.
- Relaxed 'reg' and 'interrupts' requirements in the DT schema (minItems 2)
to allow configurations where the OTG/DRD register block is missing,
- Moved PCI_DEVICE_ID_CDNS_UDC_USBSSP from pci_ids.h to cdnsp-pci.c
to keep the global PCI ID list clean.
v3:
- Improved descriptions and comments for better clarity.
- Introduced the 'no_drd' property to indicate missing DRD register block.
- Added support for fixed host-only and device-only configurations.
- Ensured cdns_otg_disable_irq is called only when no_drd is false.
- Updated cdns_drd_gadget_on/off to ensure PHY mode is correctly
handled even if DRD is disabled.
v2:
- Changed otg_irq to be optionali.
- Added cdns->no_drd check in cdns_power_is_lost.
- Added cdns->no_drd check in cdns_get_id.
---
Pawel Laszczak (2):
dt-bindings: usb: cdns3: Add no_drd property
usb: cdnsp: Add support for device-only configuration
.../devicetree/bindings/usb/cdns,usb3.yaml | 13 +++++-
drivers/usb/cdns3/cdns3-plat.c | 26 +++++++-----
drivers/usb/cdns3/cdnsp-pci.c | 47 +++++++++++++++++-----
drivers/usb/cdns3/core.c | 3 +-
drivers/usb/cdns3/core.h | 4 ++
drivers/usb/cdns3/drd.c | 44 +++++++++++++++++++-
6 files changed, 112 insertions(+), 25 deletions(-)
---
base-commit: e98d21c170b01ddef366f023bbfcf6b31509fa83
change-id: 20260512-b4-no_drd_config-f530f1f16d8a
Best regards,
--
Pawel Laszczak <pawell@cadence.com>
^ permalink raw reply [flat|nested] 6+ messages in thread* [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property 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 2026-05-12 17:10 ` Conor Dooley 2026-05-13 20:42 ` sashiko-bot 2026-05-12 11:44 ` [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration Pawel Laszczak via B4 Relay 1 sibling, 2 replies; 6+ messages in thread From: Pawel Laszczak via B4 Relay @ 2026-05-12 11:44 UTC (permalink / raw) To: Peter Chen, Roger Quadros, Greg Kroah-Hartman, Rob Herring, Krzysztof Kozlowski, Conor Dooley Cc: linux-usb, devicetree, linux-kernel, Pawel Laszczak 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 ^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property 2026-05-12 11:44 ` [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property Pawel Laszczak via B4 Relay @ 2026-05-12 17:10 ` Conor Dooley 2026-05-13 20:42 ` sashiko-bot 1 sibling, 0 replies; 6+ messages in thread From: Conor Dooley @ 2026-05-12 17:10 UTC (permalink / raw) To: pawell Cc: Peter Chen, Roger Quadros, Greg Kroah-Hartman, Rob Herring, Krzysztof Kozlowski, Conor Dooley, linux-usb, devicetree, linux-kernel [-- Attachment #1: Type: text/plain, Size: 2878 bytes --] On Tue, May 12, 2026 at 01:44:24PM +0200, Pawel Laszczak via B4 Relay wrote: > 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. Why unconditionally? I think these hardware configurations need device-specific compatibles and the constraints lowered on a case-by-case basis. Probably those compatibles should require no_drd too. Alternatively to doing the conditions per compatible, if no_drd is present, maxItems for these properties should be set to 2, and when absent minItems set to 3. pw-bot: changes-requested Thanks, Conor. > > 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 > > [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property 2026-05-12 11:44 ` [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property Pawel Laszczak via B4 Relay 2026-05-12 17:10 ` Conor Dooley @ 2026-05-13 20:42 ` sashiko-bot 1 sibling, 0 replies; 6+ messages in thread From: sashiko-bot @ 2026-05-13 20:42 UTC (permalink / raw) To: Pawel Laszczak via B4 Relay; +Cc: krzk+dt, robh, conor+dt, devicetree Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider: - [High] Schema logic error: lowering `minItems` does not make leading or intermediate array items optional, breaking schema validation when `otg` resources are omitted. - [Low] The new property `no_drd` violates standard Device Tree property naming conventions. - [Low] The schema fails to enforce the operational mode restrictions introduced by the `no_drd` property. -- commit 56705b83ac8b4d7657f3b9eca696b4b8d5225cc7 Author: Pawel Laszczak <pawell@cadence.com> dt-bindings: usb: cdns3: Add no_drd property This commit introduces a new boolean property 'no_drd' for Cadence USBSS/USBSSP controllers to support hardware configurations without a Dual-Role Device (DRD) register block. It also relaxes the 'reg' and 'interrupts' properties requirements to make the 'otg' resources optional. > diff --git a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml > index 2d95fb7321aff..8c7dc81708fb5 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 Does lowering minItems actually make the leading 'otg' resource optional? In JSON Schema, array tuple validation matches elements strictly by their index order. For reg-names, the schema expects 'otg' at index 0 and 'xhci' at index 1. Lowering minItems to 2 only makes the trailing element ('dev') optional. If a device tree omits the 'otg' resource to indicate no DRD block, and provides reg-names = "xhci", "dev", validation will fail because the first provided element ("xhci") will be evaluated against const: otg. To correctly allow omitting specific positional resources, does the schema need a oneOf construct with explicitly defined arrays of allowed combinations? [ ... ] > interrupt-names: > - minItems: 3 > + minItems: 2 > items: > - const: host > - const: peripheral Similarly, if 'otg' is omitted but the optional 'wakeup' interrupt is provided, validation will fail because 'wakeup' will be evaluated against the third element ('otg'). [ ... ] > @@ -79,6 +81,13 @@ properties: > description: Enable resetting of PHY if Rx fail is detected > type: boolean > > + no_drd: This isn't a bug, but device tree property names typically use hyphens instead of underscores. Since this property describes a hardware-specific design omission for the Cadence USB controller rather than a standard core USB subsystem property, should it use a vendor prefix and hyphens, such as cdns,no-drd, to comply with DT schema standards? > + 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 Does the schema enforce the operational mode restrictions introduced by this property? The description explicitly states that the controller must operate in a fixed peripheral or host mode. However, the schema does not enforce this functional requirement. Could an allOf block be added to the schema to restrict the dr_mode property to enum: [host, peripheral] and explicitly forbid usb-role-switch when this property is present? -- Sashiko AI review · https://sashiko.dev/#/patchset/20260512-b4-no_drd_config-v4-0-7b4e5dc96f81@cadence.com?part=1 ^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration 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 ` [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property Pawel Laszczak via B4 Relay @ 2026-05-12 11:44 ` Pawel Laszczak via B4 Relay 2026-05-13 21:04 ` sashiko-bot 1 sibling, 1 reply; 6+ messages in thread From: Pawel Laszczak via B4 Relay @ 2026-05-12 11:44 UTC (permalink / raw) To: Peter Chen, Roger Quadros, Greg Kroah-Hartman, Rob Herring, Krzysztof Kozlowski, Conor Dooley Cc: linux-usb, devicetree, linux-kernel, Pawel Laszczak, Bjorn Helgaas From: Pawel Laszczak <pawell@cadence.com> This patch introduces support for the Cadence USBSSP (cdnsp) controller in hardware configurations where the Dual-Role Device (DRD) register block is not implemented or is inaccessible. In such cases, the driver cannot rely on the DRD logic to manage roles and must operate exclusively in a fixed peripheral/host mode. The change in BAR indexing (from BAR 2 to BAR 1) is a direct consequence of the 32-bit addressing used in this specific DRD-disabled hardware layout, compared to the 64-bit addressing used in DRD-enabled configurations. Tested on a PCI platform with a hardware configuration that lacks DRD support. Platform-side changes are included to support the PCI glue layer's property injection to handle this specific layout. Acked-by: Peter Chen <peter.chen@kernel.org> Acked-by: Bjorn Helgaas <bhelgaas@google.com> Signed-off-by: Pawel Laszczak <pawell@cadence.com> --- drivers/usb/cdns3/cdns3-plat.c | 26 +++++++++++++---------- drivers/usb/cdns3/cdnsp-pci.c | 47 ++++++++++++++++++++++++++++++++++-------- drivers/usb/cdns3/core.c | 3 ++- drivers/usb/cdns3/core.h | 4 ++++ drivers/usb/cdns3/drd.c | 44 +++++++++++++++++++++++++++++++++++++-- 5 files changed, 101 insertions(+), 23 deletions(-) diff --git a/drivers/usb/cdns3/cdns3-plat.c b/drivers/usb/cdns3/cdns3-plat.c index 3fe3109a3688..86c963a072db 100644 --- a/drivers/usb/cdns3/cdns3-plat.c +++ b/drivers/usb/cdns3/cdns3-plat.c @@ -81,6 +81,7 @@ static int cdns3_plat_probe(struct platform_device *pdev) if (cdns->pdata && cdns->pdata->override_apb_timeout) cdns->override_apb_timeout = cdns->pdata->override_apb_timeout; + cdns->no_drd = device_property_read_bool(dev, "no_drd"); platform_set_drvdata(pdev, cdns); ret = platform_get_irq_byname(pdev, "host"); @@ -113,21 +114,24 @@ static int cdns3_plat_probe(struct platform_device *pdev) cdns->dev_regs = regs; - cdns->otg_irq = platform_get_irq_byname(pdev, "otg"); - if (cdns->otg_irq < 0) - return dev_err_probe(dev, cdns->otg_irq, - "Failed to get otg IRQ\n"); - - res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "otg"); - if (!res) { - dev_err(dev, "couldn't get otg resource\n"); - return -ENXIO; + if (!cdns->no_drd) { + cdns->otg_irq = platform_get_irq_byname(pdev, "otg"); + if (cdns->otg_irq < 0) + return dev_err_probe(dev, cdns->otg_irq, + "Failed to get otg IRQ\n"); + + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "otg"); + if (!res) { + dev_err(dev, "couldn't get otg resource\n"); + return -ENXIO; + } + cdns->otg_res = *res; + } else { + dev_dbg(dev, "No DRD support\n"); } cdns->phyrst_a_enable = device_property_read_bool(dev, "cdns,phyrst-a-enable"); - cdns->otg_res = *res; - cdns->wakeup_irq = platform_get_irq_byname_optional(pdev, "wakeup"); if (cdns->wakeup_irq == -EPROBE_DEFER) return cdns->wakeup_irq; diff --git a/drivers/usb/cdns3/cdnsp-pci.c b/drivers/usb/cdns3/cdnsp-pci.c index 432007cfe695..feb916229870 100644 --- a/drivers/usb/cdns3/cdnsp-pci.c +++ b/drivers/usb/cdns3/cdnsp-pci.c @@ -19,6 +19,7 @@ struct cdnsp_wrap { struct platform_device *plat_dev; + struct property_entry prop[3]; struct resource dev_res[6]; int devfn; }; @@ -29,10 +30,15 @@ struct cdnsp_wrap { #define RES_HOST_ID 3 #define RES_DEV_ID 4 #define RES_DRD_ID 5 - +/* DRD PCI configuration - 64-bit addressing */ +/* First PCI function */ #define PCI_BAR_HOST 0 -#define PCI_BAR_OTG 0 #define PCI_BAR_DEV 2 +/* Second PCI function */ +#define PCI_BAR_OTG 0 +/* Device only PCI configuration - 32-bit addressing */ +/* First PCI function */ +#define PCI_BAR_ONLY_DEV 1 #define PCI_DEV_FN_HOST_DEVICE 0 #define PCI_DEV_FN_OTG 1 @@ -40,6 +46,7 @@ struct cdnsp_wrap { #define PCI_DRIVER_NAME "cdns-pci-usbssp" #define PLAT_DRIVER_NAME "cdns-usb3" +#define PCI_DEVICE_ID_CDNS_UDC_USBSSP 0x0400 #define CHICKEN_APB_TIMEOUT_VALUE 0x1C20 static struct pci_dev *cdnsp_get_second_fun(struct pci_dev *pdev) @@ -65,6 +72,7 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, struct cdnsp_wrap *wrap; struct resource *res; struct pci_dev *func; + bool no_drd = false; int ret = 0; /* @@ -75,11 +83,14 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, pdev->devfn != PCI_DEV_FN_OTG)) return -EINVAL; + if (pdev->device == PCI_DEVICE_ID_CDNS_UDC_USBSSP) + no_drd = true; + func = cdnsp_get_second_fun(pdev); - if (!func) + if (!func && !no_drd) return -EINVAL; - if (func->class == PCI_CLASS_SERIAL_USB_XHCI || + if ((func && func->class == PCI_CLASS_SERIAL_USB_XHCI) || pdev->class == PCI_CLASS_SERIAL_USB_XHCI) { ret = -EINVAL; goto put_pci; @@ -93,7 +104,7 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, pci_set_master(pdev); - if (pci_is_enabled(func)) { + if (func && pci_is_enabled(func)) { wrap = pci_get_drvdata(func); } else { wrap = kzalloc_obj(*wrap); @@ -106,10 +117,12 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, res = wrap->dev_res; if (pdev->devfn == PCI_DEV_FN_HOST_DEVICE) { + int bar_dev = no_drd ? PCI_BAR_ONLY_DEV : PCI_BAR_DEV; + /* Function 0: host(BAR_0) + device(BAR_2). */ dev_dbg(&pdev->dev, "Initialize Device resources\n"); - res[RES_DEV_ID].start = pci_resource_start(pdev, PCI_BAR_DEV); - res[RES_DEV_ID].end = pci_resource_end(pdev, PCI_BAR_DEV); + res[RES_DEV_ID].start = pci_resource_start(pdev, bar_dev); + res[RES_DEV_ID].end = pci_resource_end(pdev, bar_dev); res[RES_DEV_ID].name = "dev"; res[RES_DEV_ID].flags = IORESOURCE_MEM; dev_dbg(&pdev->dev, "USBSSP-DEV physical base addr: %pa\n", @@ -145,9 +158,20 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, wrap->dev_res[RES_IRQ_OTG_ID].flags = IORESOURCE_IRQ; } - if (pci_is_enabled(func)) { + if (no_drd || pci_is_enabled(func)) { + u8 idx = 0; + /* set up platform device info */ pdata.override_apb_timeout = CHICKEN_APB_TIMEOUT_VALUE; + + if (no_drd) { + wrap->prop[idx++] = PROPERTY_ENTRY_STRING("dr_mode", "peripheral"); + wrap->prop[idx++] = PROPERTY_ENTRY_BOOL("no_drd"); + } else { + wrap->prop[idx++] = PROPERTY_ENTRY_STRING("dr_mode", "otg"); + wrap->prop[idx++] = PROPERTY_ENTRY_BOOL("usb-role-switch"); + } + memset(&plat_info, 0, sizeof(plat_info)); plat_info.parent = &pdev->dev; plat_info.fwnode = pdev->dev.fwnode; @@ -158,6 +182,7 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, plat_info.dma_mask = pdev->dma_mask; plat_info.data = &pdata; plat_info.size_data = sizeof(pdata); + plat_info.properties = wrap->prop; wrap->devfn = pdev->devfn; /* register platform device */ wrap->plat_dev = platform_device_register_full(&plat_info); @@ -185,13 +210,17 @@ static void cdnsp_pci_remove(struct pci_dev *pdev) if (wrap->devfn == pdev->devfn) platform_device_unregister(wrap->plat_dev); - if (!pci_is_enabled(func)) + if (!func || !pci_is_enabled(func)) kfree(wrap); pci_dev_put(func); } static const struct pci_device_id cdnsp_pci_ids[] = { + { PCI_DEVICE(PCI_VENDOR_ID_CDNS, PCI_DEVICE_ID_CDNS_UDC_USBSSP), + .class = PCI_CLASS_SERIAL_USB_DEVICE }, + { PCI_DEVICE(PCI_VENDOR_ID_CDNS, PCI_DEVICE_ID_CDNS_UDC_USBSSP), + .class = PCI_CLASS_SERIAL_USB_CDNS }, { PCI_DEVICE(PCI_VENDOR_ID_CDNS, PCI_DEVICE_ID_CDNS_USBSSP), .class = PCI_CLASS_SERIAL_USB_DEVICE }, { PCI_DEVICE(PCI_VENDOR_ID_CDNS, PCI_DEVICE_ID_CDNS_USBSSP), diff --git a/drivers/usb/cdns3/core.c b/drivers/usb/cdns3/core.c index 6a8d1fefbc0d..504bdf13ea80 100644 --- a/drivers/usb/cdns3/core.c +++ b/drivers/usb/cdns3/core.c @@ -70,7 +70,8 @@ static void cdns_role_stop(struct cdns *cdns) static void cdns_exit_roles(struct cdns *cdns) { cdns_role_stop(cdns); - cdns_drd_exit(cdns); + if (!cdns->no_drd) + cdns_drd_exit(cdns); } /** diff --git a/drivers/usb/cdns3/core.h b/drivers/usb/cdns3/core.h index bca973b999a4..8c492fda924c 100644 --- a/drivers/usb/cdns3/core.h +++ b/drivers/usb/cdns3/core.h @@ -84,6 +84,9 @@ struct cdns3_platform_data { * value in CHICKEN_BITS_3 will be preserved. * @gadget_init: pointer to gadget initialization function * @host_init: pointer to host initialization function + * @no_drd: DRD register block is inaccessible. The controller is hardwired to + * single role (host or device) or the logic for role switching is + * missing. */ struct cdns { struct device *dev; @@ -124,6 +127,7 @@ struct cdns { u32 override_apb_timeout; int (*gadget_init)(struct cdns *cdns); int (*host_init)(struct cdns *cdns); + bool no_drd; }; int cdns_hw_role_switch(struct cdns *cdns); diff --git a/drivers/usb/cdns3/drd.c b/drivers/usb/cdns3/drd.c index 84fb38a5723a..f87cf85cb97a 100644 --- a/drivers/usb/cdns3/drd.c +++ b/drivers/usb/cdns3/drd.c @@ -87,6 +87,9 @@ int cdns_get_id(struct cdns *cdns) { int id; + if (cdns->no_drd) + return 0; + id = readl(&cdns->otg_regs->sts) & OTGSTS_ID_VALUE; dev_dbg(cdns->dev, "OTG ID: %d", id); @@ -107,7 +110,7 @@ void cdns_clear_vbus(struct cdns *cdns) { u32 reg; - if (cdns->version != CDNSP_CONTROLLER_V2) + if (cdns->version != CDNSP_CONTROLLER_V2 || cdns->no_drd) return; reg = readl(&cdns->otg_cdnsp_regs->override); @@ -120,7 +123,7 @@ void cdns_set_vbus(struct cdns *cdns) { u32 reg; - if (cdns->version != CDNSP_CONTROLLER_V2) + if (cdns->version != CDNSP_CONTROLLER_V2 || cdns->no_drd) return; reg = readl(&cdns->otg_cdnsp_regs->override); @@ -181,6 +184,9 @@ int cdns_drd_host_on(struct cdns *cdns) u32 val, ready_bit; int ret; + if (cdns->no_drd) + goto phy_set; + /* Enable host mode. */ writel(OTGCMD_HOST_BUS_REQ | OTGCMD_OTG_DIS, &cdns->otg_regs->cmd); @@ -197,6 +203,7 @@ int cdns_drd_host_on(struct cdns *cdns) if (ret) dev_err(cdns->dev, "timeout waiting for xhci_ready\n"); +phy_set: phy_set_mode(cdns->usb2_phy, PHY_MODE_USB_HOST); phy_set_mode(cdns->usb3_phy, PHY_MODE_USB_HOST); return ret; @@ -210,6 +217,9 @@ void cdns_drd_host_off(struct cdns *cdns) { u32 val; + if (cdns->no_drd) + goto phy_set; + writel(OTGCMD_HOST_BUS_DROP | OTGCMD_DEV_BUS_DROP | OTGCMD_DEV_POWER_OFF | OTGCMD_HOST_POWER_OFF, &cdns->otg_regs->cmd); @@ -218,6 +228,8 @@ void cdns_drd_host_off(struct cdns *cdns) readl_poll_timeout_atomic(&cdns->otg_regs->state, val, !(val & OTGSTATE_HOST_STATE_MASK), 1, 2000000); + +phy_set: phy_set_mode(cdns->usb2_phy, PHY_MODE_INVALID); phy_set_mode(cdns->usb3_phy, PHY_MODE_INVALID); } @@ -234,6 +246,9 @@ int cdns_drd_gadget_on(struct cdns *cdns) u32 ready_bit; int ret, val; + if (cdns->no_drd) + goto phy_set; + /* switch OTG core */ writel(OTGCMD_DEV_BUS_REQ | reg, &cdns->otg_regs->cmd); @@ -251,6 +266,7 @@ int cdns_drd_gadget_on(struct cdns *cdns) return ret; } +phy_set: phy_set_mode(cdns->usb2_phy, PHY_MODE_USB_DEVICE); phy_set_mode(cdns->usb3_phy, PHY_MODE_USB_DEVICE); return 0; @@ -265,6 +281,9 @@ void cdns_drd_gadget_off(struct cdns *cdns) { u32 val; + if (cdns->no_drd) + goto phy_set; + /* * Driver should wait at least 10us after disabling Device * before turning-off Device (DEV_BUS_DROP). @@ -277,6 +296,8 @@ void cdns_drd_gadget_off(struct cdns *cdns) readl_poll_timeout_atomic(&cdns->otg_regs->state, val, !(val & OTGSTATE_DEV_STATE_MASK), 1, 2000000); + +phy_set: phy_set_mode(cdns->usb2_phy, PHY_MODE_INVALID); phy_set_mode(cdns->usb3_phy, PHY_MODE_INVALID); } @@ -392,6 +413,19 @@ int cdns_drd_init(struct cdns *cdns) u32 state, reg; int ret; + if (cdns->no_drd) { + cdns->dr_mode = usb_get_dr_mode(cdns->dev); + cdns->version = CDNSP_CONTROLLER_V2; + + if (cdns->dr_mode != USB_DR_MODE_HOST && + cdns->dr_mode != USB_DR_MODE_PERIPHERAL) { + dev_err(cdns->dev, "Incorrect dr_mode\n"); + return -EINVAL; + } + + return 0; + } + regs = devm_ioremap_resource(cdns->dev, &cdns->otg_res); if (IS_ERR(regs)) return PTR_ERR(regs); @@ -492,6 +526,9 @@ int cdns_drd_init(struct cdns *cdns) int cdns_drd_exit(struct cdns *cdns) { + if (cdns->no_drd) + return 0; + cdns_otg_disable_irq(cdns); return 0; @@ -500,6 +537,9 @@ int cdns_drd_exit(struct cdns *cdns) /* Indicate the cdns3 core was power lost before */ bool cdns_power_is_lost(struct cdns *cdns) { + if (cdns->no_drd) + return false; + if (cdns->version == CDNS3_CONTROLLER_V0) { if (!(readl(&cdns->otg_v0_regs->simulate) & BIT(0))) return true; -- 2.43.0 ^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration 2026-05-12 11:44 ` [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration Pawel Laszczak via B4 Relay @ 2026-05-13 21:04 ` sashiko-bot 0 siblings, 0 replies; 6+ messages in thread From: sashiko-bot @ 2026-05-13 21:04 UTC (permalink / raw) To: Pawel Laszczak via B4 Relay; +Cc: conor+dt, robh, devicetree, krzk+dt Thank you for your contribution! Sashiko AI review found 4 potential issue(s) to consider: - [High] Uninitialized variable returned in cdns_drd_host_on() - [High] Use-After-Free due to improper error handling in cdnsp_pci_probe() - [High] Use-After-Free via sysfs due to failure to unregister usb_role_switch on cdns_core_init_role() error - [High] Race condition in cdnsp_pci_probe() leading to NULL pointer dereference under asynchronous probing -- commit b729274ea9c34ef88a5c2a918206d853477c97a2 Author: Pawel Laszczak <pawell@cadence.com> usb: cdnsp: Add support for device-only configuration This patch introduces support for the Cadence USBSSP (cdnsp) controller in hardware configurations where the Dual-Role Device (DRD) register block is not implemented or is inaccessible. It adjusts BAR indexing, adds a no_drd flag, and skips DRD-specific initializations if no_drd is true. > diff --git a/drivers/usb/cdns3/cdns3-plat.c b/drivers/usb/cdns3/cdns3-plat.c > index 3fe3109a3688a..86c963a072dba 100644 > --- a/drivers/usb/cdns3/cdns3-plat.c > +++ b/drivers/usb/cdns3/cdns3-plat.c > @@ -81,6 +81,7 @@ static int cdns3_plat_probe(struct platform_device *pdev) > if (cdns->pdata && cdns->pdata->override_apb_timeout) > cdns->override_apb_timeout = cdns->pdata->override_apb_timeout; > > + cdns->no_drd = device_property_read_bool(dev, "no_drd"); > platform_set_drvdata(pdev, cdns); This isn't a bug introduced by this patch, but does the error path in this probe function leave a dangling role switch? In cdns3_plat_probe(), cdns_init() registers a USB role switch which stores a pointer to the devm-allocated cdns structure as its driver data. If cdns_core_init_role() fails later in the probe: cdns3_plat_probe() ret = cdns_init(cdns); ... ret = cdns_core_init_role(cdns); if (ret) goto err_cdns_init; err_cdns_init: set_phy_power_off(cdns); ... Is it possible the role switch remains alive and accessible via sysfs without being unregistered, but the underlying cdns structure gets freed by devres, leading to a use-after-free? [ ... ] > diff --git a/drivers/usb/cdns3/cdnsp-pci.c b/drivers/usb/cdns3/cdnsp-pci.c > index 432007cfe6954..feb9162298709 100644 > --- a/drivers/usb/cdns3/cdnsp-pci.c > +++ b/drivers/usb/cdns3/cdnsp-pci.c [ ... ] > @@ -93,7 +104,7 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, > > pci_set_master(pdev); > > - if (pci_is_enabled(func)) { > + if (func && pci_is_enabled(func)) { > wrap = pci_get_drvdata(func); This isn't a bug introduced by this patch, but could this race if asynchronous probing is enabled? If the first function is probed concurrently, it calls pcim_enable_device(), which makes pci_is_enabled(func) evaluate to true for the second function. If the second function reaches here before the first function calls pci_set_drvdata() at the end of its probe, will pci_get_drvdata() return a NULL pointer? If so, could this lead to a NULL pointer dereference immediately following this block when it populates resources via res = wrap->dev_res? [ ... ] > @@ -158,6 +182,7 @@ static int cdnsp_pci_probe(struct pci_dev *pdev, > plat_info.dma_mask = pdev->dma_mask; > plat_info.data = &pdata; > plat_info.size_data = sizeof(pdata); > + plat_info.properties = wrap->prop; > wrap->devfn = pdev->devfn; > /* register platform device */ > wrap->plat_dev = platform_device_register_full(&plat_info); This isn't a bug introduced by this patch, but does the error handling here risk a double-free? If the second PCI function is being probed and platform_device_register_full() fails, the existing error handling does: cdnsp_pci_probe() wrap->plat_dev = platform_device_register_full(&plat_info); if (IS_ERR(wrap->plat_dev)) { ret = PTR_ERR(wrap->plat_dev); kfree(wrap); goto put_pci; } Since wrap was retrieved from the first function's driver data via pci_get_drvdata(), the first function still holds this pointer. When the first function is eventually unbound, will cdnsp_pci_remove() attempt to use and free it again, resulting in a use-after-free? [ ... ] > diff --git a/drivers/usb/cdns3/drd.c b/drivers/usb/cdns3/drd.c > index 84fb38a5723a3..f87cf85cb97a1 100644 > --- a/drivers/usb/cdns3/drd.c > +++ b/drivers/usb/cdns3/drd.c [ ... ] > @@ -181,6 +184,9 @@ int cdns_drd_host_on(struct cdns *cdns) > u32 val, ready_bit; > int ret; > > + if (cdns->no_drd) > + goto phy_set; > + Does this jump bypass the initialization of the return variable? When no_drd is true, the execution jumps to the phy_set label, bypassing the block where ret is populated. [ ... ] > @@ -197,6 +203,7 @@ int cdns_drd_host_on(struct cdns *cdns) > if (ret) > dev_err(cdns->dev, "timeout waiting for xhci_ready\n"); > > +phy_set: > phy_set_mode(cdns->usb2_phy, PHY_MODE_USB_HOST); > phy_set_mode(cdns->usb3_phy, PHY_MODE_USB_HOST); > return ret; When the function finishes and returns ret, will it return an uninitialized value from the stack, potentially causing host initialization to fail unpredictably? -- Sashiko AI review · https://sashiko.dev/#/patchset/20260512-b4-no_drd_config-v4-0-7b4e5dc96f81@cadence.com?part=2 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2026-05-13 21:04 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 ` [PATCH v4 1/2] dt-bindings: usb: cdns3: Add no_drd property Pawel Laszczak via B4 Relay 2026-05-12 17:10 ` Conor Dooley 2026-05-13 20:42 ` sashiko-bot 2026-05-12 11:44 ` [PATCH v4 2/2] usb: cdnsp: Add support for device-only configuration Pawel Laszczak via B4 Relay 2026-05-13 21:04 ` sashiko-bot
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox