From: Pierre Ossman <drzeus@drzeus.cx>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Andrew Victor <linux@maxim.org.za>,
Ville Syrjala <syrjala@sci.fi>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] at91_mci: Enable MMC_CAP_SDIO_IRQ only when it actually works
Date: Sat, 19 Jul 2008 01:01:43 +0200 [thread overview]
Message-ID: <20080719010143.142d59a0@mjolnir.drzeus.cx> (raw)
In-Reply-To: <48809B00.1070405@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On Fri, 18 Jul 2008 15:30:40 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> Pierre Ossman :
> >
> > Not all SDIO cards use 4-bit mode, so it looks to me like you have to
> > disable it completely (unless there's a third revision where it works
> > without any fine print?).
>
> Well, I understand.
>
> In your opinion, a printed warning that says to be sure to use only
> 4-bit mode SDIO cards on slot B... is not acceptable ?
>
It's not really up to the user. The SDIO spec does not mandate 4-bit
support, so some cards will not have it.
> It kind of disappoints me to remove this feature as the
> at91sam9260ek/9xe/9g20 board uses only slot B, and I really like to
> connect SDIO with IRQ on it.
>
I haven't seen the erratum, but is there no way to poke the hardware
into getting the interrupt running even in 1-bit mode?
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-18 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 9:34 Nicolas Ferre
2008-07-17 10:55 ` Pierre Ossman
2008-07-18 13:30 ` Nicolas Ferre
2008-07-18 23:01 ` Pierre Ossman [this message]
2008-07-20 9:55 ` ian
2008-07-20 11:13 ` Pierre Ossman
2008-07-20 23:28 ` ian
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=20080719010143.142d59a0@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=syrjala@sci.fi \
/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
all inboxes | Powered by JetHome®