On Mon, Feb 12, 2024 at 01:34:49PM -0600, Bjorn Helgaas wrote:
> On Mon, Feb 12, 2024 at 05:50:41PM +0100, Johan Hovold wrote:
> > A recent commit started enabling ASPM unconditionally when the hardware
> > claims to support it. This triggers Correctable Errors for some PCIe
> > devices on machines like the Lenovo ThinkPad X13s, which could indicate
> > an incomplete driver ASPM implementation or that the hardware does in
> > fact not support L0s.
>
> I think it would be useful for debugging purposes to identify the
> specific commit. Maybe it's 9f4f3dfad8cf ("PCI: qcom: Enable ASPM for
> platforms supporting 1.9.0 ops") ?
>
> > Add support for disabling ASPM L0s in the devicetree when it is not
> > supported on a particular machine and controller.
> >
> > Note that only the 1.9.0 ops enable ASPM currently.
> >
> > Fixes: a9a023c05697 ("PCI: qcom: Add support for disabling ASPM L0s in devicetree")
>
> I don't see this SHA1 in the PCI tree; is it a stable SHA1 from
> somewhere else?
Yes, sorry, this was indeed supposed to say
Fixes: 9f4f3dfad8cf ("PCI: qcom: Enable ASPM for platforms supporting 1.9.0 ops")
as it would be a dependency for the follow-on fixes.
Johan
