From mboxrd@z Thu Jan  1 00:00:00 1970
From: Petr =?iso-8859-2?Q?=A9tetiar?= <ynezz@true.cz>
Date: Fri, 19 Nov 2010 12:05:59 +0100
Subject: [ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error
Message-ID: <20101119110559.GO15069@ibawizard.net>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Hi,

I've USB WiFi stick with VID 0x0cf3 and PID 0x1006, it's TPLink TL-WN422Gv2.
Everything works fine, even the WPA, but until I reset my board (it's ARMv4t
ts7250/mach-ep93xx). Then if the driver is loaded again, it ends with
"ath9k_htc: Target is unresponsive" error. If I replug the device, or power
on/off the board everything starts to work again without any problem, so maybe
the driver is somehow stuck somewhere?

I've tried to rmmod all the modules, but it's still same error, then I've
tried to increase the wait_for_completion_timeout[1] from HZ to HZ*8, but it
didn't helped anyway. Looks like the problem somewhere deeper, like that the
device is left in some undefined state, or maybe some timing/USB problem?

Any hint what could get wrong at this stage? How to debug this? Is it possible
to perform some reset of the device, so I can "emulate" replug of the device?
It's pretty easy to reproduce, happens always, so it shouldn't be that hard to
find the root cause of the problem. Thank you for any hints.

1. line 128 in htc_drv_init.c time_left = wait_for_completion_timeout(&priv->htc->target_wait, HZ);

-- ynezz