Commit Message

PHB slots don't have an associated device (slot->pd = NULL). They were
not used by the PCI hotplug framework so far, but with opencapi
virtual PHBs, that's changing. With opencapi, devices are directly
under the PHB (no root complex or intermediate bridge) and the slot
used for hotplug is the PHB slot.
This patch uses the proper phandle when replying asynchronously to the
OS when using a PHB slot.
Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com>
---
core/pci-opal.c | 21 +++++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)

Comments

On 09/09/2019 14:31, Frederic Barrat wrote:
> PHB slots don't have an associated device (slot->pd = NULL). They were> not used by the PCI hotplug framework so far, but with opencapi> virtual PHBs, that's changing. With opencapi, devices are directly> under the PHB (no root complex or intermediate bridge) and the slot> used for hotplug is the PHB slot.> > This patch uses the proper phandle when replying asynchronously to the> OS when using a PHB slot.> > Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com>> ---
Reviewed-by: Christophe Lombard <clombard@linux.vnet.ibm.com>