From: Krishna Kumar <krishnak@linux.ibm.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: linuxppc-dev@lists.ozlabs.org,
Timothy Pearson <tpearson@raptorengineering.com>,
Shawn Anastasio <sanastasio@raptorengineering.com>,
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>
Subject: Re: [PATCH v2 6/6] pci/hotplug/pnv_php: Enable third attention indicator
Date: Wed, 25 Jun 2025 09:38:19 +0530 [thread overview]
Message-ID: <f13a2d2b-af52-4934-b4fa-66bc1e5ece32@linux.ibm.com> (raw)
In-Reply-To: <aFaCfYre9N52ARWH@wunner.de>
On 6/21/25 3:29 PM, Lukas Wunner wrote:
> On Fri, Jun 20, 2025 at 02:56:51PM +0530, Krishna Kumar wrote:
>> 5. If point 3 and 4 does not solve the problem, then only we should
>> move to pciehp.c. But AFAIK, PPC/Powernv is DT based while pciehp.c
>> may be only supporting acpi (I have to check it on this). We need to
>> provide PHB related information via DTB and maintain the related
>> topology information via dtb and then it can be doable.
> pciehp is not ACPI-specific. The PCIe port service driver in
> drivers/pci/pcie/portdrv.c binds to any PCIe port, examines the
> port's capabilities (e.g. hotplug, AER, DPC, ...) and instantiates
> sub-devices to which pciehp and the other drivers such as aer bind.
Good to know and thanks for the info. As I already told I did not go through pciehp.c,
and its internal working (since I did not needed it) I can only comment in concrete manner
once I am done with its code review and internal logic.
What my concern was, you can comment on below point if I am wrong (I will learn something) -
1. If we get PHB info from mmcfg via acpi table in x86 and create a root port from there with
some address/entity and if this Acpi and associated entity is not present for PPC, then it can be a problem.
2. PPC is normally based on DTB entity and it identifies PHB and pcie devices from there. If this all the information
is correctly map via portdrv.c then there is no problem and whatever you are telling is correct and it will work.
3. But if point 2 is not handled correctly we need to just aligned with port related data structure to make it work.
Not a big deal but need to put thorough logic and testing effort. If its already in place, we are good.
>
> How do you prevent pciehp from driving hotplug on PowerNV anyway?
> Do you disable CONFIG_HOTPLUG_PCI_PCIE?
I am not sure if at present pciehp is used for Powenv, and PPC uses this config or it has disabled it (since we rely on pnvphp.c for our hotplug operation, I did not checked it).
If its going to work on PPC by enabling config and its giving correct output, I dont see any reason to not using it as an
alternate driver where pnvphp.c fails. But yeah, as I told I can commnet on this once I do some experiment (going through
the code and some testing). But yeah, its always good to hear from you. Thanks a bunch !!
>
> Thanks,
>
> Lukas
Best regards,
Krishna
>
next prev parent reply other threads:[~2025-06-25 4:08 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
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 [this message]
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=f13a2d2b-af52-4934-b4fa-66bc1e5ece32@linux.ibm.com \
--to=krishnak@linux.ibm.com \
--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).