[ath9k-devel] need help: ath9k_htc driver not working

[Oleksij Rempel <linux@rempel-privat.de>]

Hi Izhar,

Am 15.04.2013 14:48, schrieb izhar eyal:
> Hi Guys,
> I hope this is the right mailing list for help on bugs.
>
> Here are the detail:
> - have kernel 2.6.35.13 running on imx27, trying to use a TL-WN722N
> dongle (Atheros AR9271).

that is a bit too old.

> - compiled ath9k_htc (tried both as statically linked and as kernel
> modules, same problem)
> - using firmware htc_9271.fw (rev 1.3)...also tried older ones with same
> result

older should not work. but i do not know what firmware version was 
supported on this kernel.

> - firmware is loaded successfully by being compiled with the kernel (a
> menuconfig option, directory /firmware)

I'm not sure that firmware source would be available in this old kernel. 
Are you sure? Or do you mean, pre compiled firmware was build in in module?

> - using REG_READ to get device registers returns always the same value:
> 0x01020101
> this is why I get timeout on reading RTC register 0x7044 (probably the
> first read that uses ath9k_hw_wait function).

hmm... do this dongle gets enough power?


some parts of your dmesg are interesting:
--- this adapter was initiated at "usb 1-1:1.0"

> [    4.820000] usb 1-1: configuration #1 chosen from 1 choice
> [    4.820000] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> [    4.820000] usb 1-1:1.0: uevent
> [    4.820000] drivers/usb/core/inode.c: creating file '002'
> [    4.820000] usb 1-1: new device strings: Mfr=16, Product=32,
> SerialNumber=48
> [    4.820000] usb 1-1: Product: USB2.0 WLAN
> [    4.820000] usb 1-1: Manufacturer: ATHEROS
> [    4.820000] usb 1-1: SerialNumber: 12345
> [    4.820000] usbcore: registered new interface driver cdc_acm
> [    4.820000] cdc_acm: v0.25:USB Abstract Control Model driver for USB
> modems and ISDN adapters
> [    4.820000] usbcore: registered new interface driver libusual
> [    4.830000] usbcore: registered new interface driver usbserial
> [    4.830000] drivers/usb/serial/usb-serial.c: USB Serial support
> registered for generic

but now "1-1:1.0" is serial driver". Hmmm... do i miss some thing?

> [    4.830000] usbserial_generic 1-1:1.0: usb_probe_interface
> [    4.830000] usbserial_generic 1-1:1.0: usb_probe_interface - got id
> [    4.830000] usbcore: registered new interface driver usbserial_generic
> [    4.830000] drivers/usb/serial/usb-serial.c: USB Serial Driver core


now "1-1:1.0" is unregistred.

> <7>[  301.292000] usb 1-1: unregistering interface 1-1:1.0
> <7>[  301.292000] device: 'ep_01': device_unregister
> <7>[  301.292000] PM: Removing info for No Bus:ep_01

here is time out.

> <7>[  341.596000] *ath: timeout (100000 us) on reg 0x7044: 0x01020101 &
> 0x0000000f != 0x00000002*
> <7>[  341.596000] *ath: RTC not waking up*
> <7>[  341.596000] *ath: Couldn't reset chip*
> <7>[  341.596000] *ath: Unable to initialize hardware; initialization
> status: -5*
> <7>[  341.596000] ath: Unable to initialize hardware; initialization
> status: -5
> <3>[  341.596000] Failed to initialize the device
> <7>[  341.596000] usb 1-1: unlink qh1-0e01/c665a760 start 0 [1/3 us]
> <7>[  341.600000] usb usb1: clear tt buffer port 1, a3 ep2 t40008d80

and ath9k_hif_usb confirms that "1-1:1.0" is our device.

> <4>[  341.600000] ath9k_hif_usb: probe of 1-1:1.0 failed with error -22
> <7>[  341.600000] device: 'ep_01': device_add
> <7>[  341.600000] PM: Adding info for No Bus:ep_01
> <7>[  341.600000] device: 'ep_82': device_add
> <7>[  341.600000] PM: Adding info for No Bus:ep_82

i have some of ath9k_htc devices and all of them work with current 
firmware and 3.8.0-rc7 kernel... it is a bit old, but currently i do not 
have time to test never one.

> Is this a hardware issue?

try exclude some part from the chain. do this adapter works on other 
hardware? Do other usb hardware works on your host? For example usb 
stick? Is it working at full speed? Do usb hist provide enough power?

> software issue?

can you test this kernel on other host?

> can the system clock or other
> clocks be the issue?

i can't help you here.

> If you have any insights please respond.

You can use serial pins on the device to see if it is alive.
check this links:
https://github.com/qca/open-ath9k-htc-firmware/blob/master/docs/uart
http://wikidevi.com/wiki/AR9271

> thanks,
> izhar :)
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>


-- 
Regards,
Oleksij