From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: nb@tipi-net.de
Cc: Mathias Nyman <mathias.nyman@intel.com>,
Ben Hutchings <ben@decadent.org.uk>,
n.buchwitz@kunbus.com, l.sanfilippo@kunbus.com,
stable@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: Restore Renesas uPD72020x support in xhci-pci
Date: Mon, 3 Feb 2025 13:46:41 +0100 [thread overview]
Message-ID: <2025020307-charity-snowfield-c975@gregkh> (raw)
In-Reply-To: <20250203120026.2010567-1-nb@tipi-net.de>
On Mon, Feb 03, 2025 at 01:00:26PM +0100, nb@tipi-net.de wrote:
> From: Nicolai Buchwitz <nb@tipi-net.de>
>
> Before commit 25f51b76f90f1 ("xhci-pci: Make xhci-pci-renesas a proper
> modular driver"), the xhci-pci driver handled the Renesas uPD72020x USB3
> PHY and only utilized features of xhci-pci-renesas when no external
> firmware EEPROM was attached. This allowed devices with a valid firmware
> stored in EEPROM to function without requiring xhci-pci-renesas.
>
> That commit changed the behavior, making xhci-pci-renesas responsible for
> handling these devices entirely, even when firmware was already present
> in EEPROM. As a result, unnecessary warnings about missing firmware files
> appeared, and more critically, USB functionality broke whens
> CONFIG_USB_XHCI_PCI_RENESAS was not enabled—despite previously workings
> without it.
>
> Fix this by ensuring that devices are only handed over to xhci-pci-renesas
> if the config option is enabled. Otherwise, restore the original behavior
> and handle them as standard xhci-pci devices.
>
> Signed-off-by: Nicolai Buchwitz <nb@tipi-net.de>
> Fixes: 25f51b76f90f ("xhci-pci: Make xhci-pci-renesas a proper modular driver")
> ---
> drivers/usb/host/xhci-pci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
> index 2d1e205c14c60..4ce80d8ac603e 100644
> --- a/drivers/usb/host/xhci-pci.c
> +++ b/drivers/usb/host/xhci-pci.c
> @@ -654,9 +654,11 @@ int xhci_pci_common_probe(struct pci_dev *dev, const struct pci_device_id *id)
> EXPORT_SYMBOL_NS_GPL(xhci_pci_common_probe, "xhci");
>
> static const struct pci_device_id pci_ids_reject[] = {
> +#if IS_ENABLED(CONFIG_USB_XHCI_PCI_RENESAS)
> /* handled by xhci-pci-renesas */
> { PCI_DEVICE(PCI_VENDOR_ID_RENESAS, 0x0014) },
> { PCI_DEVICE(PCI_VENDOR_ID_RENESAS, 0x0015) },
> +#endif
> { /* end: all zeroes */ }
> };
Have you seen:
https://lore.kernel.org/r/20250128104529.58a79bfc@foxbook
?
Which one is correct?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-03 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 12:00 [PATCH] usb: xhci: Restore Renesas uPD72020x support in xhci-pci nb
2025-02-03 12:46 ` Greg Kroah-Hartman [this message]
2025-02-03 13:00 ` nb
2025-02-03 15:25 ` Greg Kroah-Hartman
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=2025020307-charity-snowfield-c975@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=n.buchwitz@kunbus.com \
--cc=nb@tipi-net.de \
--cc=stable@vger.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