From: sashiko-bot@kernel.org
To: "Brian Norris" <briannorris@chromium.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4] PCI/portdrv: Allow probing even without child services
Date: Wed, 22 Jul 2026 23:20:30 +0000 [thread overview]
Message-ID: <20260722232031.544A31F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260722160942.v4.1.I5fd5d83f518681b3949d8ab2f16ba8244fd3e774@changeid>
> 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 don't support
> any portdrv services (PCIe hotplug, AER, DPC, PME, bwctrl), 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 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>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722160942.v4.1.I5fd5d83f518681b3949d8ab2f16ba8244fd3e774@changeid?part=1
next prev parent reply other threads:[~2026-07-22 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 23:09 [PATCH v4] PCI/portdrv: Allow probing even without child services Brian Norris
2026-07-22 23:20 ` sashiko-bot [this message]
2026-07-23 6:27 ` 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=20260722232031.544A31F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=briannorris@chromium.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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