From: Pierre Ossman <drzeus@drzeus.cx>
To: ian <spyro@f2s.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Andrew Victor <linux@maxim.org.za>,
David Brownell <david-b@pacbell.net>
Subject: Re: [PATCH 1/3] at91_mci: Enable MMC_CAP_SDIO_IRQ only when it actually works
Date: Sun, 20 Jul 2008 13:13:10 +0200 [thread overview]
Message-ID: <20080720131310.74d83d54@mjolnir.drzeus.cx> (raw)
In-Reply-To: <1216547739.3200.5.camel@wirenth>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
On Sun, 20 Jul 2008 10:55:39 +0100
ian <spyro@f2s.com> wrote:
> On Sat, 2008-07-19 at 01:01 +0200, Pierre Ossman wrote:
> > > 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.
>
> That seems overly rigid.
>
> its not linux violating the spec, its the SDIO controller in this case.
>
> I see no harm in supporting what the hardware is actually capable of.
>
> It wouldnt be the first bit of broken hardware supported by linux.
>
It does tend to make a mess of things when you start adding up all the
gotchas of each and every broken controller out there (it seems like
every controller decides to violate the spec in their own creative
way).
What about David's idea? Reconfiguring the PIN to be a GPIO pin with an
interrupt shouldn't be that difficult?
Rgds
--
-- 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-20 11:13 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
2008-07-20 9:55 ` ian
2008-07-20 11:13 ` Pierre Ossman [this message]
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=20080720131310.74d83d54@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=david-b@pacbell.net \
--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=spyro@f2s.com \
/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®