Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> writes: > 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@xxxxxxxxxxxxxxxxxxxxxx> > Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> I need to fix my line wrapping, the lines are too long now. > @@ -1842,12 +1853,6 @@ void ath6kl_stop_txrx(struct ath6kl *ar) > ath6kl_htc_stop(ar->htc_target); > } > > - /* > - * Try to reset the device if we can. The driver may have been > - * configure NOT to reset the target during a debug session. > - */ > - ath6kl_init_hw_reset(ar); > - This shouldn't be there and most likely causes an regression. I'll send v2 later. -- Kalle Valo -- 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