diff options
| author | Kalle Valo <kvalo@qca.qualcomm.com> | 2013-03-09 12:01:50 +0200 |
|---|---|---|
| committer | Kalle Valo <kvalo@qca.qualcomm.com> | 2013-03-18 13:38:37 +0200 |
| commit | 44af34428dfdce0472cb229b013c72710285d2db (patch) | |
| tree | 72be0a7711e2aa907b6b43c7b9b3576ff0f52b16 /drivers/net/wireless/ath/ath6kl/Kconfig | |
| parent | 4e1609c9eec2bf9971004fce8b65c0877d5ae600 (diff) | |
| download | talos-op-linux-44af34428dfdce0472cb229b013c72710285d2db.tar.gz talos-op-linux-44af34428dfdce0472cb229b013c72710285d2db.zip | |
ath6kl: cold reset target after host warm boot
Julien reported that ar6004 usb device fails to initialise
after host has been rebooted and power is still on for the ar6004 device. He
found out that doing a cold reset fixes the issue.
I wasn't sure what would be the best way to detect if target needs a reset so I
settled on checking a timeout from htc_wait_recv_ctrl_message().
Reported-by: Julien Massot <jmassot@aldebaran-robotics.com>
Tested-by: Julien Massot <jmassot@aldebaran-robotics.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat (limited to 'drivers/net/wireless/ath/ath6kl/Kconfig')
0 files changed, 0 insertions, 0 deletions
