[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aFaCfYre9N52ARWH@wunner.de>
Date: Sat, 21 Jun 2025 11:59:25 +0200
From: Lukas Wunner <lukas@...ner.de>
To: Krishna Kumar <krishnak@...ux.ibm.com>
Cc: linuxppc-dev@...ts.ozlabs.org,
Timothy Pearson <tpearson@...torengineering.com>,
Shawn Anastasio <sanastasio@...torengineering.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
"\"linux-pci\"," <linux-pci@...r.kernel.org>,
Madhavan Srinivasan <maddy@...ux.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
christophe leroy <christophe.leroy@...roup.eu>,
Naveen N Rao <naveen@...nel.org>,
"\"Bjorn Helgaas\"," <bhelgaas@...gle.com>
Subject: Re: [PATCH v2 6/6] pci/hotplug/pnv_php: Enable third attention
indicator
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.
How do you prevent pciehp from driving hotplug on PowerNV anyway?
Do you disable CONFIG_HOTPLUG_PCI_PCIE?
Thanks,
Lukas
Powered by blists - more mailing lists