linux-kernel - Re: [PATCH 2/2] regulator: core: Add reg_ignore_unused to keep boot time regulators enabled

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: <CAHbNUh0dwBWfT=AAYP_W2yx2xkbnjbhOBF_PSKrLdv1VaUv9Sw@mail.gmail.com>
Date:	Tue, 1 Apr 2014 18:59:04 +0530
From:	Tushar Behera <tushar.behera@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	linux-doc@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Rob Landley <rob@...dley.net>, Olof Johansson <olof@...om.net>
Subject: Re: [PATCH 2/2] regulator: core: Add reg_ignore_unused to keep boot
 time regulators enabled

On 28 March 2014 15:52, Mark Brown <broonie@...nel.org> wrote:
> On Fri, Mar 28, 2014 at 10:50:22AM +0530, Tushar Behera wrote:
>> Keep all regulators already enabled by bootloader on, even if no
>> driver has claimed them. This is useful for debug and development, but
>> should not be needed on a platform with proper driver support.
>
> That's already the default on non-DT systems so I'd expect that if we
> were doing this the code would be joined up with the code for that.  I'm
> not sure this is a terribly good idea though - we already display a
> message just before we power off the regulator and having an option like
> this feels like it's going to encourage people to write bad DTs and tell
> people to add this to their command line.

I agree with your point that it may lead developers to write bad DTs,
but it becomes quite helpful while debugging issues.

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