linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Fuzzey <mfuzzey@parkeon.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Firmware problems with Lesswire Wibear  11n module using mwifiex
Date: Mon, 15 Apr 2013 14:55:44 +0200	[thread overview]
Message-ID: <516BF8D0.5070401@parkeon.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430D9DCBF173@SC-VEXCH1.marvell.com>

Hi Bing,

Thanks for your reply.
On 29/03/13 22:32, Bing Zhao wrote:
> Hi Martin,
>
>> [ 2210.066680] mwifiex_sdio mmc1:0001:1: WLAN FW is active
>> [ 2220.083880] mwifiex_sdio mmc1:0001:1: mwifiex_cmd_timeout_func:
>> Timeout cmd id (1584563353.27844) = 0xa9, act = 0x0
>>
>> This shows that there is no reply to the first command sent in
>> mwifiex_sta_init_cmd()
> There is a possibility that the firmware has responded to this command but the SDIO interrupt gets stuck somewhere.
>
> Are you able to hook up an oscilloscope to check whether SDIO DAT1 pin stays low or not?
Indeed,

DAT1 goes low after the command is sent and stays low until the card is 
reset.

No SDIO interrupts are received by the host controller (i.MX53)

So it looks like a host controller issue - right?

Regards,

Martin


  reply	other threads:[~2013-04-15 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 16:21 Firmware problems with Lesswire Wibear 11n module using mwifiex Martin Fuzzey
2013-03-29 21:32 ` Bing Zhao
2013-04-15 12:55   ` Martin Fuzzey [this message]
2013-04-15 23:41     ` Bing Zhao
2013-04-16  8:19       ` Martin Fuzzey

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=516BF8D0.5070401@parkeon.com \
    --to=mfuzzey@parkeon.com \
    --cc=bzhao@marvell.com \
    --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).