From: Daniel Mack <daniel@caiaq.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mmc@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: MXC MMC driver and SDIO peripherals
Date: Wed, 21 Oct 2009 21:20:38 +0200 [thread overview]
Message-ID: <20091021192038.GK14091@buzzloop.caiaq.de> (raw)
Hi,
we're having trouble getting SDIO connected harware to fly on MX31 based
designs. In particular, a SD8686 chip supported by the libertas_sdio
driver will hang forever when built without CONFIG_MMC_DEBUG=y. With
that option selected, however, the behaviour is a little different, and
I can at least see the following messages on a recent 2.6.32-rc5 based
MX31 tree.
Is there any common pitfall for such setups? I did more or less the same
thing on PXAs (same WLAN chip, same kind of interface, same firmware),
and haven't seen any such effects, so I suspect the MXC specific parts
to be the reason for that. Any ideas?
Thanks,
Daniel
[ 1.450000] mmc0: new SDIO card at address 0001
...
# modprobe libertas_sdio
[ 15.180000] libertas_sdio: Libertas SDIO driver
[ 15.180000] libertas_sdio: Copyright Pierre Ossman
[ 15.190000] libertas_sdio mmc0:0001:1: firmware: requesting sd8686_helper.bin
[ 15.320000] libertas_sdio mmc0:0001:1: firmware: requesting sd8686.bin
[ 15.840000] libertas: 00:19:88:03:13:5a, fw 8.73.7p3, cap 0x00000393
[ 16.870000] libertas: problem fetching packet from firmware
[ 18.840000] libertas: command 0x001e timed out
[ 18.840000] libertas: requeueing command 0x001e due to timeout (#1)
[ 18.870000] libertas: Received result 0 to command 1e after 1 retries
[ 18.910000] libertas: wlan0: Marvell WLAN 802.11 adapter
# ifconfig wlan0 up
[ 216.760000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 217.800000] libertas: problem fetching packet from firmware
[ 219.770000] libertas: command 0x0010 timed out
[ 219.770000] libertas: requeueing command 0x0010 due to timeout (#1)
[ 219.800000] libertas: Received result 0 to command 10 after 1 retries
# iwlist wlan0 scan
[ 244.260000] libertas: problem fetching packet from firmware
[ 247.800000] libertas: command 0x0006 timed out
[ 247.800000] libertas: requeueing command 0x0006 due to timeout (#1)
[ 248.260000] libertas: Received result 0 to command 6 after 1 retries
[ 249.920000] libertas: problem fetching packet from firmware
[ 253.560000] libertas: command 0x0006 timed out
[ 253.560000] libertas: requeueing command 0x0006 due to timeout (#1)
[ 254.920000] libertas: problem fetching packet from firmware
wlan0 Failed to read scan data : Resource temporarily unavailable
WARNING: multiple messages have this Message-ID (diff)
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: MXC MMC driver and SDIO peripherals
Date: Wed, 21 Oct 2009 21:20:38 +0200 [thread overview]
Message-ID: <20091021192038.GK14091@buzzloop.caiaq.de> (raw)
Hi,
we're having trouble getting SDIO connected harware to fly on MX31 based
designs. In particular, a SD8686 chip supported by the libertas_sdio
driver will hang forever when built without CONFIG_MMC_DEBUG=y. With
that option selected, however, the behaviour is a little different, and
I can at least see the following messages on a recent 2.6.32-rc5 based
MX31 tree.
Is there any common pitfall for such setups? I did more or less the same
thing on PXAs (same WLAN chip, same kind of interface, same firmware),
and haven't seen any such effects, so I suspect the MXC specific parts
to be the reason for that. Any ideas?
Thanks,
Daniel
[ 1.450000] mmc0: new SDIO card at address 0001
...
# modprobe libertas_sdio
[ 15.180000] libertas_sdio: Libertas SDIO driver
[ 15.180000] libertas_sdio: Copyright Pierre Ossman
[ 15.190000] libertas_sdio mmc0:0001:1: firmware: requesting sd8686_helper.bin
[ 15.320000] libertas_sdio mmc0:0001:1: firmware: requesting sd8686.bin
[ 15.840000] libertas: 00:19:88:03:13:5a, fw 8.73.7p3, cap 0x00000393
[ 16.870000] libertas: problem fetching packet from firmware
[ 18.840000] libertas: command 0x001e timed out
[ 18.840000] libertas: requeueing command 0x001e due to timeout (#1)
[ 18.870000] libertas: Received result 0 to command 1e after 1 retries
[ 18.910000] libertas: wlan0: Marvell WLAN 802.11 adapter
# ifconfig wlan0 up
[ 216.760000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 217.800000] libertas: problem fetching packet from firmware
[ 219.770000] libertas: command 0x0010 timed out
[ 219.770000] libertas: requeueing command 0x0010 due to timeout (#1)
[ 219.800000] libertas: Received result 0 to command 10 after 1 retries
# iwlist wlan0 scan
[ 244.260000] libertas: problem fetching packet from firmware
[ 247.800000] libertas: command 0x0006 timed out
[ 247.800000] libertas: requeueing command 0x0006 due to timeout (#1)
[ 248.260000] libertas: Received result 0 to command 6 after 1 retries
[ 249.920000] libertas: problem fetching packet from firmware
[ 253.560000] libertas: command 0x0006 timed out
[ 253.560000] libertas: requeueing command 0x0006 due to timeout (#1)
[ 254.920000] libertas: problem fetching packet from firmware
wlan0 Failed to read scan data : Resource temporarily unavailable
next reply other threads:[~2009-10-21 19:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 19:20 Daniel Mack [this message]
2009-10-21 19:20 ` MXC MMC driver and SDIO peripherals Daniel Mack
2009-10-21 20:15 ` Dan Williams
2009-10-21 20:15 ` Dan Williams
2009-10-21 20:51 ` Daniel Mack
2009-10-21 20:51 ` Daniel Mack
2009-10-22 8:19 ` Sascha Hauer
2009-10-22 8:19 ` Sascha Hauer
2009-10-22 11:05 ` tommy tommy
2009-10-22 16:41 ` Matt Hsu
2009-10-22 16:41 ` Matt Hsu
2009-10-28 16:47 ` Daniel Mack
2009-10-28 16:47 ` Daniel Mack
2009-10-28 17:06 ` Dan Williams
2009-10-28 17:06 ` Dan Williams
2009-10-28 17:19 ` Daniel Mack
2009-10-28 17:19 ` Daniel Mack
2009-10-28 18:46 ` Dan Williams
2009-10-28 18:46 ` Dan Williams
2009-10-29 10:27 ` Daniel Mack
2009-10-29 10:27 ` Daniel Mack
2009-11-02 20:00 ` Dan Williams
2009-11-02 20:00 ` Dan Williams
2009-10-28 17:11 ` Dan Williams
2009-10-28 17:11 ` Dan Williams
2009-10-28 17:21 ` Daniel Mack
2009-10-28 17:21 ` Daniel Mack
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=20091021192038.GK14091@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.