From: Matt Fleming <matt@console-pimps.org>
To: David Vrabel <david.vrabel@csr.com>
Cc: Philip Langdale <philipl@overt.org>,
Andrew Morton <akpm@linux-foundation.org>,
ohad@bencohen.org, ian@mnementh.co.uk, pierre@ossman.eu,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
nico@cam.org, nicolas.ferre@rfo.atmel.com, hskinnemoen@atmel.com,
tony@atomide.com, david-b@pacbell.net, manuel.lauss@gmail.com,
mirq-l@jasper.es
Subject: Re: New MMC maintainer needed
Date: Mon, 27 Jul 2009 22:40:01 +0100 [thread overview]
Message-ID: <20090727214001.GK12665@console-pimps.org> (raw)
In-Reply-To: <4A6D990B.9000005@csr.com>
On Mon, Jul 27, 2009 at 01:09:47PM +0100, David Vrabel wrote:
> Philip Langdale wrote:
> >
> > Both the (Simplified) SD and SDIO specifications do not formally
> > define the 'low voltage' range in the way the MMC spec does. ie: You
> > won't find anything in the SD specs that even tell you what the range
> > is - it just says that it exists.
>
> Standard SD/SDIO cards only support 2.7-3.6V.
>
> 1.8V operation is added in SD physical spec 3.00 and is part of any of
> the UHS-1 modes (SDR12-SDR104 and DDR50). It has a different timings
> and requires a different (3.00 compliant) host controller.
Is the 3.00 spec publicly available?
next prev parent reply other threads:[~2009-07-27 21:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:36 Pierre Ossman
2009-07-14 21:04 ` Ian Molton
2009-07-22 22:17 ` Andrew Morton
2009-07-23 0:08 ` Ian Molton
2009-07-23 5:54 ` Matt Fleming
2009-07-23 6:22 ` Andrew Morton
2009-07-23 6:42 ` Paul Mundt
2009-07-23 6:50 ` Ohad Ben-Cohen
2009-07-23 13:52 ` Matt Fleming
2009-07-24 22:29 ` Andrew Morton
2009-07-27 6:06 ` Philip Langdale
2009-07-27 12:09 ` David Vrabel
2009-07-27 21:40 ` Matt Fleming [this message]
2009-07-28 0:52 ` Philip Langdale
2009-07-28 12:51 ` David Vrabel
2009-07-23 7:01 ` Adrian Hunter
2009-07-23 7:25 ` Stephen Rothwell
2009-07-23 7:32 ` Andrew Morton
2009-07-23 7:38 ` Stephen Rothwell
2009-07-23 16:29 ` Andi Kleen
2009-07-23 10:57 ` Roberto A. Foglietta
2009-07-28 20:22 ` Pierre Ossman
2009-07-30 2:36 ` Segher Boessenkool
2009-07-28 20:20 ` Pierre Ossman
2009-07-28 21:14 ` Ian Molton
2009-07-28 22:41 ` Andrew Morton
2009-07-29 6:35 ` Sam Ravnborg
2009-07-29 10:35 ` Ian Molton
2009-07-28 20:23 ` Pierre Ossman
2009-07-31 10:26 ` Pierre Ossman
2009-07-31 10:54 ` Matt Fleming
2009-08-03 10:34 ` Pierre Ossman
2009-08-03 11:10 ` Matt Fleming
2009-08-03 11:13 ` Adrian Hunter
2009-08-03 21:41 ` Andrew Morton
2009-08-11 14:02 ` Matt Fleming
2009-08-12 22:27 ` Andrew Morton
2009-08-13 8:21 ` Matt Fleming
2009-08-13 7:01 ` Adrian Hunter
2009-08-13 17:03 ` Nicolas Pitre
2009-08-04 1:51 ` David Brownell
2009-08-05 1:42 ` David VomLehn
2009-08-06 8:54 ` Pierre Ossman
2009-08-18 9:33 ` Nicolas Ferre
2009-07-15 4:59 Alex Dubov
2009-07-31 13:36 ` Maxim Levitsky
2009-08-01 6:53 ` Alex Dubov
2009-08-01 7:21 ` Maxim Levitsky
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=20090727214001.GK12665@console-pimps.org \
--to=matt@console-pimps.org \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=david.vrabel@csr.com \
--cc=hskinnemoen@atmel.com \
--cc=ian@mnementh.co.uk \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=mirq-l@jasper.es \
--cc=nico@cam.org \
--cc=nicolas.ferre@rfo.atmel.com \
--cc=ohad@bencohen.org \
--cc=philipl@overt.org \
--cc=pierre@ossman.eu \
--cc=tony@atomide.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
Powered by JetHome