mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: David Brownell <david-b@pacbell.net>
Cc: lkml <linux-kernel@vger.kernel.org>, Tony Lindgren <tony@atomide.com>
Subject: Re: [patch 2.6.29-rc5] MMC: omap_hsmmc: only MMC1 allows HCTL.SDVS != 1.8V
Date: Wed, 18 Feb 2009 21:22:37 +0100	[thread overview]
Message-ID: <20090218212237.4cc73890@mjolnir.ossman.eu> (raw)
In-Reply-To: <200902171449.01646.david-b@pacbell.net>

On Tue, 17 Feb 2009 14:49:01 -0800
David Brownell <david-b@pacbell.net> wrote:

> From: David Brownell <dbrownell@users.sourceforge.net>
> 
> Based on a patch from Tony Lindgren ... after initialization,
> never change HCTL.SDVS except for MMC1.  The other controller
> instances only support 1.8V in that field, although they can
> suport other card/SDIO/eMMC/... voltages with level shifting
> solutions such as external transceivers.
> 
> MMC2 behavior sanity tested on Overo/WLAN, OMAP3430 SDP, and
> custom hardware.  MMC1 also sanity tested on those platforms
> plus Beagle.  This also fixes a bug preventing MMC2 (and also
> presumably MMC3) from powering down when requested.
> 
> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> ---

This suffers from the same problem as all other omap_hsmmc patches. Who
claims ownership of that driver?

-- 
     -- Pierre Ossman

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

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

  reply	other threads:[~2009-02-18 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 22:49 David Brownell
2009-02-18 20:22 ` Pierre Ossman [this message]
2009-02-18 20:52   ` Tony Lindgren

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=20090218212237.4cc73890@mjolnir.ossman.eu \
    --to=drzeus-mmc@drzeus.cx \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®