Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: "Michal Gorlas" <michal.gorlas@9elements.com>
To: "Manivannan Sadhasivam" <mani@kernel.org>,
	"Richard Zhu" <hongxing.zhu@nxp.com>,
	"Lucas Stach" <l.stach@pengutronix.de>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@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>
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 20:50:59 +0200	[thread overview]
Message-ID: <DL521SM75B0T.1DGK1GVSH1G51@9elements.com> (raw)
In-Reply-To: <gayg4xafgxcog7f7jy2i2e3wctds3do2ytttgv74f3y6ed7qtg@mr3xfxugjfeh>

On Wed Sep 2, 2026 at 5:36 PM CEST, Manivannan Sadhasivam wrote:
> On Wed, Sep 02, 2026 at 04:31:19PM +0200, Manivannan Sadhasivam wrote:
>> 
>> 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
>> 
>
> I dropped this patch now as I completely missed that this patch incorrectly
> assumed that ASPM L1 is controlled by the 'supports-clkreq' property. This
> property is supposed to be used only for ASPM L1ss where REFCLK would be cut
> off.
>
> As Krishna explained in v3 [1], you should use 'aspm,no-l1' property in DT and
> use it to disable ASPM L1.

Right, 'aspm,no-l1' solves the issue I had. Also forgot to answer
to Krishna's remark in v3 thread. Sorry.

Best,
Michal

>
> - Mani
>
> [1] https://lore.kernel.org/linux-pci/aabc3dbd-3e5b-4272-807f-f0743606e25a@oss.qualcomm.com/

      reply	other threads:[~2026-09-02 18:51 UTC|newest]

Thread overview: 8+ 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 16:59 ` sashiko-bot
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
2026-09-02 15:36   ` Manivannan Sadhasivam
2026-09-02 18:50     ` Michal Gorlas [this message]

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=DL521SM75B0T.1DGK1GVSH1G51@9elements.com \
    --to=michal.gorlas@9elements.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=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