lkml.org 
[lkml]   [2012]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] regulator: Provide a check for dummy regulator
From
On 20 April 2012 18:31, Mark Brown <broonie@opensource.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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2012-04-20 15:51    [W:0.073 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site