From: Chris Ball <cjb@laptop.org>
To: Aaron Lu <aaron.lu@amd.com>
Cc: Philip Rakity <prakity@marvell.com>,
linux-mmc@vger.kernel.org, Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH v2 2/2] mmc: sd: Fix sd current limit setting
Date: Mon, 09 Jul 2012 22:57:40 -0400 [thread overview]
Message-ID: <87629wuxuj.fsf@octavius.laptop.org> (raw)
In-Reply-To: <20120704053148.GC2607@aarontestpc.amd.com> (Aaron Lu's message of "Wed, 4 Jul 2012 13:31:48 +0800")
Hi,
On Wed, Jul 04 2012, Aaron Lu wrote:
> Host has different current capabilities at different voltages, we need
> to record these settings seperately. The defined voltages are 1.8/3.0/3.3.
> For other voltages, we do not touch current limit setting.
>
> Before set current limit for the sd card, find out the host's operating
> voltage first and then find out the current capabilities of the host at
> that voltage to set the current limit.
>
> Signed-off-by: Aaron Lu <aaron.lu@amd.com>
> ---
> v2:
> Do not call BUG() when the host's voltage is not supported as suggested by
> Chris Ball.
> Do not use 0/1/2 to represent the host's voltage as suggested by Philip Rakity.
Thanks, pushed to mmc-next for 3.6.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-07-10 2:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 6:16 [PATCH 0/2] SD current limit setting fix Aaron Lu
2012-07-03 6:16 ` [PATCH 1/2] mmc: core: Simplify and fix for SD switch processing Aaron Lu
2012-07-04 0:48 ` Chris Ball
2012-07-03 6:16 ` [PATCH 2/2] mmc: sd: Fix sd current limit setting Aaron Lu
2012-07-03 14:18 ` Philip Rakity
2012-07-04 0:52 ` Chris Ball
2012-07-04 5:31 ` [PATCH v2 " Aaron Lu
2012-07-09 1:23 ` Philip Rakity
2012-07-10 2:57 ` Chris Ball [this message]
2012-07-17 9:34 ` [PATCH " Girish K S
2012-07-17 13:43 ` Aaron Lu
2012-07-17 15:43 ` Chris Ball
2012-07-18 5:09 ` Aaron Lu
2012-07-18 5:28 ` Chris Ball
2012-07-18 6:22 ` Aaron Lu
2012-07-19 2:41 ` Chris Ball
2012-07-19 3:47 ` Philip Rakity
2012-07-19 6:25 ` Chris Ball
2012-07-19 4:47 ` Girish K S
2012-07-19 5:03 ` 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=87629wuxuj.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=aaron.lu@amd.com \
--cc=aaron.lwe@gmail.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.