linux-kernel - Re: [PATCH V3] regulator: disable supply regulator if it is enabled for boot-on

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

Message-ID: <20120907131918.GC4438@opensource.wolfsonmicro.com>
Date:	Fri, 7 Sep 2012 21:19:20 +0800
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	"lrg@...com" <lrg@...com>,
	"rabin.vincent@...il.com" <rabin.vincent@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V3] regulator: disable supply regulator if it is enabled
 for boot-on

On Fri, Sep 07, 2012 at 06:21:25PM +0530, Laxman Dewangan wrote:
> On Friday 07 September 2012 07:29 AM, Mark Brown wrote:

> >  I think what we need to
> >do here is always take a reference to the supply if the child is enabled
> >during boot, then in the initcall we can just disable the parent
> >regulator as normal.

> My second patch was similar but Rabin has some issue to handle the
> case when is_regulator_enable() is not implementd by regulator
> device driver.

So let's fix that...  if it's causing an issue in this case it's likely
to affect other areas too, coding in custom hacks in different bits of
the code isn't going to help maintainability.  What was the issue?
--
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/