From: "Richard Purdie" <rpurdie@rpsys.net>
To: "Pierre Ossman" <drzeus-list@drzeus.cx>
Cc: "Russell King" <rmk+lkml@arm.linux.org.uk>,
"Ian Molton" <spyro@f2s.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: MMC Driver RFC
Date: Mon, 17 Jan 2005 09:53:51 -0000 [thread overview]
Message-ID: <00d501c4fc7a$76ef9940$0f01a8c0@max> (raw)
In-Reply-To: 41EB5610.1080708@drzeus.cx
Pierre Ossman:
> I fail to see what this delay does. A few lines further down you have a
> mmc_delay which you have removed. That delay was added just to give slow
> cards enough time to power up.
I hadn't realised that delay had been added. It wasn't present in the older
code I was working against and when I upgraded, I've failed to notice it had
been added. Adding that will solve all the problems I was seeing.
> I, personally, would really like to see SD support included in the main
> kernel. But I can also fully understand if that's not currently possible.
I think the way forward is for someone to propose a patch. Your code sounds
the most advanced but Ian or myself may be prepared to propose something if
you don't want to. A decision can then be made about whether it can be
accepted. There have been no objections raised so far - just words of
caution.
Richard
next prev parent reply other threads:[~2005-01-17 9:59 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
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 [this message]
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='00d501c4fc7a$76ef9940$0f01a8c0@max' \
--to=rpurdie@rpsys.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.