From: Daniel Mack <zonque@gmail.com>
To: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>,
Bing Zhao <bzhao@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
"Porter, Matt" <mporter@ti.com>
Subject: Re: mwifiex_sdio problem: firmware fails to be active in time
Date: Sun, 28 Oct 2012 16:49:02 +0100 [thread overview]
Message-ID: <508D53EE.7050405@gmail.com> (raw)
In-Reply-To: <508AF992.8070606@gmail.com>
On 26.10.2012 22:58, Daniel Mack wrote:
> [have to re-open this issue again]
>
> On 21.10.2012 16:16, Andrei Emeltchenko wrote:
>> I have the same board and see this problem sometimes. Reloading modules
>> might help, if not reboot always works :).
>
> I thought I solved this issue, but I can't reproduce the running version
> anymore unfortunately. It constantly fails with the error I described,
> even though the clock and all voltages etc are definitely stable.
Ok, following up on my own writings: I solved this issue. It took me
awhile to figure out that the 88WSD8787 is really picky about the
clock/power sequencing. It really needs >= 1ms delay in the startup
phase, otherwise the firmware won't start up.
So if anyone has this problem, make sure to care for that very detail.
Daniel
next prev parent reply other threads:[~2012-10-28 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 23:50 mwifiex_sdio problem: firmware fails to be active in time Daniel Mack
2012-10-18 0:20 ` 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 [this message]
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=508D53EE.7050405@gmail.com \
--to=zonque@gmail.com \
--cc=akarwar@marvell.com \
--cc=andrei.emeltchenko.news@gmail.com \
--cc=bzhao@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mporter@ti.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).