On 5/31/2018 5:44 PM, Alex G. wrote: > On 05/31/2018 10:30 AM, Sinan Kaya wrote: >> On 5/31/2018 11:05 AM, Alexandru Gagniuc wrote: >>> + if (dev_cur_speed < max_link_speed) >>> + pci_warn(dev, "PCIe downtrain: link speed is %s (%s capable)", >>> + pcie_bus_speed_name(dev_cur_speed), >>> + pcie_bus_speed_name(max_link_speed)); >>> + >> >> Also this isn't quite correct. Target link speed is what the device tries to >> train. A device can try to train to much lower speed than the maximum on purpose. >> >> It makes sense to print this if the speed that platform wants via target link >> speed is different from what is actually established though. > > After seeing Gen 3 devices that train above the speed in the target link > speed field, I talked to one the spec writers today. There is some > ambiguity with the target link speed field. In PCIe 4.0 they are > clarifying that to state that this field is "permitted to have no effect". Good to know. Probably, some company screwed up implementing this register... All these flexible terminology in the spec is an indication of such a failure. > > Alex > > -- 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.
