From: Inochi Amaoto <inochiama@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Inochi Amaoto <inochiama@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Chen Wang <unicorn_wang@outlook.com>,
Han Gao <rabenda.cn@gmail.com>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yixun Lan <dlan@gentoo.org>, Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH 0/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042/2044 PCIe Root Ports
Date: Tue, 30 Dec 2025 17:45:39 +0800 [thread overview]
Message-ID: <aVOfBNP3vy4Q52bZ@inochi.infowork> (raw)
In-Reply-To: <20251226163031.GA4128882@bhelgaas>
On Fri, Dec 26, 2025 at 10:30:31AM -0600, Bjorn Helgaas wrote:
> On Thu, Dec 25, 2025 at 06:05:27PM +0800, Inochi Amaoto wrote:
> > Since commit f3ac2ff14834 ("PCI/ASPM: Enable all ClockPM and ASPM
> > states for devicetree platforms") force enable ASPM on all device tree
> > platform, the SG2042/SG2044 PCIe Root Ports breaks as it advertises L0s
> > and L1 capabilities without supporting it.
> >
> > Override the L0s and L1 Support advertised in Link Capabilities by the
> > SG2042/SG2044 Root Ports so we don't try to enable those states.
> >
> > Inochi Amaoto (2):
> > PCI/ASPM: Avoid L0s and L1 on Sophgo 2042 PCIe [1f1c:2042] Root Ports
> > PCI/ASPM: Avoid L0s and L1 on Sophgo 2044 PCIe [1f1c:2044] Root Ports
> >
> > drivers/pci/quirks.c | 2 ++
> > include/linux/pci_ids.h | 2 ++
> > 2 files changed, 4 insertions(+)
>
> 1) Can somebody at Sophgo confirm that this is a hardware erratum? I
> just want to make rule out some kind of OS bug in configuring L0s/L1.
>
Hi Bjorn,
I have asked for the Sophgo staff, and they already confirmed this
hardware errata.
Regards,
Inochi
next prev parent reply other threads:[~2025-12-30 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 10:05 [PATCH 0/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042/2044 PCIe Root Ports Inochi Amaoto
2025-12-25 10:05 ` [PATCH 1/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042 PCIe [1f1c:2042] " Inochi Amaoto
2025-12-26 1:24 ` Chen Wang
2025-12-25 10:05 ` [PATCH 2/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2044 PCIe [1f1c:2044] " Inochi Amaoto
2025-12-26 16:30 ` [PATCH 0/2] PCI/ASPM: Avoid L0s and L1 on Sophgo 2042/2044 PCIe " Bjorn Helgaas
2025-12-29 0:17 ` Chen Wang
2025-12-29 15:11 ` Bjorn Helgaas
2025-12-30 9:45 ` Inochi Amaoto [this message]
2025-12-30 10:08 ` Manivannan Sadhasivam
2025-12-30 11:08 ` Inochi Amaoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aVOfBNP3vy4Q52bZ@inochi.infowork \
--to=inochiama@gmail.com \
--cc=bhelgaas@google.com \
--cc=dlan@gentoo.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=looong.bin@gmail.com \
--cc=mani@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=unicorn_wang@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox