From: Daniel Mack <zonque@gmail.com>
To: linux-wireless@vger.kernel.org, Bing Zhao <bzhao@marvell.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Andreas Fenkart <andreas.fenkart@streamunlimited.com>,
Amitkumar Karwar <akarwar@marvell.com>
Subject: mwifiex_sdio problem: firmware fails to be active in time
Date: Thu, 18 Oct 2012 01:50:32 +0200 [thread overview]
Message-ID: <507F4448.2040707@gmail.com> (raw)
Hi,
we're trying to get a SD8787 to play which is connected via SDIO to an
OMAP hsmmc (AM33xx hardware). This fails with the following message:
# modprobe mwifiex_sdio
[ 13.984779] [sched_delayed] sched: RT throttling activated
[ 22.401700] mwifiex_sdio mmc0:0001:1: FW failed to be active in time
The firmware sd8787_uapsta.bin was taken from the linux-firmware.git and
apparently is transferred successfully, but then consequently fails to
do start up. When compiled with CONFIG_MMC_CONFIG=y, tons of successful
messages are logged like this:
[ 2607.867660] mmc0: starting CMD52 arg 00000a00 flags 00000195
[ 2607.867713] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 2607.883273] mmc0: starting CMD52 arg 00000a00 flags 00000195
[ 2607.883327] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 2607.898905] mmc0: starting CMD52 arg 00000a00 flags 00000195
The kernel we're based on is Linus' current merge tree (3.7-rc1), but
earlier version (3.6) have shown the same issue.
Before we start digging into this, I want to ask whether there are any
common pitfalls we should be aware of and that could cause this?
Please let me know whether you need any further information.
Many thanks,
Daniel
next reply other threads:[~2012-10-17 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 23:50 Daniel Mack [this message]
2012-10-18 0:20 ` mwifiex_sdio problem: firmware fails to be active in time Bing Zhao
2012-10-18 16:08 ` Daniel Mack
[not found] ` <CAMXE1-qWOKphtOjUYWUz1CLDUtAynODvHmLm60rJMC=jBtRsNw@mail.gmail.com>
2012-10-26 20:58 ` Daniel Mack
2012-10-28 15:49 ` Daniel Mack
2012-11-01 9:48 ` Andrei Emeltchenko
2012-11-01 11:10 ` Daniel Mack
2012-11-01 9:46 ` Andrei Emeltchenko
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=507F4448.2040707@gmail.com \
--to=zonque@gmail.com \
--cc=akarwar@marvell.com \
--cc=andreas.fenkart@streamunlimited.com \
--cc=bzhao@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).