linux-kernel - Re: [PATCH] regulator: Add option for machine drivers to enable the dummy regulator

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:	Wed, 6 Oct 2010 06:08:25 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Marek Vasut <marek.vasut@...il.com>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>, linux-kernel@...r.kernel.org,
	Igor Grinberg <grinberg@...pulab.co.il>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linus Walleij <linus.ml.walleij@...il.com>
Subject: Re: [PATCH] regulator: Add option for machine drivers to enable
	the dummy regulator

On Wed, Oct 06, 2010 at 06:09:17AM +0200, Marek Vasut wrote:

> This still solves nothing ... This leaves boards broken and the granularity is 
We've already got a compatibility option which allows this to be enabled
with a config change, and the actual code update required has been
reduced to a single line.  This does not seem terribly onerous.

> too big. Consider there are boards that use regulator for MMC, but not for 
> ADS7846 for example.

You can't have it both ways.  Either drivers just ignore missing
regulators and just run as though everything is fine (which is what
you've been requesting enthusiastically) or they trust that they can get
accurate information about what is and isn't mapped.  All this is doing
is providing a way to enable the former behaviour in the core.
--
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/