On 4/23/2018 3:10 PM, Alex Williamson wrote: >> Do we need a retrain API with the speed that driver wants to reach to? >> API can return what was actually accomplished. The quirk from Alex can >> run inside this API to make a decision on what speed do we actually want >> to reach to for a given PCI topology by reprogramming the target link speed >> field. > Yes, I think the core should provide a retraining API, that would also > make the Pericom quirk easier to implement. We'd want a field/flag on > the pcidev that could be set by quirks to limit the highest target > rate, but it makes sense that this should be an interface provided by > and control point for the PCI core. Thanks, Maybe, we could live with the existing secondary bus reset API. The speed that driver wants to reach to is in the target speed field. Quirk can hook up to the secondary bus reset call, read the target speed field to see what speed we are trying to negotiate to and override the target speed register based on upstream and downstream speeds. -- 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
