On Mon, Nov 13, 2017 at 4:48 PM, Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> wrote: > Enabling MSI by default is just too invasive, ath9k is used in so many > different enviroments that risk of regressions is high. MSI needs a lot > of testing before we can even consider enabling it by default. And it seems like we already found a regression here - the MSI Message Data is being corrupted as described in my last mail. Can't be fixed in firmware, but it would be good to have confirmation of the hardware behavivour, and maybe some other solution is possible? Are you following this up within Qualcomm? >> I have tested your patch on Acer Aspire ES1-432. It does not work - >> I still can't connect to wifi. >> /proc/interrupts shows that no MSI interrupts are delivered, the >> counters are 0. >> >> lspci -vv shows: >> Capabilities: [50] MSI: Enable+ Count=1/4 Maskable+ 64bit+ >> Address: 00000000fee0f00c Data: 4142 >> Masking: 0000000e Pending: 00000000 >> >> So MSI is enabled and the vector number is 0x42 (decimal 66). >> However my kernel log is now totally spammed with: >> do_IRQ: 0.64 No irq handler for vector >> >> My assumption here is that the ath9k hardware implementation of >> MSI is buggy, and it is therefore corrupting the MSI vector number >> by zeroing out the lower 2 bits (e.g. 66 -> 64). Thanks Daniel
