I’m having a similar problem with a 5g card in the b-key slow (see GitHub issue here) and I’m seeing very similar issues in the kernel log.
[ 0.043952] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 0.043971] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 0.043983] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000
[ 0.043995] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000
[ 0.044096] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[ 0.044107] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[ 0.044116] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000
[ 0.044126] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000
[ 0.044144] /soc/pcie@11290000: Failed to get clk index: 0 ret: -517
[ 0.044152] mtk-pcie-gen3 11290000.pcie: failed to get clocks
[ 0.044212] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[ 0.044221] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[ 0.044230] mtk-pcie-gen3 11300000.pcie: IO 0x0030000000..0x00301fffff -> 0x0030000000
[ 0.044239] mtk-pcie-gen3 11300000.pcie: MEM 0x0030200000..0x0037ffffff -> 0x0030200000
[ 0.044254] /soc/pcie@11300000: Failed to get clk index: 0 ret: -517
[ 0.044262] mtk-pcie-gen3 11300000.pcie: failed to get clocks
[ 0.044332] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges:
[ 0.044342] mtk-pcie-gen3 11310000.pcie: Parsing ranges property...
[ 0.044350] mtk-pcie-gen3 11310000.pcie: IO 0x0038000000..0x00381fffff -> 0x0038000000
[ 0.044359] mtk-pcie-gen3 11310000.pcie: MEM 0x0038200000..0x003fffffff -> 0x0038200000
[ 0.044374] /soc/pcie@11310000: Failed to get clk index: 0 ret: -517
[ 0.044381] mtk-pcie-gen3 11310000.pcie: failed to get clocks
...
[ 2.646088] mtk-pcie-gen3: probe of 11280000.pcie failed with error -110
[ 2.653130] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[ 2.660441] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[ 2.666703] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000
[ 2.675138] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000
[ 3.017289] mtk-pcie-gen3 11290000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
I think the first bridge is the mPCIe slots (where I have a QCNFA765 working fine - this is having no issues with the ath11k driver). The second and 3rd pci bridges seem like they are the B and M key slots.
What’s interesting is that I am able to get the 5g modem in the B slot to be recognized when I boot with the Bpi-provided image, but it’s not showing up in nightlies.
It seems like something to do with the device tree.