diff options
| author | Stanislaw Gruszka <stf_xl@wp.pl> | 2021-11-11 17:10:03 +0300 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2021-11-29 13:53:50 +0300 |
| commit | ed53ae75693096f1c10b4561edd31a07b631bd72 (patch) | |
| tree | 266f5590582b2214458e4a1a1a0eadca337f21f5 /tools/perf/scripts/python | |
| parent | 2a9e9857473bfc5721092ff274bc1e371e5a0d2f (diff) | |
| download | linux-ed53ae75693096f1c10b4561edd31a07b631bd72.tar.xz | |
rt2x00: do not mark device gone on EPROTO errors during start
As reported by Exuvo is possible that we have lot's of EPROTO errors
during device start i.e. firmware load. But after that device works
correctly. Hence marking device gone by few EPROTO errors done by
commit e383c70474db ("rt2x00: check number of EPROTO errors") caused
regression - Exuvo device stop working after kernel update. To fix
disable the check during device start.
Link: https://lore.kernel.org/linux-wireless/bff7d309-a816-6a75-51b6-5928ef4f7a8c@exuvo.se/
Reported-and-tested-by: Exuvo <exuvo@exuvo.se>
Fixes: e383c70474db ("rt2x00: check number of EPROTO errors")
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/20211111141003.GA134627@wp.pl
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions