On 8/21/2017 3:18 PM, Bjorn Helgaas wrote:
>> pci_bus_read_dev_vendor_id()
>> {
>> ...
>> if (pci_bus_crs_visibility_supported())
>> return pci_bus_wait_crs(dev->bus, dev->devfn, &id, 60000);
>>
>> return true
>> }
>>
>> Similar pattern for pci_flr_wait().
Sorry for the poor choice of function name.
I was thinking of something like this.
bool pci_bus_crs_pending(u32 l)
{
return (l & 0xFFFF) == 0x0001
}
if (pci_bus_crs_pending(id))
return pci_bus_wait_crs(dev->bus, dev->devfn, &id, 60000);
> I think that makes sense. We'd want to check for CRS SV being
> enabled, e.g., maybe read PCI_EXP_RTCTL_CRSSVE back in
> pci_enable_crs() and cache it somewhere. Maybe a crs_sv_enabled bit
> in the root port's pci_dev, and check it with something like what
> pcie_root_rcb_set() does?
>
You can observe CRS under the following conditions
1. root port <-> endpoint
2. bridge <-> endpoint
3. root port<->bridge
I was relying on the fact that we are reading 0x001 as an indication that
this device detected CRS. Maybe, this is too indirect.
If we also want to capture the capability, I think the right thing is to
check the parent capability.
bool pci_bus_crs_vis_supported(struct pci_dev *bridge)
{
if (device type(bridge) == root port)
return read(root_crs_register_reg);
if (device type(bridge) == switch)
return read(switch_crs_register);
return false;
}
bool pci_bus_crs_pending(struct pci_dev *dev, u32 l)
{
if !pci_bus_crs_vis_supported(dev->parent)
return false;
return (l & 0xFFFF) == 0x0001;
}
I'll prototype this. Let me know if you have concerns.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
