From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ian Molton <spyro@f2s.com>
Subject: Re: MMC Driver RFC
Date: Wed, 12 Jan 2005 21:43:45 +0000 [thread overview]
Message-ID: <20050112214345.D17131@flint.arm.linux.org.uk> (raw)
In-Reply-To: <021901c4f8eb$1e9cc4d0$0f01a8c0@max>; from rpurdie@rpsys.net on Wed, Jan 12, 2005 at 09:10:12PM -0000
On Wed, Jan 12, 2005 at 09:10:12PM -0000, Richard Purdie wrote:
> 1. Card Detection Interrupts
>
> The MMC code completely misses card removals on my test hardware as when the
> interrupt triggers electrical contact is still fully functional.
>
> The PXA code calls mmc_detect_change() whenever an interrupt is detected.
> The MMC core then does a schedule_work(&host->detect). The problem is that
> when the interrupt is generated, the card may not be 100% inserted or 100%
> removed. Given the mechanical nature of insertions and removals, electrical
> contact is possible for a while after removal has been started (and a while
> before insertion is complete).
If your socket works like that, you need to handle that by using a timer
yourself. It normally only affects removal rather than insertion.
> 2. Card Initialisation Problems
>
> One of my cards works fine. The other works when I enable debug and doesn't
> when I don't. I suspect the delay while it does a printk gives something
> time to happen that doesn't normally when running at full speed!
Different cards behave differently. I suspect you have yet another
quirky card.
> I suspect this is related to the 1ms wait that was added to mmc_setup() as
> per comments. Is there any documentation which tells us exactly what timings
> we should be aiming for here? Has anyone else has problems like this?
There isn't any 1ms wait in mmc_setup().
> 3. SD Support
>
> Ian Molton seems to have added SD support to handhelds.org's kernel. I'm
> still trying to contact him to discuss this but the following patch enables
> SD cards to work for me:
> http://www.rpsys.net/openzaurus/2.6.11-rc1/mmc_sd-r1.patch
People are nervous about SD support - the SD forum has been traditionally
rather closed, and there is the perception that a SD card driver may not
go down well. I have even heard rumours of patent issues/IP issues in
this area, and I don't wish to get stung.
However, that said, the situation has improved recently - we've gone from
no documentation to limited documentation. However, this documentation
still isn't sufficient to do the job - eg, the SD formats for the CID
and CSD registers remain completely undocumented.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2005-01-12 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:10 MMC Driver RFC Richard Purdie
2005-01-12 21:43 ` Russell King [this message]
2005-01-12 22:07 ` Richard Purdie
2005-01-12 22:17 ` Russell King
2005-01-12 23:23 ` Ian Molton
2005-01-12 23:58 ` Richard Purdie
2005-01-14 11:37 ` Pierre Ossman
2005-01-14 14:55 ` Ian Molton
2005-01-16 12:22 ` Pierre Ossman
2005-01-16 13:19 ` Ian Molton
2005-01-16 19:43 ` Pierre Ossman
2005-01-16 23:17 ` Richard Purdie
2005-01-16 22:33 ` Alan Cox
2005-01-17 6:07 ` Pierre Ossman
2005-01-17 9:53 ` Richard Purdie
2005-01-17 11:59 ` Pierre Ossman
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=20050112214345.D17131@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--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