From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale i.mx25 SDIO/Libertas issue
Date: Mon, 30 May 2011 23:03:35 -0300 [thread overview]
Message-ID: <BANLkTika2NNTmWNBmLC60GVMLTzXUS5X+A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=j3UXV6FMS6vkA+Vrpt3JjsNwMiA@mail.gmail.com>
Hi Daniel,
On Mon, May 30, 2011 at 6:50 AM, Daniel Mack <zonque@gmail.com> wrote:
> On Mon, May 30, 2011 at 3:52 AM, Andre Renaud <andre@bluewatersys.com> wrote:
>> Hello,
>> I am trying to use a Wi2Wi 802.11b/g (W2CBW009S) module attached to an
>> i.MX25 cpu, specifically the i.MX25 PDK from freescale, although I've
>> also tried it on a DeviceSolutions Topaz i.MX25. However it is unable to
>> fully load the driver, leaving me with the following in the logs:
>> [ ? 30.149097] libertas_sdio mmc0:0001:1: (unregistered net_device):
>> command 0x00a9 timed out
>> [ ? 30.153759] libertas_sdio mmc0:0001:1: (unregistered net_device):
>> Timeout submitting command 0x00a9
>> [ ? 30.158843] libertas_sdio mmc0:0001:1: (unregistered net_device):
>> PREP_CMD: command 0x00a9 failed: -110
>> [ ? 30.164126] libertas_sdio mmc0:0001:1: (unregistered net_device):
>> CMD_FUNC_INIT cmd failed
>> This wifi chip is based around the Marvell 8688 core.
>>
>> I have also tried using an 8686 device, and in that case it is unable to
>> even complete loading the firmware, failing with the following:
>> [ ? 14.753132] libertas_sdio: Firmware req_size: 17
>> [ ? 14.755713] libertas_sdio: failed to load firmware: -5
>> [ ? 14.759272] libertas_sdio: probe of mmc0:0001:1 failed with error -5
>> Note: I added the 'req_size: ' debugging message in
>
> I assume this error happens after the driver uploaded the helper
> firmware and switched to multi-block transfers?
>
> Which kernel version are you working on? I'm asking because I fixed a
> similar bug some months ago which I happend to see an a MX31 CPU with
> a 8686 attach to the SDIO bus. The MX3 MMC controller has bug severe
> bug in its CRC calculation code which causes multi-block transfers on
> a 4-bit bus to fail, and hence the only solution was to switch to a
> 1-bit bus. But I don't known whether this also affects MX25 cores.
The MX25 has a different SD controller (eSDHC) than the one found on
MX31 and such issue is not present.
Regards,
Fabio Estevam
next prev parent reply other threads:[~2011-05-31 2:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 1:52 Freescale i.mx25 SDIO/Libertas issue Andre Renaud
2011-05-30 9:50 ` Daniel Mack
2011-05-31 2:03 ` Fabio Estevam [this message]
2011-05-31 8:52 ` Daniel Mack
[not found] ` <4DE4110D.2090808@bluewatersys.com>
2011-05-31 8:56 ` Daniel Mack
2011-05-30 14:24 ` Alan Carvalho de Assis
2011-09-19 7:45 ` albert
2011-05-31 2:14 ` Andre Renaud
[not found] ` <4DE5E97D.90705@gmail.com>
2011-06-01 22:41 ` [Solved] " Andre Renaud
2011-09-15 15:59 ` Albert
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=BANLkTika2NNTmWNBmLC60GVMLTzXUS5X+A@mail.gmail.com \
--to=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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