Skip to content

Disable PCIe ASPM through kernel command line for iq-8275-evk#1313

Closed
krishnachaitanya-linux wants to merge 1 commit intoqualcomm-linux:masterfrom
krishnachaitanya-linux:master
Closed

Disable PCIe ASPM through kernel command line for iq-8275-evk#1313
krishnachaitanya-linux wants to merge 1 commit intoqualcomm-linux:masterfrom
krishnachaitanya-linux:master

Conversation

@krishnachaitanya-linux
Copy link
Copy Markdown

PCIe ASPM is not working with the current boards, so disable ASPM with kernel command line.

@Mani-Sadhasivam
Copy link
Copy Markdown
Member

As discussed offline, both RB4 and RB8 have some link stability issues with ASPM. But this commit just disables ASPM for all boards, which is wrong. This cmdline param should be passed in the relevant machine config file in conf/machine.

@krishnachaitanya-linux
Copy link
Copy Markdown
Author

ok I will raise for conf/machine/iq-8275-evk.conf as this affecting rb4 for now in new PR and close this one.

When PCIe ASPM is enabled, WLAN functionality is completly broken.
There are some connectivity issues in this platform mostly with
CLKREQ# pin.

To resolve this disable ASPM using kernel command line.

Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
@krishnachaitanya-linux
Copy link
Copy Markdown
Author

Instead of creating new one, reopened the same PR with new patch.

@krishnachaitanya-linux krishnachaitanya-linux changed the title Disable PCIe ASPM through kernel command line Disable PCIe ASPM through kernel command line for i Dec 18, 2025
@krishnachaitanya-linux krishnachaitanya-linux changed the title Disable PCIe ASPM through kernel command line for i Disable PCIe ASPM through kernel command line for iq-8275-evk Dec 18, 2025
@Mani-Sadhasivam
Copy link
Copy Markdown
Member

@krishnachaitanya-linux Don't you need the same change for RB8?

@Mani-Sadhasivam
Copy link
Copy Markdown
Member

Also beware that this cmdline param disables all ASPM states, not just L1ss where the issue is currently. So there is power penalty.

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit 3da4aca

@test-reporting-app
Copy link
Copy Markdown

Test Results

 14 files  ±0   28 suites  +2   33m 45s ⏱️ - 16m 39s
 50 tests  - 2   50 ✅ + 2  0 💤 ±0  0 ❌  - 4 
304 runs  +8  304 ✅ +16  0 💤 ±0  0 ❌  - 8 

Results for commit 3da4aca. ± Comparison against base commit db27458.

This pull request removes 2 tests.
lava ‑ auto-login-action
lava ‑ minimal-boot

@github-actions
Copy link
Copy Markdown

Test run workflow

Test jobs for commit e331608fd14d766bf01fac0537e099d0c300aa29

@krishnachaitanya-linux
Copy link
Copy Markdown
Author

@krishnachaitanya-linux Don't you need the same change for RB8?

we are not hitting this issue in RB8 yet for now, may be due to pwrctrl the athk driver is probing after PCIe controller is enabling L1ss. we can raise the patch for RB8 separately. We are hoping to solve this L1ss issue next week.

@krishnachaitanya-linux
Copy link
Copy Markdown
Author

Also beware that this cmdline param disables all ASPM states, not just L1ss where the issue is currently. So there is power penalty.

There is no other way currently to disable L1ss unless a driver change, like I said in the previous reply, we are hoping to close this by next week, then we will come with proper solution, untill then to unblock test teams we can use this.

@vkraleti
Copy link
Copy Markdown
Contributor

vkraleti commented Jan 6, 2026

@krishnachaitanya-linux IMHO using the kernel command line for this purpose is not appropriate. command line is for user configurations, not for masking underlying issues. The correct approach here is to root cause and fix the issues that are causing WLAN failures.

If disabling PCIe ASPM is indeed the ultimate fix, please apply it through the defconfig rather than via the kernel command line.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Jan 6, 2026

If disabling PCIe ASPM is indeed the ultimate fix, please apply it through the defconfig rather than via the kernel command line.

I think you mean DT / Driver here.

@ricardosalveti
Copy link
Copy Markdown
Contributor

@krishnachaitanya-linux IMHO using the kernel command line for this purpose is not appropriate. command line is for user configurations, not for masking underlying issues. The correct approach here is to root cause and fix the issues that are causing WLAN failures.

+1, we should work to avoid any custom kernel command line here, as we want the kernel to work as it would work on any other generic distribution (e.g. with systemready we are not supposed to add custom kernel command line arguments).

So NAK from my side.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Jan 19, 2026

@Mani-Sadhasivam do we have a conclusion on how this should be handled? Should ASPM be disabled for those platforms?

@Mani-Sadhasivam
Copy link
Copy Markdown
Member

@krishnachaitanya-linux If the ASPM root cause is not yet found, then disable ASPM for Root Port in controller driver based on the board compatible.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Jan 30, 2026

Per @Mani-Sadhasivam , this should be handled in the kernel driver. I totally agree with that conclusion. Closing.

@lumag lumag closed this Jan 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants