On Sat, Apr 14, 2018 at 09:04:05AM +0530, Srinath Mannam wrote: > I am sorry, in previous mail by mistake I have written L1.s support is > not there, Actually I wanted to write L0s support is not there. > L1 and L1ss support is there. If your endpoint (and everything in the path) advertise both LTR and L1ss support, that patch probably won't make a difference. It *might* make a difference if only part of the path supports both, because my reading of the spec is that L1ss requires LTR and LTR requires the entire path to support LTR, and we currently don't enforce that "entire path" part before enabling L1ss. > But In our platform we required to disable ASPM. We're trying to figure out exactly *why* you must disable ASPM. If it's because of a hardware defect, e.g., the device advertises ASPM support but it's actually broken, we probably need to add a quirk. Given the complexity of ASPM, it's surprising we don't have similar quirks already. > RC in our platform supports upto Gen3 only. I don't think there's a connection between ASPM or LTR and the link speed (Gen2, Gen3, etc), is there? Bjorn
