linux-kernel - Re: [patch 2.6.29-rc5] MMC: omap_hsmmc: only MMC1 allows HCTL.SDVS != 1.8V

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090218205214.GD11928@atomide.com>
Date:	Wed, 18 Feb 2009 12:52:14 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Pierre Ossman <drzeus-mmc@...eus.cx>
Cc:	David Brownell <david-b@...bell.net>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [patch 2.6.29-rc5] MMC: omap_hsmmc: only MMC1 allows HCTL.SDVS
	!= 1.8V

* Pierre Ossman <drzeus-mmc@...eus.cx> [090218 12:22]:
> On Tue, 17 Feb 2009 14:49:01 -0800
> David Brownell <david-b@...bell.net> wrote:
> 
> > From: David Brownell <dbrownell@...rs.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@...rs.sourceforge.net>
> > ---
> 
> This suffers from the same problem as all other omap_hsmmc patches. Who
> claims ownership of that driver?

Jarkko Lavinen has agreed to maintain it. Meanwhile, here's my
ack for this one:

Acked-by: Tony Lindgren <tony@...mide.com>

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/