From: Adrian Hunter <adrian.hunter@nokia.com>
To: Philip Rakity <prakity@marvell.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH] mmc: MMC 4.4 DDR support
Date: Fri, 08 Oct 2010 10:02:21 +0300 [thread overview]
Message-ID: <4CAEC1FD.6060607@nokia.com> (raw)
In-Reply-To: <DFA7B5FE-718A-484B-BA1D-D1B44E3A5A32@marvell.com>
On 01/10/10 06:01, ext Philip Rakity wrote:
>
> I was wondering if we could remove one of the CAPS for DDR voltage (MMC_CAP_1_8V_DDR and MMC_CAP_1_2V_DDR). Both 1.2 and 1.8v are defined in the JEDEC Standard No. 84-A441.
>
> The sd 3.0 host controller only defines the option for 1.8v. I cannot see a way to set 1.2v.
>
> If this makes sense I can prepare a patch.--
If the host controller does not support 1.2V DDR then it should definitely
not set MMC_CAP_1_2V_DDR. That is precisely what the caps are for.
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-10-08 7:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 3:01 [PATCH] mmc: MMC 4.4 DDR support Philip Rakity
2010-10-08 7:02 ` Adrian Hunter [this message]
2010-10-08 15:26 ` Philip Rakity
-- strict thread matches above, loose matches on Subject: below --
2010-07-09 6:59 Hanumath Prasad
2010-07-09 6:59 ` Hanumath Prasad
2010-07-10 5:28 ` Kyungmin Park
2010-07-10 5:29 ` Kyungmin Park
[not found] ` <81C3A93C17462B4BBD7E272753C10579169F9BD429@EXDCVYMBSTM005.EQ1STM.local>
2010-07-13 1:14 ` Kyungmin Park
2010-08-21 22:30 ` Linus Walleij
2010-08-21 22:37 ` Chris Ball
2010-08-23 7:21 ` Linus Walleij
2010-08-23 20:48 ` Matt Fleming
2010-08-23 21:28 ` Andrew Morton
2010-08-24 10:30 ` Adrian Hunter
2010-09-14 11:21 ` Chris Ball
2010-09-15 9:32 ` Ghorai, Sukumar
2010-09-20 4:34 ` Ghorai, Sukumar
2010-09-22 2:20 ` Chris Ball
2010-09-30 8:06 ` zhangfei gao
2010-09-30 22:30 ` Chris Ball
2010-09-30 22:29 ` Chris Ball
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=4CAEC1FD.6060607@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.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.