linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Alan Cooper <alcooperx@gmail.com>
Cc: linux-mmc@vger.kernel.org,
	Girish K S <girish.shivananjappa@linaro.org>,
	Ulf Hansson <ulf.hansson@stericsson.com>,
	"Nath, Arindam" <Arindam.Nath@amd.com>,
	Philip Rakity <prakity@marvell.com>
Subject: Re: [PATCH] mmc: Prevent 1.8V switch for SD hosts that don't support UHS modes.
Date: Mon, 02 Apr 2012 20:42:27 -0400	[thread overview]
Message-ID: <87r4w5ir2k.fsf@laptop.org> (raw)
In-Reply-To: <CAOGqxeWdOjkSTa2N5GwCvGb02zge+66_CT=0u7upznoWVfUCcw@mail.gmail.com> (Alan Cooper's message of "Mon, 2 Apr 2012 14:29:18 -0400")

Hi Al,

On Mon, Apr 02 2012, Alan Cooper wrote:
> Still hoping for comments on the patch.

Thanks for the reminder; adding a few potential reviewers to CC:.

- Chris.

> On Fri, Mar 16, 2012 at 3:54 PM, Al Cooper <acooper@gmail.com> wrote:
>> The driver should not try to switch to 1.8V when the SD 3.0 host
>> controller does not have any UHS capabilities bits set (SDR50, DDR50
>> or SDR104). See page 72 of "SD Specifications Part A2 SD Host
>> Controller Simplified Specification Version 3.00" under
>> "1.8V Signaling Enable". Instead of setting SDR12 and SDR25 in the host
>> capabilities data structure for all V3.0 host controllers, only set them
>> if SDR104, SDR50 or DDR50 is set in the host capabilities register. This
>> will prevent the switch to 1.8V later.
>>
>> Signed-off-by: Al Cooper <acooper@gmail.com>
>> ---
>>  drivers/mmc/host/sdhci.c |    5 +++--
>>  1 files changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
>> index 8d66706..cdf900e 100644
>> --- a/drivers/mmc/host/sdhci.c
>> +++ b/drivers/mmc/host/sdhci.c
>> @@ -2762,8 +2762,9 @@ int sdhci_add_host(struct sdhci_host *host)
>>            mmc_card_is_removable(mmc))
>>                mmc->caps |= MMC_CAP_NEEDS_POLL;
>>
>> -       /* UHS-I mode(s) supported by the host controller. */
>> -       if (host->version >= SDHCI_SPEC_300)
>> +       /* Any UHS-I mode in caps implies SDR12 and SDR25 support. */
>> +       if (caps[1] & (SDHCI_SUPPORT_SDR104 | SDHCI_SUPPORT_SDR50 |
>> +                      SDHCI_SUPPORT_DDR50))
>>                mmc->caps |= MMC_CAP_UHS_SDR12 | MMC_CAP_UHS_SDR25;
>>
>>        /* SDR104 supports also implies SDR50 support */
>> --
>> 1.7.6

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2012-04-03  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 19:54 [PATCH] mmc: Prevent 1.8V switch for SD hosts that don't support UHS modes Al Cooper
2012-04-02 18:29 ` Alan Cooper
2012-04-03  0:42   ` Chris Ball [this message]
2012-04-04  3:46     ` Nath, Arindam
2012-04-04  3:58       ` Philip Rakity
2012-04-04  4:31         ` Girish K S
2012-04-04 13:13       ` 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=87r4w5ir2k.fsf@laptop.org \
    --to=cjb@laptop.org \
    --cc=Arindam.Nath@amd.com \
    --cc=alcooperx@gmail.com \
    --cc=girish.shivananjappa@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@marvell.com \
    --cc=ulf.hansson@stericsson.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;
as well as URLs for NNTP newsgroup(s).