linux-kernel - Re: [PATCH] regulator: Provide a check for 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]

Message-ID: <CAJe_ZhdKtK8YKo1qc8g18XrdnrQRZw2aFSkW8x3koELU10EsHw@mail.gmail.com>
Date:	Fri, 20 Apr 2012 19:18:15 +0530
From:	Jassi Brar <jaswinder.singh@...aro.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, lrg@...com
Subject: Re: [PATCH] regulator: Provide a check for dummy regulator

On 20 April 2012 18:31, Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:
> On Fri, Apr 20, 2012 at 05:59:42PM +0530, Jassi Brar wrote:
>
>> That's what I have been trying to fix. My example might be fictitious but
>> I have a real scenario with omap_hsmmc (I was avoiding getting into that).
>
>> The dummy not just provide a place holder data structure for missing definition
>> of an available supply, but it also masks the fact that there might indeed be no
>> supply at all on the given machine.
>
>> As I said, atm the only option for a consumer is to know it via PD/DT.
>
> No.  You're failing to understand what dummy regulators are for.
>
I think I do understand what dummy regulators are for and also that
they are meant to go away some time in future.

>  To repeat yet again you're not supposed to actually use dummy regulators,
> you're supposed to fully specify the regulators on your platform.
>
I use dummy regulators for what they are meant for - until every platform
completely define supplies for every consumer.
We are not there yet, yet one 'ideal' consumer suffers because of that.

If you ask me to go away and disable dummy and update all consumers
and their platforms, then I say why not remove the concept of dummy
altogether which only delays full compliance to the regulator api ?

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