From: manuel.stahl@iis.fraunhofer.de (Manuel Stahl)
To: linux-arm-kernel@lists.infradead.org
Subject: atmel-mci / at91_mci
Date: Mon, 22 Feb 2010 10:56:47 +0100 [thread overview]
Message-ID: <4B8254DF.8090602@iis.fraunhofer.de> (raw)
In-Reply-To: <4B797349.4030902@who-ing.de>
Am 15.02.2010 17:16, schrieb Sebastian Heutling:
> On 02/09/10 16:49, Manuel Stahl wrote:
>> Unfortunately this is not the problem. The SD-card works fine with the
>> old at91_mci driver, but not with the newer atmel-mci. The problem is
>> that I need both slots at the same time, so at91_mci is no option for me.
>>
>> In the second slot there is a WLAN card which gets timeouts after
>> successful firmware load with at91_mci but does not work with atmel-mci.
>>
>> I have exactly the same setup with an AVR32 processor, there both
>> devices work. With the atmel-mci driver obiously.
>
> Could that be related to the "SLOT_B" bit in the SDCR?
> I had to set it in U-Boot to get the second slot working properly.
> My guess is that on AT91 (we use SAM9G20) every access needs to set or
> clear that bit depending on which slot is addressed.
No there was a bug in the atmel_mci driver for 2.6.27 related to SDCR.
With at91_mci you can only use one slot at a time, which is configured
in the board setup code. The at91_mci driver communicates with the right
slot, it can even download the firmware. Until then all SDIO traffic is
OK, after the download there are timeouts. Maybe the restart of the
device with the new firmware is not working properly.
Regards,
--
Dipl.-Inf. Manuel Stahl
Fraunhofer-Institut f?r Integrierte Schaltungen IIS
- Leistungsoptimierte Systeme -
Nordostpark 93 Telefon +49 (0)911/58061-6419
90411 N?rnberg Fax +49 (0)911/58061-6398
http://www.iis.fraunhofer.de manuel.stahl at iis.fraunhofer.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6148 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100222/1a8980b6/attachment.p7s>
prev parent reply other threads:[~2010-02-22 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 8:57 atmel-mci / at91_mci Manuel Stahl
2010-02-08 13:13 ` Fabian Godehardt
2010-02-09 15:49 ` Manuel Stahl
2010-02-15 16:16 ` Sebastian Heutling
2010-02-22 9:56 ` Manuel Stahl [this message]
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=4B8254DF.8090602@iis.fraunhofer.de \
--to=manuel.stahl@iis.fraunhofer.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).