linux-kernel - Re: [PATCH 1/2] MMC/pxamci: workaround regulator framework bugs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090629094311.GD11855@sirena.org.uk>
Date:	Mon, 29 Jun 2009 10:43:11 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Eric Miao <eric.y.miao@...il.com>
Cc:	Daniel Ribeiro <drwyrm@...il.com>,
	Pierre Ossman <pierre@...man.eu>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	openezx-devel <openezx-devel@...ts.openezx.org>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-arm-kernel <linux-arm-kernel@...ts.arm.linux.org.uk>
Subject: Re: [PATCH 1/2] MMC/pxamci: workaround regulator framework bugs

On Mon, Jun 29, 2009 at 11:00:38AM +0800, Eric Miao wrote:

> This looks to be running into the same issue as clocks - where for power
> savings the clocks are assumed to be off as many as possible, leaving only
> those essential ones enabled, yet the assumption of the boot loader does
> this correctly is always a big problem, putting this into the kernel,
> however, is ugly.

At the minute the regulator API actually copes pretty well with this -
the only problem I'm aware of is with drivers like the MMC driver which
require exclusive control of the regulator.  With other drivers the core
API can clean up after startup and the drivers never need to worry about
fixing things up.
--
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/