Re: atheros ath9k_htc - EP4 Issue / BOGUS urb xfer, pipe 1 != type 3

Am 27.08.2017 um 01:31 schrieb M D:

Hi,
I am using the TPLink TL721N on an ARM MX21 platform, Linux Kernel 3.0

are there any reason to use such old kernel?

I am facing the following issue when the adapter is connected directly
to the USB Hub.

1) ifconfig -a does not show the wlan node
2) the adapter is detected on the USB bus
3) The ath9k_htc modules are loaded

...

AFTER A REBOOT
Once the above issue occurs, a software reboot renders the adapter not
to be enumerated/detected on the USB. That is a lsusb does not display
the model/serial of the adapter.

If repluging help you. You can try to implement USB link reinit after FW
was uploaded. Theoretically it is a proper way to init FW.

I can imagine following scenario:
- USB adabter is starting internal bootloader and inialize some USB Caps
- FW is uploaded with different USB Cups which a re expected by host driver.
- USB Host Controller has idea about changes because USB link should be
reinited to populate them.

To implement this FW should be patched to reset usb line after start and
driver should recognize some how a reseted FW (different USB id or what
ever)
However as I tried to implement it, the result was not the same on
different hosts. In some cases host turned the power off on device reset
and FW was lost, so driver tried to upload it again. May be I did some
thing wrong.

dmesg log:
usb 1-2: device descriptor read/64, error -110
usb 1-2: device descriptor read/64, error -110
usb 1-2: new full speed USB device number 5 using imx21-hcd
usb 1-2: device descriptor read/64, error -110
usb 1-2: device descriptor read/64, error -110
hub 1-0:1.0: unable to enumerate USB device on port 2


I referred to the instructions as mentioned here and ensured that
https://github.com/qca/open-ath9k-htc-firmware/wiki/usb-related-issues#bogus-urb-xfer-pipe-1--type-3

1) the driver has the patch
2) the firmware being used is 1.4

However the device is being configured in Full Speed mode.
usb 1-2: new full speed USB device number 2 using imx21-hcd

May be you will need just backport imx21-hcd patches too ;)

Could someone offer some suggestions if there are some workarounds in
the software? Is there anything more that I can try out or any areas I
can investigate to try and fix this issue? I am presently reading
through the device driver to see if I can fix it there, but am not
making much progress.

-- 
Regards,
Oleksij