From: Herve Codina <herve.codina@bootlin.com>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-rockchip@lists.infradead.org
Subject: Re: [RESEND] Re: [PATCH] PCI/ASPM: Enable only L0s and L1 for devicetree platforms
Date: Thu, 23 Oct 2025 11:30:43 +0200 [thread overview]
Message-ID: <20251023113043.2caffec9@bootlin.com> (raw)
In-Reply-To: <B08A289028EE2F0D+c2d1f2e5-d7c6-497a-82bd-92ae477e1016@radxa.com>
Hi,
On Thu, 23 Oct 2025 14:01:59 +0900
FUKAUMI Naoki <naoki@radxa.com> wrote:
...
>
> maybe https://lore.kernel.org/all/20251015101304.3ec03e6b@bootlin.com/
> (then +Cc: linux-arm-kernel@lists.infradead.org?)
>
For information, I tested the patch and I can confirm that my issue is
still there with the patch applied.
The only way to fix it seems to either fully disable ASPM or move to
performance ASPM policy.
Maybe my issue is simply a broken ASPM either on my host or my endpoint.
Best regards,
Hervé
WARNING: multiple messages have this Message-ID (diff)
From: Herve Codina <herve.codina@bootlin.com>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-rockchip@lists.infradead.org
Subject: Re: [RESEND] Re: [PATCH] PCI/ASPM: Enable only L0s and L1 for devicetree platforms
Date: Thu, 23 Oct 2025 11:30:43 +0200 [thread overview]
Message-ID: <20251023113043.2caffec9@bootlin.com> (raw)
In-Reply-To: <B08A289028EE2F0D+c2d1f2e5-d7c6-497a-82bd-92ae477e1016@radxa.com>
Hi,
On Thu, 23 Oct 2025 14:01:59 +0900
FUKAUMI Naoki <naoki@radxa.com> wrote:
...
>
> maybe https://lore.kernel.org/all/20251015101304.3ec03e6b@bootlin.com/
> (then +Cc: linux-arm-kernel@lists.infradead.org?)
>
For information, I tested the patch and I can confirm that my issue is
still there with the patch applied.
The only way to fix it seems to either fully disable ASPM or move to
performance ASPM policy.
Maybe my issue is simply a broken ASPM either on my host or my endpoint.
Best regards,
Hervé
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-10-23 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 22:12 [PATCH] PCI/ASPM: Enable only L0s and L1 for devicetree platforms Bjorn Helgaas
2025-10-21 4:01 ` Manivannan Sadhasivam
2025-10-21 12:35 ` Manivannan Sadhasivam
2025-10-21 15:39 ` Bjorn Helgaas
2025-10-21 15:36 ` Bjorn Helgaas
2025-10-22 19:13 ` Bjorn Helgaas
2025-10-23 4:18 ` FUKAUMI Naoki
2025-10-23 4:25 ` [RESEND] " FUKAUMI Naoki
2025-10-23 4:25 ` FUKAUMI Naoki
2025-10-23 5:01 ` FUKAUMI Naoki
2025-10-23 5:01 ` FUKAUMI Naoki
2025-10-23 9:30 ` Herve Codina [this message]
2025-10-23 9:30 ` Herve Codina
2025-10-23 5:03 ` Manivannan Sadhasivam
2025-10-23 5:03 ` Manivannan Sadhasivam
2025-10-23 6:12 ` FUKAUMI Naoki
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=20251023113043.2caffec9@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=bhelgaas@google.com \
--cc=chzigotzky@xenosoft.de \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=naoki@radxa.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.