On 21 October 2014 10:17, Kalle Valo <[email protected]> wrote:
> Michal Kazior <[email protected]> writes:
>
>> In some cases hw recovery was taking an absurdly
>> long time due to ath10k waiting for things that
>> would never really complete.
>>
>> Instead of waiting for inevitable timeouts poke
>> all completions and wakequeues and check if it's
>> still worth waiting.
>>
>> Reading/writing ar->state requires conf_mutex.
>> Since waiters might be holding it introduce a new
>> flag CRASH_FLUSH so it's possible to tell waiters
>> to abort whatever they were waiting for.
>>
>> Signed-off-by: Michal Kazior <[email protected]>
>
> While applying to ath-next-test there was a conflict in core.h. Please
> check my resolution:
>
> https://github.com/kvalo/ath/commit/6cccda0185c7df96f439dc3f87961e81843de3ee
I think it was `enum ath10k_cal_mode {` vs `enum ath10k_scan_state {`
because my patch was based without your cal patches.
Anyway - looks good, thanks!
Michał
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
