2297524_en-US

Yes

PCIe: i.MX 95: Allocate Multiple MSI IRQ Vectors

Hi,

We are using an ATH12K Wi‑Fi module on an i.MX95‑based system, connected via the PCIe2 instance.

On a kernel based on linux-imx lf‑6.12.y this setup fails, whereas with a kernel based on lf‑6.6.y it works as expected.

The kernel driver successfully requests and receives 16 MSI interrupts. However, it subsequently fails to bring up the Wi‑Fi module:

[ 5.888139] ath12k_pci 0001:01:00.0: Adding to iommu group 5
[ 5.888506] ath12k_pci 0001:01:00.0: BAR 0 [mem 0xa10000000-0xa101fffff 64bit]: assigned
[ 5.888553] ath12k_pci 0001:01:00.0: enabling device (0000 -> 0002)
[ 5.889315] ath12k_pci 0001:01:00.0: MSI vectors: 16
[ 5.889334] ath12k_pci 0001:01:00.0: Hardware name: wcn7850 hw2.0
[ 6.475718] ath12k_pci 0001:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
[ 6.475743] ath12k_pci 0001:01:00.0: fw_version 0x110cffff fw_build_timestamp 2025-06-25 09:26 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.115823.3
[ 7.647106] ath12k_pci 0001:01:00.0: failed to receive control response completion, polling..
[ 8.675241] ath12k_pci 0001:01:00.0: Service connect timeout
[ 8.681002] ath12k_pci 0001:01:00.0: failed to connect to HTT: -110
[ 8.692180] ath12k_pci 0001:01:00.0: failed to start core: -110

There was a related discussion on the kernel mailing list [1] with a different PCIe device, but it has not yet led to a working configuration for our system.

What would be the best way to proceed?

Thank you for your support.

Max

[1] https://lore.kernel.org/all/1819305.VLH7GnMWUR@steina-w/

Re: PCIe: i.MX 95: Allocate Multiple MSI IRQ Vectors

Hello,

The i,MX95 is in early stage and some configuration are not in design. However your i.MX95 with ATH12K via PCIe2 failing on

lf-6.12.y but working on lf-6.6.y suggests a regression or driver interaction change in newer kernel's PCIe or Wi-Fi stack, likely involving PCIe power management (ASPM), MSI mapping, or specific PCIe endpoint quirks for the ATH12K, often resolved by kernel patches or disabling ASPM in boot args for newer kernels; check dmesg for PCIe errors, compare devicetree, and look for related commits in NXP/Linux kernel mailing lists.

Here's a breakdown of potential causes and troubleshooting steps:

1. Check Kernel Logs (dmesg)

Look for PCIe Errors: Search for "PCI", "MSI", "ATH12K", "Error", "Firmware", or "Timeout" messages in dmesg on the failing lf-6.12.y kernel.
Firmware Loading: Verify the ath12k firmware is loaded correctly and if there are any errors during initialization.

2. PCIe Power Management (ASPM)

Common Issue: Newer kernels often enable Active State Power Management (ASPM) by default, which can cause issues with PCIe devices like the ATH12K on embedded systems, especially older firmware/hardware.
Try Disabling ASPM: Add pcie_aspm=off to your kernel boot arguments (e.g., in U-Boot or GRUB) and test again.

3. Devicetree/DTB Differences

Compare DTBs: Generate and compare the Device Tree Blobs (DTBs) used with both kernels (.dtb files). Look for changes in the PCIe node for pci2, especially related to interrupts, power domains, or compatibility properties.

4. Kernel Driver/Firmware Regressions

Specific Commits: The ATH12K driver (ath12k), mac80211, or core PCIe/ARM code in lf-6.12.y might have introduced a change breaking your setup.
Search Mailing Lists: Check the Linux Kernel Mailing Lists (LKML) and NXP's lists for related patches or discussions around ath12k, i.MX95, and newer kernels (6.12+).

5. MSI Handling

Interrupt Remapping: While you receive interrupts, the way they are handled (MSI-X vs. MSI, interrupt remapping) might have subtle changes.
Check Interrupts in proc/interrupts: See if the interrupt distribution or count differs between kernels.

6. Firmware Blobs

Firmware Version: Ensure you are using the correct firmware for the ATH12K, compatible with the newer kernel's driver. Sometimes newer drivers require newer firmware.

In summary, start with dmesg and try disabling ASPM; these are the most frequent culprits for PCIe Wi-Fi failures in newer kernels on embedded platforms

Regards

Re: PCIe: i.MX 95: Allocate Multiple MSI IRQ Vectors

While the suggestions were good pointers to debug the issue I couldn't find the solution, i.e. not all MSI IRQ vectors triggered the IRQ routines in the driver.

I ended up working around the issue by changing the ath12k driver to only request one MSI IRQ.

Note that current Linux master does not have the issue.

Regards

Max