From: mkl@pengutronix.de (Marc Kleine-Budde)
To: linux-arm-kernel@lists.infradead.org
Subject: mx28 sdio problems
Date: Tue, 29 Mar 2011 12:05:45 +0200 [thread overview]
Message-ID: <4D91AEF9.4080401@pengutronix.de> (raw)
In-Reply-To: <20110326141312.GA17797@S2100-06.ap.freescale.net>
On 03/26/2011 03:13 PM, Shawn Guo wrote:
> On Fri, Mar 25, 2011 at 12:46:37PM +0100, Marc Kleine-Budde wrote:
>> On 02/22/2011 09:50 AM, Shawn Guo wrote:
>>> Signed-off-by: Shawn Guo <shawn.guo@freescale.com>
>>
>> I ported these patches to current mainline (the to be released
>> 2.6.39-rc1). mmc works with sd and sdhc cards without problems on my
>> mx28evk.
>>
>> However sdio doesn't work. When I plug a sdio wlan card the kernel gives
>> me the following error messages in a loop:
>>
>> [ 1002.760000] mmc1: new SDIO card at address 0001
>> [ 1003.760000] mmc1: card 0001 removed
>> [ 1003.810000] mmc1: new SDIO card at address 0001
>> [ 1004.810000] mmc1: card 0001 removed
>>
>> Any hints how to debug?
>>
> The only problem I had when testing an Atheros sdio wifi cards was
> the shortage of power supply on slot1 (internal regulator powered).
> The slot2 on mx28evk just works out of box with this sdio card. You
> also rework the board to get the slot1 be powered by external
> regulator just like slot2.
I just received an atheros sd25, the card gets recognized. No driver to
test more.
However with the old card the problem remains. On my sheeva plug I see
the same problems with the old card.
cheers, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110329/a2ea84e9/attachment.sig>
next prev parent reply other threads:[~2011-03-29 10:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 10:42 [PATCH v3] Add mmc device for i.MX23/28 Shawn Guo
2011-02-21 10:42 ` [PATCH v3 1/6] ARM: mxs/clock: fix base address missing in name##_set_parent Shawn Guo
2011-02-21 10:42 ` [PATCH v3 2/6] ARM: mxs: make ssp error irq definition consistent Shawn Guo
2011-02-22 8:20 ` Uwe Kleine-König
2011-02-21 10:42 ` [PATCH v3 3/6] ARM: mxs: dynamically allocate mmc device Shawn Guo
2011-02-22 8:31 ` Uwe Kleine-König
2011-02-22 12:39 ` Shawn Guo
2011-02-22 18:33 ` Uwe Kleine-König
2011-03-16 10:31 ` [PATCH v4 " Uwe Kleine-König
2011-02-21 10:42 ` [PATCH v3 4/6] ARM: mxs: fix typo "GPO" in iomux-mx23.h Shawn Guo
2011-02-25 20:55 ` Uwe Kleine-König
2011-02-21 10:42 ` [PATCH v3 5/6] ARM: mxs/mx23evk: add mmc device Shawn Guo
2011-02-21 17:42 ` Wolfram Sang
2011-02-22 8:33 ` Uwe Kleine-König
2011-02-22 12:22 ` Shawn Guo
2011-02-22 8:49 ` [PATCH v4] " Shawn Guo
2011-02-22 10:35 ` Wolfram Sang
2011-02-21 10:42 ` [PATCH v3 6/6] ARM: mxs/mx28evk: " Shawn Guo
2011-02-22 8:50 ` [PATCH v4] " Shawn Guo
2011-02-22 10:35 ` Wolfram Sang
2011-03-25 11:46 ` mx28 sdio problems (was: Re: [PATCH v4] ARM: mxs/mx28evk: add mmc device) Marc Kleine-Budde
2011-03-26 14:13 ` Shawn Guo
2011-03-29 10:05 ` Marc Kleine-Budde [this message]
2011-02-21 17:40 ` [PATCH v3] Add mmc device for i.MX23/28 Wolfram Sang
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=4D91AEF9.4080401@pengutronix.de \
--to=mkl@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).