public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Philip Langdale <philipl@overt.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Carlos Aguiar <carlos.aguiar@indt.org.br>,
	juha.yrjola@solidboot.com
Subject: Re: [PATCH] MMC: Clean up low voltage range handling
Date: Mon, 12 Mar 2007 00:39:54 +0100	[thread overview]
Message-ID: <45F4934A.3030303@drzeus.cx> (raw)
In-Reply-To: <45F33C2C.2090905@overt.org>

Philip Langdale wrote:
> Clean up the handling of low voltage MMC cards.
>
>   
> The latest MMC and SD specs both agree that the low
> voltage range is defined as 1.65-1.95V and is signified
> by bit 7 in the OCR. An old Sandisk spec implied that
> bits 7-0 represented voltages below 2.0V in 1V increments,
> and the code was accordingly written with that expectation.
>
>   

We must not have the same specs. My simplified SD 2.0 physical spec
defines everything below bit 15 as reserved.

> This change switches the code to conform to the specs and
> fixes the SDHCI driver. It also removes the explicit
> defines for the host vdd and updates the SDHCI driver
> to convert the bit number back to the mask value
> for comparisons. Having only a single set of defines
> ensures there's nothing to get out of sync.
>
>   

Although this is a nice change, it confuses things to have two changes
in one commit. Could you split them up and base it on my "for-andrew"
branch?

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org


  reply	other threads:[~2007-03-11 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10 23:15 [PATCH] MMC: Clean up low voltage range handling Philip Langdale
2007-03-11 23:39 ` Pierre Ossman [this message]
2007-03-12  0:13   ` Philip Langdale

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=45F4934A.3030303@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=carlos.aguiar@indt.org.br \
    --cc=juha.yrjola@solidboot.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipl@overt.org \
    /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