linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* AR9374 v1.3 (Ath6kl - 6004) in sdio mode
@ 2013-03-18 17:53 drwho
  2013-03-19  5:25 ` Kalle Valo
  0 siblings, 1 reply; 2+ messages in thread
From: drwho @ 2013-03-18 17:53 UTC (permalink / raw)
  To: linux-wireless; +Cc: ath6kl-devel

Can anyone confirm if they have had an AR9374 v1.3 (=AR6004) working in
sdio mode in compat v3.8?  I have three AR9374s working just fine in USB
mode with compat v3.8.  I have an AR6103 (=AR6003), sdio, working on the
same host as I'm trying the AR9374 on.  The AR9374 only gets as far as
registering as mmc1.  The vendor and device IDs are correct.  When I try
to load ath6kl_sdio, I get....

ath6kl: 8f69fe04
ath6kl: 8f69fe34
ath6kl: 8f69fe7c
ath6kl_sdio: probe of mmc1:0001:1 failed with error -110

loading ath6kl_core.ko debug_mask=0xffffffff doesn't give much more. 
compat is build with
export CONFIG_ATH_DEBUG=y
export CONFIG_ATH6KL_DEBUG=y
and I'm getting tones on debug when booting the AR6103.

My hardware settings for usb or sdio mode on the AR9374....

USB mode
sdio_cmd = 10k pull down

SDIO mode
sdio_cmd = 10k pull up to 3.3v
sdio_D1 = 10k pull up to 3.3v

I've tried dropping my sdio clock from 50Mhz to 10Mhz,  no go either.

Jon


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: AR9374 v1.3 (Ath6kl - 6004) in sdio mode
  2013-03-18 17:53 AR9374 v1.3 (Ath6kl - 6004) in sdio mode drwho
@ 2013-03-19  5:25 ` Kalle Valo
  0 siblings, 0 replies; 2+ messages in thread
From: Kalle Valo @ 2013-03-19  5:25 UTC (permalink / raw)
  To: drwho; +Cc: linux-wireless, ath6kl-devel

<drwho@infidigm.net> writes:

> Can anyone confirm if they have had an AR9374 v1.3 (=AR6004) working in
> sdio mode in compat v3.8?  I have three AR9374s working just fine in USB
> mode with compat v3.8.  I have an AR6103 (=AR6003), sdio, working on the
> same host as I'm trying the AR9374 on.  The AR9374 only gets as far as
> registering as mmc1.  The vendor and device IDs are correct.  When I try
> to load ath6kl_sdio, I get....
>
> ath6kl: 8f69fe04
> ath6kl: 8f69fe34
> ath6kl: 8f69fe7c
> ath6kl_sdio: probe of mmc1:0001:1 failed with error -110
>
> loading ath6kl_core.ko debug_mask=0xffffffff doesn't give much more. 
> compat is build with
> export CONFIG_ATH_DEBUG=y
> export CONFIG_ATH6KL_DEBUG=y
> and I'm getting tones on debug when booting the AR6103.
>
> My hardware settings for usb or sdio mode on the AR9374....
>
> USB mode
> sdio_cmd = 10k pull down
>
> SDIO mode
> sdio_cmd = 10k pull up to 3.3v
> sdio_D1 = 10k pull up to 3.3v
>
> I've tried dropping my sdio clock from 50Mhz to 10Mhz,  no go either.

Sounds like a hardware problem but difficult to say for sure. From
ath6kl point of view ar6003 and ar6004/ar9374 are not that different, at
least not that early on hardware initialisation.

-- 
Kalle Valo

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-03-19  5:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-03-18 17:53 AR9374 v1.3 (Ath6kl - 6004) in sdio mode drwho
2013-03-19  5:25 ` Kalle Valo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).