From: Bjorn Helgaas <helgaas@kernel.org>
To: Timothy Pearson <tpearson@raptorengineering.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
christophe leroy <christophe.leroy@csgroup.eu>,
Naveen N Rao <naveen@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Shawn Anastasio <sanastasio@raptorengineering.com>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH v2 2/6] pci/hotplug/pnv_php: Work around switches with broken
Date: Wed, 18 Jun 2025 14:44:00 -0500 [thread overview]
Message-ID: <20250618194400.GA1219576@bhelgaas> (raw)
In-Reply-To: <1741778252.1310636.1750265814430.JavaMail.zimbra@raptorengineeringinc.com>
[+cc Lukas, pciehp expert]
On Wed, Jun 18, 2025 at 11:56:54AM -0500, Timothy Pearson wrote:
> presence detection
(subject/commit wrapping seems to be on all of these patches)
> The Microsemi Switchtec PM8533 PFX 48xG3 [11f8:8533] PCIe switch system
> was observed to incorrectly assert the Presence Detect Set bit in its
> capabilities when tested on a Raptor Computing Systems Blackbird system,
> resulting in the hot insert path never attempting a rescan of the bus
> and any downstream devices not being re-detected.
Seems like this switch supports standard PCIe hotplug? Quite a bit of
this driver looks similar to things in pciehp. Is there some reason
we can't use pciehp directly? Maybe pciehp could work if there were
hooks for the PPC-specific bits?
> Work around this by additionally checking whether the PCIe data link is
> active or not when performing presence detection on downstream switches'
> ports, similar to the pciehp_hpc.c driver.
>
> Signed-off-by: Shawn Anastasio <sanastasio@raptorengineering.com>
> Signed-off-by: Timothy Pearson <tpearson@raptorengineering.com>
> ---
> drivers/pci/hotplug/pnv_php.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/pci/hotplug/pnv_php.c b/drivers/pci/hotplug/pnv_php.c
> index aec0a6d594ac..bac8af3df41a 100644
> --- a/drivers/pci/hotplug/pnv_php.c
> +++ b/drivers/pci/hotplug/pnv_php.c
> @@ -391,6 +391,20 @@ static int pnv_php_get_power_state(struct hotplug_slot *slot, u8 *state)
> return 0;
> }
>
> +static int pcie_check_link_active(struct pci_dev *pdev)
> +{
> + u16 lnk_status;
> + int ret;
> +
> + ret = pcie_capability_read_word(pdev, PCI_EXP_LNKSTA, &lnk_status);
> + if (ret == PCIBIOS_DEVICE_NOT_FOUND || PCI_POSSIBLE_ERROR(lnk_status))
> + return -ENODEV;
> +
> + ret = !!(lnk_status & PCI_EXP_LNKSTA_DLLLA);
> +
> + return ret;
> +}
> +
> static int pnv_php_get_adapter_state(struct hotplug_slot *slot, u8 *state)
> {
> struct pnv_php_slot *php_slot = to_pnv_php_slot(slot);
> @@ -403,6 +417,19 @@ static int pnv_php_get_adapter_state(struct hotplug_slot *slot, u8 *state)
> */
> ret = pnv_pci_get_presence_state(php_slot->id, &presence);
> if (ret >= 0) {
> + if (pci_pcie_type(php_slot->pdev) == PCI_EXP_TYPE_DOWNSTREAM &&
> + presence == OPAL_PCI_SLOT_EMPTY) {
> + /*
> + * Similar to pciehp_hpc, check whether the Link Active
> + * bit is set to account for broken downstream bridges
> + * that don't properly assert Presence Detect State, as
> + * was observed on the Microsemi Switchtec PM8533 PFX
> + * [11f8:8533].
> + */
> + if (pcie_check_link_active(php_slot->pdev) > 0)
> + presence = OPAL_PCI_SLOT_PRESENT;
> + }
> +
> *state = presence;
> ret = 0;
> } else {
> --
> 2.39.5
next prev parent reply other threads:[~2025-06-18 19:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 16:54 [PATCH v2 0/6] PowerNV PCIe Hotplug Driver Fixes Timothy Pearson
2025-06-18 16:56 ` [PATCH v2 1/6] pci/hotplug/pnv_php: Properly clean up allocated IRQs on Timothy Pearson
2025-06-18 16:56 ` [PATCH v2 2/6] pci/hotplug/pnv_php: Work around switches with broken Timothy Pearson
2025-06-18 19:44 ` Bjorn Helgaas [this message]
2025-06-18 19:50 ` Timothy Pearson
2025-06-18 20:17 ` Bjorn Helgaas
2025-06-19 19:29 ` Timothy Pearson
2025-06-20 7:52 ` Lukas Wunner
2025-06-20 16:45 ` Timothy Pearson
2025-06-25 8:45 ` Lukas Wunner
2025-06-18 16:57 ` [PATCH v2 3/6] powerpc/eeh: Export eeh_unfreeze_pe() Timothy Pearson
2025-06-18 16:57 ` [PATCH v2 4/6] powerpc/eeh: Make EEH driver device hotplug safe Timothy Pearson
2025-06-18 16:58 ` [PATCH v2 5/6] pci/hotplug/pnv_php: Fix surprise plug detection and Timothy Pearson
2025-06-18 19:15 ` Bjorn Helgaas
2025-06-19 19:22 ` Timothy Pearson
2025-06-18 16:58 ` [PATCH v2 6/6] pci/hotplug/pnv_php: Enable third attention indicator Timothy Pearson
2025-06-18 19:01 ` Bjorn Helgaas
2025-06-19 0:37 ` Timothy Pearson
2025-06-20 9:26 ` Krishna Kumar
2025-06-21 9:59 ` Lukas Wunner
2025-06-25 4:08 ` Krishna Kumar
2025-06-25 8:08 ` Lukas Wunner
2025-06-25 10:55 ` Krishna Kumar
2025-06-21 15:05 ` Timothy Pearson
2025-06-24 7:07 ` Krishna Kumar
2025-06-24 16:34 ` Timothy Pearson
2025-06-24 22:34 ` Bjorn Helgaas
2025-07-07 8:01 ` Krishna Kumar
2025-07-11 18:18 ` Timothy Pearson
2025-07-11 21:05 ` Bjorn Helgaas
2025-07-15 21:41 ` Timothy Pearson
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=20250618194400.GA1219576@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=sanastasio@raptorengineering.com \
--cc=tpearson@raptorengineering.com \
/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;
as well as URLs for NNTP newsgroup(s).