QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi Michal,

this is the dmesg output from a boot with kernel 4.1.2 with patch to
make the firmware load [1]

Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: enabling device (0000 -> 0002)
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
failed with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0 wlp3s0: renamed from wlan0

I saw the report you mentioned (I'm subscribed to ath10k and try to
keep it up with it). Not being expert at all I was not sure it was the
same or not. Also there seems to be a difference that with irq_mode=1
for me it just works like before.

[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060

On 28 July 2015 at 06:31, Michal Kazior <michal.kazior at tieto.com> wrote:
> On 27 July 2015 at 22:08, Enrico Tagliavini <enrico.tagliavini at gmail.com> wrote:
>> Hello there,
>>
>> I gave 4.2 rc3 a shot and I discovered the wireless was not working
>> anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
>> ath10k_core (I assume you need fw api 5 to remove this, is that
>> correct?, I still have fw 4 only).
>>
>> Loading with irq_mode=0
>>
>> [   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>
> There was already a similar report[1]. Just for the record: what
> number of interrupts did you have before 4.2-rc3? I assume it was "pci
> irq msi interrupts 1 irq_mode 0 reset_mode 0".
>
> My suspicion is that either the firmware is buggy and doesn't play
> well with multiple MSI interrupts or the MSI interrupt behaviour
> changed significantly (compared to qca988x) and this remained hidden
> because not an awful lot of machines seemed to have provided more than
> 1 msi interrupt for ath10k.
>
> [1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005695.html
>
>
> Michał