From: Bjorn Helgaas <helgaas@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, Lukas Wunner <lukas@wunner.de>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-pci@vger.kernel.org, David Matlack <dmatlack@google.com>
Subject: Re: [PATCH v2] PCI/portdrv: Allow probing even without child services
Date: Thu, 16 Jul 2026 12:26:41 -0500 [thread overview]
Message-ID: <20260716172641.GA100369@bhelgaas> (raw)
In-Reply-To: <20260209171535.v2.1.I5fd5d83f518681b3949d8ab2f16ba8244fd3e774@changeid>
[+cc David]
On Mon, Feb 09, 2026 at 05:15:35PM -0800, Brian Norris wrote:
> The PCIe port driver fails to probe if it finds no child services,
> presumably under the assumption that the driver is not useful in that
> case. However, the driver *can* still be useful for power management
> support -- namely, it still configures the port for runtime PM / D3,
> which may be important for allowing a bridge to enter low power modes.
>
> Thus, allow probe to succeed even if no IRQs and no child services are
> available. This also mirrors existing behavior for ports that have no
> PCIe capabilities, where we'd also probe successfully.
>
> This change is a bit more important after commit f5cd8a929c82 ("PCI:
> dwc: Remove MSI/MSIX capability for Root Port if iMSI-RX is used as MSI
> controller"), because it's common for some DWC-based systems to:
>
> 1. have only have the "aer" and "pcie_pme" port services available and
> 2. not define legacy INTx interrupts properly in their device tree.
>
> After commit f5cd8a929c82, such systems may fail
> pcie_init_service_irqs() and so exit with -ENODEV.
>
> Link: https://lore.kernel.org/all/nyada24tqwlkzdceyoxbzitzygvp4elvj5oajnqdwb33xkcdwk@76vnrx45fsfd/
> Signed-off-by: Brian Norris <briannorris@chromium.org>
Applied to pci/portdrv for v7.3, thank you!
I did update the commit log to be more specific about "ports that have
no PCIe capabilities" because I think we only care about AER, DPC, and
things in the PCIe Capability itself:
This also mirrors existing behavior for ports that don't support any
portdrv services (PCIe hotplug, AER, DPC, PME, bwctrl), where we'd
also probe successfully.
> ---
>
> Changes in v2:
> * clear master when we have no child services
>
> drivers/pci/pcie/portdrv.c | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/pci/pcie/portdrv.c b/drivers/pci/pcie/portdrv.c
> index 88af0dacf351..19b08f3653ee 100644
> --- a/drivers/pci/pcie/portdrv.c
> +++ b/drivers/pci/pcie/portdrv.c
> @@ -330,7 +330,7 @@ static int pcie_device_init(struct pci_dev *pdev, int service, int irq)
> */
> static int pcie_port_device_register(struct pci_dev *dev)
> {
> - int status, capabilities, i, nr_service;
> + int status, capabilities, i;
> int irqs[PCIE_PORT_DEVICE_MAXSERVICES];
>
> /* Enable PCI Express port device */
> @@ -355,29 +355,22 @@ static int pcie_port_device_register(struct pci_dev *dev)
> if (status) {
> capabilities &= PCIE_PORT_SERVICE_HP;
> if (!capabilities)
> - goto error_disable;
> + goto out;
> }
>
> /* Allocate child services if any */
> - status = -ENODEV;
> - nr_service = 0;
> for (i = 0; i < PCIE_PORT_DEVICE_MAXSERVICES; i++) {
> int service = 1 << i;
> if (!(capabilities & service))
> continue;
> - if (!pcie_device_init(dev, service, irqs[i]))
> - nr_service++;
> + pcie_device_init(dev, service, irqs[i]);
> }
> - if (!nr_service)
> - goto error_cleanup_irqs;
>
> +out:
> + /* With no child services, we shouldn't need bus mastering. */
> + if (!capabilities)
> + pci_clear_master(dev);
> return 0;
> -
> -error_cleanup_irqs:
> - pci_free_irq_vectors(dev);
> -error_disable:
> - pci_disable_device(dev);
> - return status;
> }
>
> typedef int (*pcie_callback_t)(struct pcie_device *);
> --
> 2.53.0.239.g8d8fc8a987-goog
>
next prev parent reply other threads:[~2026-07-16 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 1:15 [PATCH v2] PCI/portdrv: Allow probing even without child services Brian Norris
2026-02-19 22:25 ` Bjorn Helgaas
2026-02-20 2:35 ` Brian Norris
2026-02-20 16:40 ` Bjorn Helgaas
2026-04-09 23:20 ` Brian Norris
2026-04-09 23:41 ` Brian Norris
2026-07-16 17:26 ` Bjorn Helgaas [this message]
2026-07-17 8:26 ` Lukas Wunner
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=20260716172641.GA100369@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=briannorris@chromium.org \
--cc=dmatlack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mani@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.