From: Bjorn Helgaas <helgaas@kernel.org>
To: pawell@cadence.com
Cc: Peter Chen <peter.chen@kernel.org>,
Roger Quadros <rogerq@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] usb: cdnsp: Add support for device-only configuration
Date: Fri, 8 May 2026 09:42:41 -0500 [thread overview]
Message-ID: <20260508144241.GC85390@bhelgaas> (raw)
In-Reply-To: <20260508-no_drd_config-v3-1-0614f5044721@cadence.com>
On Fri, May 08, 2026 at 12:06:39PM +0200, Pawel Laszczak via B4 Relay wrote:
> 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: Bjorn Helgaas <bhelgaas@google.com> # pci_ids.h
I did ack this
(https://lore.kernel.org/linux-pci/20260331181209.GA148250@bhelgaas/) but I
wish I had added a note about why. Usually we don't add things to
pci_ids.h unless they're used by more than one driver. This (slightly)
simplifies backporting things.
Fine as-is, but if you respin for other reasons, you could consider moving
it to cdnsp-pci.c.
> +++ b/include/linux/pci_ids.h
* Do not add new entries to this file unless the definitions
* are shared between multiple drivers.
*/
> +#define PCI_DEVICE_ID_CDNS_UDC_USBSSP 0x0400
Looks like this #define could go in cdnsp-pci.c, since that's the only
place it's used.
next prev parent reply other threads:[~2026-05-08 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:06 [PATCH v3] usb: cdnsp: Add support for device-only configuration Pawel Laszczak
2026-05-08 10:06 ` Pawel Laszczak via B4 Relay
2026-05-08 14:42 ` Bjorn Helgaas [this message]
2026-05-12 6:16 ` Pawel Laszczak
2026-05-08 20:21 ` sashiko-bot
2026-05-09 1:31 ` Peter Chen (CIX)
2026-05-14 2:48 ` kernel test robot
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=20260508144241.GC85390@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.