From: Bjorn Helgaas <helgaas@kernel.org>
To: Maverickk 78 <maverickk1778@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: pcie hotplug driver probe is not getting called
Date: Fri, 27 Sep 2024 12:17:22 -0500 [thread overview]
Message-ID: <20240927171722.GA84699@bhelgaas> (raw)
In-Reply-To: <CALfBBTthgTJKZ+49rW7XKDp2xP6pDhSqPAgDsxczV_s00-Ov1A@mail.gmail.com>
On Fri, Sep 27, 2024 at 08:50:41PM +0530, Maverickk 78 wrote:
> Hello
>
> Debugging a downstream port with slot capabilities indicating hotplug
> capability is advertised in pci capability(id =0x10) .
>
> None of the hotplug driver is getting invoked.
>
> I assume pciehp_probe should've been called because its associated
> with ".port_type = PCIE_ANY_PORT," in the pcie_port_service_driver
> structure.
>
> I assumed SHPC shpc_probe function would be called because the pci_id
> table has PCI_CLASS_BRIDGE_PCI_NORMAL, but nothing related to hotplug
> drivers is seen in the ftrace or dmesg.
>
> Tried "pciehp.pciehp_force=1 pciehp.pciehp_debug=1" in the command
> line but no luck
>
> As part of port initialization if the hotplug capability is indicated
> in the capability register the hotplug drivers should have been
> invoked, but looks like its not the case.
I would expect pciehp to work in this case, but there is some
negotiation between the OS and the firmware to figure out which
owns it.
I assume you have CONFIG_PCIEPORTBUS and CONFIG_HOTPLUG_PCI_PCIE
enabled? Can you supply the dmesg log and output of "sudo lspci -vv"?
Bjorn
next prev parent reply other threads:[~2024-09-27 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 15:20 pcie hotplug driver probe is not getting called Maverickk 78
2024-09-27 17:17 ` Bjorn Helgaas [this message]
2024-09-29 13:59 ` Maverickk 78
2024-09-30 12:49 ` Maverickk 78
2024-09-30 19:28 ` Bjorn Helgaas
2024-10-01 12:48 ` Maverickk 78
2024-10-01 18:09 ` Maverickk 78
2024-10-01 18:19 ` Keith Busch
[not found] ` <CALfBBTtxJB1BQkSZ=RBKCiZKNeTxsJHAZ50jdBUjNSmOf79NWw@mail.gmail.com>
2024-10-04 18:20 ` Maverickk 78
2024-10-04 21:56 ` Bjorn Helgaas
[not found] ` <CALfBBTtjXJiZBSfFTUAPsD+G15nPQQsn-2sCrAt1UwPsrNsqNg@mail.gmail.com>
2024-10-15 8:44 ` Maverickk 78
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=20240927171722.GA84699@bhelgaas \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maverickk1778@gmail.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).