opencapi: enable card reset and link retraining
Subsystems (4)
cover opencapi: enable card reset and link retraining
This is the linux part of the work to use the PCI hotplug framework to control an opencapi card so that it can be reset and re-read after flashing a new FPGA image.
It needs support in skiboot:
http://patchwork.ozlabs.org/project/skiboot/list/?series=114803
On an old skiboot, it will do nothing.
A virtual PCI slot is created for the opencapi adapter, and its state can be controlled through the pnv-php hotplug driver:
echo 0|1 > /sys/bus/pci/slots/OPENCAPI-<...>/power
Note that the power to the card is not really turned off, as the card needs to stay on to be flashed with a new image. Instead the card is placed in reset.
The first part of the series mostly deals with the pci/ioda state, as the devices can now go away and the state needs to be cleaned up.
The second part is modifications to the hotplug driver on powernv, so that a virtual slot is created for the opencapi adapters found in the device tree
Frederic Barrat (11):
powerpc/powernv/ioda: Fix ref count for devices with their own PE powerpc/powernv/ioda: Protect PE list powerpc/powernv/ioda: set up PE on opencapi device when enabling powerpc/powernv/ioda: Release opencapi device powerpc/powernv/ioda: Find opencapi slot for a device node pci/hotplug/pnv-php: Remove erroneous warning pci/hotplug/pnv-php: Improve error msg on power state change failure pci/hotplug/pnv-php: Register opencapi slots pci/hotplug/pnv-php: Relax check when disabling slot pci/hotplug/pnv-php: Wrap warnings in macro
ocxl: Add PCI hotplug dependency to Kconfig
arch/powerpc/include/asm/pnv-pci.h | 1 + arch/powerpc/platforms/powernv/pci-ioda.c | 106 ++++++++++++++-------- arch/powerpc/platforms/powernv/pci.c | 10 +- drivers/misc/ocxl/Kconfig | 1 + drivers/pci/hotplug/pnv_php.c | 66 ++++++++------ 5 files changed, 115 insertions(+), 69 deletions(-)
Signature · 1 line
2.21.0
RFC 1/11 powerpc/powernv/ioda: Fix ref count for devices with their own PE
Taking a reference on the pci_dev structure was required with initial commit 184cd4a3b962 ("powerpc/powernv: PCI support for p7IOC under OPAL v2"), where we we storing the pci dev in the pci_dn structure.
However, the pci_dev was later removed from the pci_dn structure, but the reference was kept. See 902bdc57451c ("powerpc/powernv/idoa:
Remove unnecessary pcidev from pci_dn").
The pnv_ioda_pe structure life cycle is the same as the pci_dev structure, the PE is freed when the device is released. So we don't need a reference for the pci_dev stored in the PE, otherwise the pci_dev will never be released. Which is not really a surprise as the comment (removed here as no longer needed) was stating as much.
--- arch/powerpc/platforms/powernv/pci-ioda.c | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-)
arch/powerpc/platforms/powernv/pci-ioda.c +1 -10
@@ -1060,14 +1060,6 @@ static struct pnv_ioda_pe *pnv_ioda_setup_dev_PE(struct pci_dev *dev)return NULL ; } -/* NOTE: We get only one ref to the pci_dev for the pdn, not for the -* pointer in the PE data structure, both should be destroyed at the -* same time. However, this needs to be looked at more closely again -* once we actually start removing things (Hotplug, SR-IOV, ...) -* -* At some point we want to remove the PDN completely anyways -*/ -pci_dev_get (dev); pdn->pe_number = pe->pe_number; pe->flags =PNV_IODA_PE_DEV ; pe->pdev = dev;
@@ -1082,7 +1074,6 @@ static struct pnv_ioda_pe *pnv_ioda_setup_dev_PE(struct pci_dev *dev)pnv_ioda_free_pe (pe); pdn->pe_number =IODA_INVALID_PE ; pe->pdev =NULL ; -pci_dev_put (dev);return NULL ; }
@@ -1226,7 +1217,7 @@ static struct pnv_ioda_pe *pnv_ioda_setup_npu_PE(struct pci_dev *npu_pdev)*/ dev_info (&npu_pdev->dev,"Associating to existing PE %x\n" , pe_num); -pci_dev_get (npu_pdev); +pci_dev_get (npu_pdev);// still needed after 902bdc57451c2c64aa139bbe24067f70a186db0a ? npu_pdn =pci_get_pdn (npu_pdev); rid = npu_pdev->bus->number <<8 | npu_pdn->devfn; npu_pdn->pe_number = pe_num;
Signature · 1 line
2.21.0
RFC 2/11 powerpc/powernv/ioda: Protect PE list
In reply to Frederic BarratProtect the PHB's list of PE. Probably not needed as long as it was populated during PHB creation, but it feels right and will become required once we can add/remove opencapi devices on hotplug.
--- arch/powerpc/platforms/powernv/pci-ioda.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
arch/powerpc/platforms/powernv/pci-ioda.c +5 -1
@@ -1078,8 +1078,9 @@ static struct pnv_ioda_pe *pnv_ioda_setup_dev_PE(struct pci_dev *dev) }/* Put PE to the list */ +mutex_lock (&phb->ioda.pe_list_mutex);list_add_tail (&pe->list, &phb->ioda.pe_list); - +mutex_unlock (&phb->ioda.pe_list_mutex);return pe; }
@@ -3501,7 +3502,10 @@ static void pnv_ioda_release_pe(struct pnv_ioda_pe *pe)struct pnv_phb *phb = pe->phb;struct pnv_ioda_pe *slave, *tmp; +mutex_lock (&phb->ioda.pe_list_mutex);list_del (&pe->list); +mutex_unlock (&phb->ioda.pe_list_mutex); +switch (phb->type) {case PNV_PHB_IODA1 :pnv_pci_ioda1_release_pe_dma (pe);
Signature · 1 line
2.21.0
Re: [RFC 02/11] powerpc/powernv/ioda: Protect PE list
Quoted 5 lines · Frederic Barrat
Protect the PHB's list of PE. Probably not needed as long as it was populated during PHB creation, but it feels right and will become required once we can add/remove opencapi devices on hotplug.
Signed-off-by Frederic Barrat <[email protected]>
Quoted 31 lines
--- arch/powerpc/platforms/powernv/pci-ioda.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)arch/powerpc/platforms/powernv/pci-ioda.c +5
-1@@ -1078,8 +1078,9 @@ static struct pnv_ioda_pe *pnv_ioda_setup_dev_PE(struct pci_dev *dev) }/* Put PE to the list */ +mutex_lock (&phb->ioda.pe_list_mutex);list_add_tail (&pe->list, &phb->ioda.pe_list); - +mutex_unlock (&phb->ioda.pe_list_mutex);return pe; }@@ -3501,7 +3502,10 @@ static void pnv_ioda_release_pe(struct pnv_ioda_pe *pe)struct pnv_phb *phb = pe->phb;struct pnv_ioda_pe *slave, *tmp; +mutex_lock (&phb->ioda.pe_list_mutex);list_del (&pe->list); +mutex_unlock (&phb->ioda.pe_list_mutex); +switch (phb->type) {case PNV_PHB_IODA1 :pnv_pci_ioda1_release_pe_dma (pe);
Signature · 2 lines
Andrew Donnellan OzLabs, ADL Canberra [email protected] IBM Australia Limited
RFC 3/11 powerpc/powernv/ioda: set up PE on opencapi device when enabling
In reply to Frederic BarratThe PE for an opencapi device was set as part of a late PHB fixup operation, when creating the PHB. To use the PCI hotplug framework, this is not going to work, as the PHB stays the same, it's only the devices underneath which are updated. For regular PCI devices, it is done as part of the reconfiguration of the bridge, but for opencapi PHBs, we don't have an intermediate bridge. So let's define the PE when the device is enabled. PEs are meaningless for opencapi, the NPU doesn't define them and opal is not doing anything with them.
--- arch/powerpc/platforms/powernv/pci-ioda.c | 31 +++++++++++++++++------ 1 file changed, 23 insertions(+), 8 deletions(-)
arch/powerpc/platforms/powernv/pci-ioda.c +23 -8
@@ -1258,8 +1258,6 @@ static void pnv_pci_ioda_setup_PEs(void) {struct pci_controller *hose;struct pnv_phb *phb; -struct pci_bus *bus; -struct pci_dev *pdev;struct pnv_ioda_pe *pe;list_for_each_entry (hose, &hose_list, list_node) {
@@ -1271,11 +1269,6 @@ static void pnv_pci_ioda_setup_PEs(void)if (phb->model ==PNV_PHB_MODEL_NPU2 )WARN_ON_ONCE (pnv_npu2_init (hose)); } -if (phb->type ==PNV_PHB_NPU_OCAPI ) { - bus = hose->bus; -list_for_each_entry (pdev, &bus->devices, bus_list) -pnv_ioda_setup_dev_PE (pdev); - } }list_for_each_entry (hose, &hose_list, list_node) { phb = hose->private_data;
@@ -3373,6 +3366,28 @@ static bool pnv_pci_enable_device_hook(struct pci_dev *dev)return true; } +static bool pnv_ocapi_enable_device_hook (struct pci_dev *dev) +{ +struct pci_controller *hose =pci_bus_to_host (dev->bus); +struct pnv_phb *phb = hose->private_data; +struct pci_dn *pdn; +struct pnv_ioda_pe *pe; + +if (!phb->initialized) +return true; + + pdn =pci_get_pdn (dev); +if (!pdn) +return false; + +if (pdn->pe_number ==IODA_INVALID_PE ) { + pe =pnv_ioda_setup_dev_PE (dev); +if (!pe) +return false; + } +return true; +} +static long pnv_pci_ioda1_unset_window (struct iommu_table_group *table_group,int num) {
@@ -3613,7 +3628,7 @@ static const struct pci_controller_ops pnv_npu_ioda_controller_ops = { };static const struct pci_controller_ops pnv_npu_ocapi_ioda_controller_ops = { - .enable_device_hook = pnv_pci_enable_device_hook, + .enable_device_hook = pnv_ocapi_enable_device_hook, .window_alignment = pnv_pci_window_alignment, .reset_secondary_bus = pnv_pci_reset_secondary_bus, .shutdown = pnv_pci_ioda_shutdown,
Signature · 1 line
2.21.0
RFC 4/11 powerpc/powernv/ioda: Release opencapi device
In reply to Frederic BarratWith hotplug, an opencapi device can now go away. It needs to be released, mostly to clean up its PE state. We were previously not defining any device callback. We can reuse the standard PCI release callback, it does a bit too much for an opencapi device, but it's harmless, and only needs minor tuning.
Also separate the undo of the PELT-V code in a separate function, it is not needed for NPU devices and it improves a bit the readability of the code.
--- arch/powerpc/platforms/powernv/pci-ioda.c | 58 +++++++++++++++-------- 1 file changed, 38 insertions(+), 20 deletions(-)
arch/powerpc/platforms/powernv/pci-ioda.c +38 -20
@@ -186,7 +186,7 @@ static void pnv_ioda_free_pe(struct pnv_ioda_pe *pe)unsigned int pe_num = pe->pe_number;WARN_ON (pe->pdev); -WARN_ON (pe->npucomp);/* NPUs are not supposed to be freed */ +WARN_ON (pe->npucomp);/* NPUs for nvlink are not supposed to be freed */ kfree (pe->npucomp);memset (pe,0 ,sizeof (struct pnv_ioda_pe ));clear_bit (pe_num, phb->ioda.pe_alloc);
@@ -775,6 +775,33 @@ static int pnv_ioda_set_peltv(struct pnv_phb *phb,return 0 ; } +static void pnv_ioda_unset_peltv (struct pnv_phb *phb, +struct pnv_ioda_pe *pe, +struct pci_dev *parent) +{ +int64_t rc; + +while (parent) { +struct pci_dn *pdn =pci_get_pdn (parent); +if (pdn && pdn->pe_number !=IODA_INVALID_PE ) { + rc =opal_pci_set_peltv (phb->opal_id, pdn->pe_number, + pe->pe_number,OPAL_REMOVE_PE_FROM_DOMAIN ); +/* XXX What to do in case of error ? */ + } + parent = parent->bus->self; + } + +opal_pci_eeh_freeze_clear (phb->opal_id, pe->pe_number, +OPAL_EEH_ACTION_CLEAR_FREEZE_ALL ); + +/* Disassociate PE in PELT */ + rc =opal_pci_set_peltv (phb->opal_id, pe->pe_number, + pe->pe_number,OPAL_REMOVE_PE_FROM_DOMAIN ); +if (rc) +pe_warn (pe,"OPAL error %lld remove self from PELTV\n" , rc); + +} +static int pnv_ioda_deconfigure_pe (struct pnv_phb *phb,struct pnv_ioda_pe *pe) {struct pci_dev *parent;
@@ -825,25 +852,13 @@ static int pnv_ioda_deconfigure_pe(struct pnv_phb *phb, struct pnv_ioda_pe *pe)for (rid = pe->rid; rid < rid_end; rid++) phb->ioda.pe_rmap[rid] =IODA_INVALID_PE ; -/* Release from all parents PELT-V */ -while (parent) { -struct pci_dn *pdn =pci_get_pdn (parent); -if (pdn && pdn->pe_number !=IODA_INVALID_PE ) { - rc =opal_pci_set_peltv (phb->opal_id, pdn->pe_number, - pe->pe_number,OPAL_REMOVE_PE_FROM_DOMAIN ); -/* XXX What to do in case of error ? */ - } - parent = parent->bus->self; - } - -opal_pci_eeh_freeze_clear (phb->opal_id, pe->pe_number, -OPAL_EEH_ACTION_CLEAR_FREEZE_ALL ); +/* +* Release from all parents PELT-V. NPUs don't have a PELTV +* table +*/ +if (phb->type !=PNV_PHB_NPU_NVLINK && phb->type !=PNV_PHB_NPU_OCAPI ) +pnv_ioda_unset_peltv (phb, pe, parent); -/* Disassociate PE in PELT */ - rc =opal_pci_set_peltv (phb->opal_id, pe->pe_number, - pe->pe_number,OPAL_REMOVE_PE_FROM_DOMAIN ); -if (rc) -pe_warn (pe,"OPAL error %lld remove self from PELTV\n" , rc); rc =opal_pci_set_pe (phb->opal_id, pe->pe_number, pe->rid, bcomp, dcomp, fcomp,OPAL_UNMAP_PE );if (rc)
@@ -3528,6 +3543,8 @@ static void pnv_ioda_release_pe(struct pnv_ioda_pe *pe)case PNV_PHB_IODA2 :pnv_pci_ioda2_release_pe_dma (pe);break ; +case PNV_PHB_NPU_OCAPI : +break ;default :WARN_ON (1 ); }
@@ -3580,7 +3597,7 @@ static void pnv_pci_release_device(struct pci_dev *pdev) pe = &phb->ioda.pe_array[pdn->pe_number]; pdn->pe_number =IODA_INVALID_PE ; -WARN_ON (--pe->device_count <0 ); +WARN_ON ((pe->flags !=PNV_IODA_PE_DEV ) && (--pe->device_count <0 ));if (pe->device_count ==0 )pnv_ioda_release_pe (pe); }
@@ -3629,6 +3646,7 @@ static const struct pci_controller_ops pnv_npu_ioda_controller_ops = {static const struct pci_controller_ops pnv_npu_ocapi_ioda_controller_ops = { .enable_device_hook = pnv_ocapi_enable_device_hook, + .release_device = pnv_pci_release_device, .window_alignment = pnv_pci_window_alignment, .reset_secondary_bus = pnv_pci_reset_secondary_bus, .shutdown = pnv_pci_ioda_shutdown,
Signature · 1 line
2.21.0
RFC 5/11 powerpc/powernv/ioda: Find opencapi slot for a device node
In reply to Frederic BarratUnlike 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 it from the PHB ID, like skiboot.
--- arch/powerpc/include/asm/pnv-pci.h | 1 + arch/powerpc/platforms/powernv/pci.c | 10 +++++++--- 2 files changed, 8 insertions(+), 3 deletions(-)
arch/powerpc/include/asm/pnv-pci.h +1 -0
@@ -15,6 +15,7 @@#define PCI_SLOT_ID_PREFIX (1UL << 63)#define PCI_SLOT_ID (phb_id, bdfn) \ (PCI_SLOT_ID_PREFIX | ((uint64_t)(bdfn) << 16) | (phb_id)) +#define PCI_PHB_SLOT_ID (phb_id) (phb_id)extern int pnv_pci_get_slot_id (struct device_node *np,uint64_t *id);extern int pnv_pci_get_device_tree (uint32_t phandle,void *buf,uint64_t len);
arch/powerpc/platforms/powernv/pci.c +7 -3
@@ -49,13 +49,14 @@ int pnv_pci_get_slot_id(struct device_node *np, uint64_t *id)return -ENXIO ; bdfn = ((bdfn &0x00ffff00 ) >>8 ); -while ((parent =of_get_parent (parent))) { +for (parent = np; parent; parent =of_get_parent (parent)) {if (!PCI_DN (parent)) {of_node_put (parent);break ; } -if (!of_device_is_compatible (parent,"ibm,ioda2-phb" )) { +if (!of_device_is_compatible (parent,"ibm,ioda2-phb" ) && + !of_device_is_compatible (parent,"ibm,ioda2-npu2-opencapi-phb" )) {of_node_put (parent);continue ; }
@@ -66,7 +67,10 @@ int pnv_pci_get_slot_id(struct device_node *np, uint64_t *id)return -ENXIO ; } - *id =PCI_SLOT_ID (phbid, bdfn); +if (of_device_is_compatible (parent,"ibm,ioda2-npu2-opencapi-phb" )) + *id =PCI_PHB_SLOT_ID (phbid); +else + *id =PCI_SLOT_ID (phbid, bdfn);return 0 ; }
Signature · 1 line
2.21.0
RFC 6/11 pci/hotplug/pnv-php: Remove erroneous warning
In reply to Frederic BarratOn powernv, when removing a device through hotplug, the following warning is logged:
Invalid refcount <.> on <...>
It may be incorrect, the refcount may be set to a higher value than 1 and be valid. of_detach_node() can drop more than one reference. As it doesn't seem trivial to assert the correct value, let's remove the warning.
--- drivers/pci/hotplug/pnv_php.c | 6 ------ 1 file changed, 6 deletions(-)
drivers/pci/hotplug/pnv_php.c +0 -6
@@ -151,17 +151,11 @@ static void pnv_php_rmv_pdns(struct device_node *dn)static void pnv_php_detach_device_nodes (struct device_node *parent) {struct device_node *dn; -int refcount;for_each_child_of_node (parent, dn) {pnv_php_detach_device_nodes (dn);of_node_put (dn); - refcount =kref_read (&dn->kobj.kref); -if (refcount !=1 ) -pr_warn ("Invalid refcount %d on <%pOF>\n" , - refcount, dn); -of_detach_node (dn); } }
Signature · 1 line
2.21.0
RFC 7/11 pci/hotplug/pnv-php: Improve error msg on power state change failure
In reply to Frederic BarratWhen changing the slot state, if opal hits an error and tells as such in the asynchronous reply, the warning "Wrong msg" is logged, which is rather confusing. Instead we can reuse the better message which is already used when we couldn't submit the asynchronous opal request initially.
--- drivers/pci/hotplug/pnv_php.c | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-)
drivers/pci/hotplug/pnv_php.c +11 -5
@@ -336,18 +336,19 @@ int pnv_php_set_slot_power_state(struct hotplug_slot *slot, ret =pnv_pci_set_power_state (php_slot->id, state, &msg);if (ret >0 ) {if (be64_to_cpu (msg.params[1 ]) != php_slot->dn->phandle || -be64_to_cpu (msg.params[2 ]) != state || -be64_to_cpu (msg.params[3 ]) !=OPAL_SUCCESS ) { +be64_to_cpu (msg.params[2 ]) != state) {pci_warn (php_slot->pdev,"Wrong msg (%lld, %lld, %lld)\n" ,be64_to_cpu (msg.params[1 ]),be64_to_cpu (msg.params[2 ]),be64_to_cpu (msg.params[3 ]));return -ENOMSG ; } +if (be64_to_cpu (msg.params[3 ]) !=OPAL_SUCCESS ) { + ret = -ENODEV ; + goto error; + } }else if (ret <0 ) { -pci_warn (php_slot->pdev,"Error %d powering %s\n" , - ret, (state ==OPAL_PCI_SLOT_POWER_ON ) ?"on" :"off" ); -return ret; + goto error; }if (state ==OPAL_PCI_SLOT_POWER_OFF || state ==OPAL_PCI_SLOT_OFFLINE )
@@ -356,6 +357,11 @@ int pnv_php_set_slot_power_state(struct hotplug_slot *slot, ret =pnv_php_add_devtree (php_slot);return ret; + +error: +pci_warn (php_slot->pdev,"Error %d powering %s\n" , + ret, (state ==OPAL_PCI_SLOT_POWER_ON ) ?"on" :"off" ); +return ret; }EXPORT_SYMBOL_GPL (pnv_php_set_slot_power_state);
Signature · 1 line
2.21.0
RFC 8/11 pci/hotplug/pnv-php: Register opencapi slots
In reply to Frederic BarratAdd the opencapi PHBs to the list of PHBs being scanned to look for slots.
--- drivers/pci/hotplug/pnv_php.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/pci/hotplug/pnv_php.c +4 -1
@@ -954,7 +954,8 @@ static int __init pnv_php_init(void)pr_info (DRIVER_DESC " version: " DRIVER_VERSION "\n" );for_each_compatible_node (dn,NULL ,"ibm,ioda2-phb" )pnv_php_register (dn); - +for_each_compatible_node (dn,NULL ,"ibm,ioda2-npu2-opencapi-phb" ) +pnv_php_register_one (dn);return 0 ; }
@@ -964,6 +965,8 @@ static void __exit pnv_php_exit(void)for_each_compatible_node (dn,NULL ,"ibm,ioda2-phb" )pnv_php_unregister (dn); +for_each_compatible_node (dn,NULL ,"ibm,ioda2-npu2-opencapi-phb" ) +pnv_php_unregister (dn); }module_init (pnv_php_init);
Signature · 1 line
2.21.0
RFC 9/11 pci/hotplug/pnv-php: Relax check when disabling slot
In reply to Frederic BarratThe driver only allows to disable a slot in the POPULATED state. However, if an error occurs while enabling the slot, say because the link couldn't be trained, then the POPULATED state may not be reached, yet the power state of the slot is on. So allow to disable a slot in the REGISTERED state. Removing the devices will do nothing since it's not populated, and we'll set the power state of the slot back to off.
--- drivers/pci/hotplug/pnv_php.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/pci/hotplug/pnv_php.c +7 -1
@@ -523,7 +523,13 @@ static int pnv_php_disable_slot(struct hotplug_slot *slot)struct pnv_php_slot *php_slot =to_pnv_php_slot (slot);int ret; -if (php_slot->state !=PNV_PHP_STATE_POPULATED ) +/* +* Allow to disable a slot already in the registered state to +* cover cases where the slot couldn't be enabled and never +* reached the populated state +*/ +if (php_slot->state !=PNV_PHP_STATE_POPULATED && + php_slot->state !=PNV_PHP_STATE_REGISTERED )return 0 ;/* Remove all devices behind the slot */
Signature · 1 line
2.21.0
Re: [RFC 09/11] pci/hotplug/pnv-php: Relax check when disabling slot
Quoted 9 lines · Frederic Barrat
The driver only allows to disable a slot in the POPULATED state. However, if an error occurs while enabling the slot, say because the link couldn't be trained, then the POPULATED state may not be reached, yet the power state of the slot is on. So allow to disable a slot in the REGISTERED state. Removing the devices will do nothing since it's not populated, and we'll set the power state of the slot back to off.
Signed-off-by Frederic Barrat <[email protected]>
Quoted 24 lines
--- drivers/pci/hotplug/pnv_php.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/pci/hotplug/pnv_php.c +7
-1@@ -523,7 +523,13 @@ static int pnv_php_disable_slot(struct hotplug_slot *slot)struct pnv_php_slot *php_slot =to_pnv_php_slot (slot);int ret; -if (php_slot->state !=PNV_PHP_STATE_POPULATED ) +/* +* Allow to disable a slot already in the registered state to +* cover cases where the slot couldn't be enabled and never +* reached the populated state +*/ +if (php_slot->state !=PNV_PHP_STATE_POPULATED && + php_slot->state !=PNV_PHP_STATE_REGISTERED )return 0 ;/* Remove all devices behind the slot */
Signature · 2 lines
Andrew Donnellan OzLabs, ADL Canberra [email protected] IBM Australia Limited
RFC 10/11 pci/hotplug/pnv-php: Wrap warnings in macro
In reply to Frederic BarratAn opencapi slot doesn't have an associated bridge device. It's not needed for operation, but any warning is displayed through pci_warn() which uses the pci_dev struct of the assocated bridge device. So wrap those warning so that a different trace mechanism can be used if it's an opencapi slot.
--- drivers/pci/hotplug/pnv_php.c | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-)
drivers/pci/hotplug/pnv_php.c +18 -15
@@ -18,6 +18,9 @@#define DRIVER_AUTHOR "Gavin Shan, IBM Corporation"#define DRIVER_DESC "PowerPC PowerNV PCI Hotplug Driver" +#define SLOT_WARN(slot, x...) \ + (slot->pdev ? pci_warn(slot->pdev, x) : dev_warn(&slot->bus->dev, x)) +struct pnv_php_event {bool added;struct pnv_php_slot *php_slot;
@@ -265,7 +268,7 @@ static int pnv_php_add_devtree(struct pnv_php_slot *php_slot) ret =pnv_pci_get_device_tree (php_slot->dn->phandle, fdt1,0x10000 );if (ret) { -pci_warn (php_slot->pdev,"Error %d getting FDT blob\n" , ret); +SLOT_WARN (php_slot,"Error %d getting FDT blob\n" , ret); goto free_fdt1; }
@@ -279,7 +282,7 @@ static int pnv_php_add_devtree(struct pnv_php_slot *php_slot) dt =of_fdt_unflatten_tree (fdt, php_slot->dn,NULL );if (!dt) { ret = -EINVAL ; -pci_warn (php_slot->pdev,"Cannot unflatten FDT\n" ); +SLOT_WARN (php_slot,"Cannot unflatten FDT\n" ); goto free_fdt; }
@@ -289,7 +292,7 @@ static int pnv_php_add_devtree(struct pnv_php_slot *php_slot) ret =pnv_php_populate_changeset (&php_slot->ocs, php_slot->dn);if (ret) {pnv_php_reverse_nodes (php_slot->dn); -pci_warn (php_slot->pdev,"Error %d populating changeset\n" , +SLOT_WARN (php_slot,"Error %d populating changeset\n" , ret); goto free_dt; }
@@ -297,7 +300,7 @@ static int pnv_php_add_devtree(struct pnv_php_slot *php_slot) php_slot->dn->child =NULL ; ret =of_changeset_apply (&php_slot->ocs);if (ret) { -pci_warn (php_slot->pdev,"Error %d applying changeset\n" , ret); +SLOT_WARN (php_slot,"Error %d applying changeset\n" , ret); goto destroy_changeset; }
@@ -337,7 +340,7 @@ int pnv_php_set_slot_power_state(struct hotplug_slot *slot,if (ret >0 ) {if (be64_to_cpu (msg.params[1 ]) != php_slot->dn->phandle ||be64_to_cpu (msg.params[2 ]) != state) { -pci_warn (php_slot->pdev,"Wrong msg (%lld, %lld, %lld)\n" , +SLOT_WARN (php_slot,"Wrong msg (%lld, %lld, %lld)\n" ,be64_to_cpu (msg.params[1 ]),be64_to_cpu (msg.params[2 ]),be64_to_cpu (msg.params[3 ]));
@@ -359,7 +362,7 @@ int pnv_php_set_slot_power_state(struct hotplug_slot *slot,return ret; error: -pci_warn (php_slot->pdev,"Error %d powering %s\n" , +SLOT_WARN (php_slot,"Error %d powering %s\n" , ret, (state ==OPAL_PCI_SLOT_POWER_ON ) ?"on" :"off" );return ret; }
@@ -378,7 +381,7 @@ static int pnv_php_get_power_state(struct hotplug_slot *slot, u8 *state)*/ ret =pnv_pci_get_power_state (php_slot->id, &power_state);if (ret) { -pci_warn (php_slot->pdev,"Error %d getting power status\n" , +SLOT_WARN (php_slot,"Error %d getting power status\n" , ret); }else { *state = power_state;
@@ -402,7 +405,7 @@ static int pnv_php_get_adapter_state(struct hotplug_slot *slot, u8 *state) *state = presence; ret =0 ; }else { -pci_warn (php_slot->pdev,"Error %d getting presence\n" , ret); +SLOT_WARN (php_slot,"Error %d getting presence\n" , ret); }return ret;
@@ -637,7 +640,7 @@ static int pnv_php_register_slot(struct pnv_php_slot *php_slot) ret =pci_hp_register (&php_slot->slot, php_slot->bus, php_slot->slot_no, php_slot->name);if (ret) { -pci_warn (php_slot->pdev,"Error %d registering slot\n" , ret); +SLOT_WARN (php_slot,"Error %d registering slot\n" , ret);return ret; }
@@ -690,7 +693,7 @@ static int pnv_php_enable_msix(struct pnv_php_slot *php_slot)/* Enable MSIx */ ret =pci_enable_msix_exact (pdev, &entry,1 );if (ret) { -pci_warn (pdev,"Error %d enabling MSIx\n" , ret); +SLOT_WARN (php_slot,"Error %d enabling MSIx\n" , ret);return ret; }
@@ -734,7 +737,7 @@ static irqreturn_t pnv_php_interrupt(int irq, void *data) (sts & PCI_EXP_SLTSTA_PDC)) { ret =pnv_pci_get_presence_state (php_slot->id, &presence);if (ret) { -pci_warn (pdev,"PCI slot [%s] error %d getting presence (0x%04x), to retry the operation.\n" , +SLOT_WARN (php_slot,"PCI slot [%s] error %d getting presence (0x%04x), to retry the operation.\n" , php_slot->name, ret, sts);return IRQ_HANDLED ; }
@@ -764,7 +767,7 @@ static irqreturn_t pnv_php_interrupt(int irq, void *data)*/ event =kzalloc (sizeof (*event),GFP_ATOMIC );if (!event) { -pci_warn (pdev,"PCI slot [%s] missed hotplug event 0x%04x\n" , +SLOT_WARN (php_slot,"PCI slot [%s] missed hotplug event 0x%04x\n" , php_slot->name, sts);return IRQ_HANDLED ; }
@@ -789,7 +792,7 @@ static void pnv_php_init_irq(struct pnv_php_slot *php_slot, int irq)/* Allocate workqueue */ php_slot->wq =alloc_workqueue ("pciehp-%s" ,0 ,0 , php_slot->name);if (!php_slot->wq) { -pci_warn (pdev,"Cannot alloc workqueue\n" ); +SLOT_WARN (php_slot,"Cannot alloc workqueue\n" );pnv_php_disable_irq (php_slot, true);return ; }
@@ -813,7 +816,7 @@ static void pnv_php_init_irq(struct pnv_php_slot *php_slot, int irq) php_slot->name, php_slot);if (ret) {pnv_php_disable_irq (php_slot, true); -pci_warn (pdev,"Error %d enabling IRQ %d\n" , ret, irq); +SLOT_WARN (php_slot,"Error %d enabling IRQ %d\n" , ret, irq);return ; }
@@ -849,7 +852,7 @@ static void pnv_php_enable_irq(struct pnv_php_slot *php_slot) ret =pci_enable_device (pdev);if (ret) { -pci_warn (pdev,"Error %d enabling device\n" , ret); +SLOT_WARN (php_slot,"Error %d enabling device\n" , ret);return ; }
Signature · 1 line
2.21.0
RFC 11/11 ocxl: Add PCI hotplug dependency to Kconfig
In reply to Frederic BarratThe PCI hotplug framework is used to update the devices when a new image is written to the FPGA.
--- drivers/misc/ocxl/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/misc/ocxl/Kconfig +1 -0
@@ -12,6 +12,7 @@ config OCXL tristate "OpenCAPI coherent accelerator support" depends on PPC_POWERNV && PCI && EEH select OCXL_BASE + select HOTPLUG_PCI_POWERNV default m help Select this option to enable the ocxl driver for Open
Signature · 1 line
2.21.0
Re: [RFC 11/11] ocxl: Add PCI hotplug dependency to Kconfig
Quoted 4 lines · Frederic Barrat
The PCI hotplug framework is used to update the devices when a new image is written to the FPGA.
Signed-off-by Frederic Barrat <[email protected]>
Quoted 17 lines
--- drivers/misc/ocxl/Kconfig | 1 + 1 file changed, 1 insertion(+)drivers/misc/ocxl/Kconfig +1
-0@@ -12,6 +12,7 @@ config OCXL tristate "OpenCAPI coherent accelerator support" depends on PPC_POWERNV && PCI && EEH select OCXL_BASE + select HOTPLUG_PCI_POWERNV default m help Select this option to enable the ocxl driver for Open
Signature · 2 lines
Andrew Donnellan OzLabs, ADL Canberra [email protected] IBM Australia Limited