From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: "Richard Zhu" <hongxing.zhu@nxp.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Michal Gorlas" <michal.gorlas@9elements.com>
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2] PCI: imx6: Enable ASPM L1 only iff CLKREQ# is supported
Date: Wed, 02 Sep 2026 16:31:19 +0200 [thread overview]
Message-ID: <178835947957.88571.7553170178358028044.b4-ty@b4> (raw)
In-Reply-To: <20260827-l1-conditional-imx-v2-1-40b324aa2a94@9elements.com>
On Thu, 27 Aug 2026 18:51:00 +0200, Michal Gorlas wrote:
> Since commit f3ac2ff14834 ("PCI/ASPM: Enable all ClockPM and ASPM
> states for devicetree platforms"), ASPM states are force enabled
> on all devicetree platforms. This causes PCI devices on some i.MX SoCs
> (for e.g. i.MX 8M Plus Kontron SMARC eval carrier) to enter L1 even
> though CLKREQ# is not supported (and consequently supports-clkreq is
> not set in pcie controller node of their DT), which causes the device to
> never wake up from L1.
>
> [...]
Applied, thanks!
[1/1] PCI: imx6: Enable ASPM L1 only iff CLKREQ# is supported
commit: 94420d27973f567e5c10b631115ea8b9abc0172e
Best regards,
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2026-09-02 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 16:51 [PATCH RESEND v2] PCI: imx6: Enable ASPM L1 only iff CLKREQ# is supported Michal Gorlas
2026-08-27 17:10 ` Frank Li
2026-08-27 18:29 ` Michal Gorlas
2026-08-27 19:08 ` Frank Li
2026-09-02 14:31 ` Manivannan Sadhasivam [this message]
2026-09-02 15:36 ` Manivannan Sadhasivam
2026-09-02 18:50 ` Michal Gorlas
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=178835947957.88571.7553170178358028044.b4-ty@b4 \
--to=manivannan.sadhasivam@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kwilczynski@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=michal.gorlas@9elements.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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