Re: [PATCH 05/11] powerpc/powernv/ioda: Find opencapi slot for a device node

2019-11-19 Thread Frederic Barrat
Le 19/11/2019 à 02:26, Andrew Donnellan a écrit : On 10/9/19 1:45 am, Frederic Barrat wrote: diff --git a/arch/powerpc/platforms/powernv/pci.c b/arch/powerpc/platforms/powernv/pci.c index 6104418c9ad5..00a79f3c989f 100644 --- a/arch/powerpc/platforms/powernv/pci.c +++ b/arch/powerpc/platform

Re: [PATCH 05/11] powerpc/powernv/ioda: Find opencapi slot for a device node

2019-11-18 Thread Andrew Donnellan
On 10/9/19 1:45 am, Frederic Barrat wrote: diff --git a/arch/powerpc/platforms/powernv/pci.c b/arch/powerpc/platforms/powernv/pci.c index 6104418c9ad5..00a79f3c989f 100644 --- a/arch/powerpc/platforms/powernv/pci.c +++ b/arch/powerpc/platforms/powernv/pci.c @@ -48,13 +48,14 @@ int pnv_pci_get_sl

Re: [PATCH 05/11] powerpc/powernv/ioda: Find opencapi slot for a device node

2019-09-09 Thread Alastair D'Silva
On Mon, 2019-09-09 at 17:45 +0200, Frederic Barrat wrote: > Unlike real PCI slots, opencapi slots are directly associated to > the (virtual) opencapi PHB, there's no intermediate bridge. So when > looking for a slot ID, we must start the search from the device node > itself and not its parent. > >

[PATCH 05/11] powerpc/powernv/ioda: Find opencapi slot for a device node

2019-09-09 Thread Frederic Barrat
Unlike real PCI slots, opencapi slots are directly associated to the (virtual) opencapi PHB, there's no intermediate bridge. So when looking for a slot ID, we must start the search from the device node itself and not its parent. Also, the slot ID is not attached to a specific bdfn, so let's build