From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <drwho@infidigm.net>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qca.qualcomm.com>
Subject: Re: AR9374 v1.3 (Ath6kl - 6004) in sdio mode
Date: Tue, 19 Mar 2013 07:25:58 +0200 [thread overview]
Message-ID: <877gl43qqh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <a10f9fe2e0e48f8b7378bb655d673151.squirrel@www.infidigm.net> (drwho@infidigm.net's message of "Mon, 18 Mar 2013 13:53:04 -0400")
<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
prev parent reply other threads:[~2013-03-19 5:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 17:53 AR9374 v1.3 (Ath6kl - 6004) in sdio mode drwho
2013-03-19 5:25 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gl43qqh.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qca.qualcomm.com \
--cc=drwho@infidigm.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).