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]

Date:	Tue, 30 Jun 2009 19:36:20 -0700
From:	David Brownell <david-b@...bell.net>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Eric Miao <eric.y.miao@...il.com>,
	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 Monday 29 June 2009, Mark Brown wrote:
> 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.

Which is a fairly typical situation for power-aware drivers.

Which belies your claim that the regulator API "copes pretty well".
It'd be more accurate to say "broken-as-designed", since you have
rejected numerous attempts to fix this, yet not fixed it yourself.


> With other drivers the core 
> API can clean up after startup and the drivers never need to worry about
> fixing things up.

MMC isn't particularly unusual.  It's just the first place this
type problem tends to come up.  Expect more such problelms as
folkl actually try to *use* the regulator framework.



--
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/