there is a function in driver "ath9k_htc_reset" http://lxr.free-electrons.com/source/drivers/net/wireless/ath/ath9k/htc_drv_main.c#L189 but not sure that is what you are looking for. 2013/5/15 Kalle Valo <kvalo@xxxxxxxxxxxxxxxx>: > Ignacy Gawedzki <i@xxxxxx> 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 > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@xxxxxxxxxxxxxxx > https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- Best regards, Eugene -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
