ath10k: protect driver from unsolicited htc ep0 events
authorMichal Kazior <michal.kazior@tieto.com>
Wed, 11 Mar 2015 13:37:11 +0000 (14:37 +0100)
committerKalle Valo <kvalo@qca.qualcomm.com>
Thu, 19 Mar 2015 13:53:16 +0000 (15:53 +0200)
commit5dc0f1db41df905c19f95bb7809940f2debf0aef
tree29f2459702e37497e900ec56a6ba30d7940c344b
parent7e47e8e30f2ae10473eafbe8eaad4a0d17b3e656
ath10k: protect driver from unsolicited htc ep0 events

Some firmware revisions (tested with qca6174
rm2.0-00088) deliver unsolicited unknown (kind of
garbled) HTC ep0 event to host in some cases.

This issue was mainly observed with both qca988x
and qca6174 being installed on a single host
system. During driver probing if qca6174 booting
sequences were somehow deferred (e.g. by qca988x
implicitly making some resources busy presumably)
the unsolicited event would came around 1s after
ATH10K_HTC_MSG_READY_ID was delivered to host for
qca6174.

The unsolicited event would confuse driver and
cause HTT initialization (and subsequently
driver probing) to fail.

Make the ep0 event processing more robust. The
event will still be caught but instead will
only generate a warning now.

Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
drivers/net/wireless/ath/ath10k/htc.c