[ath9k-devel] ath9k_htc: Target is unresponsive

[Kalle Valo <kvalo@qca.qualcomm.com>]

Ignacy Gawedzki <i@lri.fr> writes:

> Hi everyone,
>
> This is an old issue, about which it seems the first posts date back to 2009.
> With the latest possible version of the firmware for AR9271 and the latest
> possible wireless drivers, the issue is still there.  Whether this is still
> the exact same problem every time remains to be checked, but it is annoying
> enough to deserve some consideration.
>
> The problem is that the driver can't talk to the device if the following
> conditions are met:
>
>  - The system cold boots with the USB dongle inserted or the USB dongle is
>    inserted on a running system.
>
>  - The interface is *not* brought up.
>
>  - The system (warm) reboots.
>
> Then the driver complains about the target being unresponsive after uploading
> the firmware.  Apparently the only way to make it work again is to unplug and
> then plug the USB dongle back, physically.  It seems that if the USB port is
> not powered down during reboot (which happens with at least two different
> setups that I've tested it with), the device is left in a broken state.
>
> I would gladly help in tracing down this bug if only I knew where to start.

With ath6kl a cold reset helped in a similar situation. Try to find if
ath9k_htc has a cold/warm reset and see if that helps.

-- 
Kalle Valo