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  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, 25 Jan 2017 10:44:32 -0800
From:   Dmitry Torokhov <>
To:     Mark Brown <>
Cc:     Mark Rutland <>,
        Furquan Shaikh <>,
        "Rafael J. Wysocki" <>,
        "Rafael J . Wysocki" <>,
        Liam Girdwood <>,
        Tony Lindgren <>, Len Brown <>,
        Greg Kroah-Hartman <>,
        Lorenzo Pieralisi <>,
        Hanjun Guo <>,
        Will Deacon <>,
        Rob Herring <>,
        Sathyanarayana Nujella <>,
        Heikki Krogerus <>,
        Adam Thomson <>,
        Linus Walleij <>,
        Alexandre Courbot <>,,
        ACPI Devel Maling List <>,
        Linux Kernel Mailing List <>,
        Linux OMAP Mailing List <>,
        Aaron Durbin <>,
Subject: Re: [PATCH 0/7] Implement generic regulator constraints parsing for
 ACPI and OF

On Wed, Jan 25, 2017 at 06:29:55PM +0000, Mark Brown wrote:
> On Wed, Jan 25, 2017 at 06:23:20PM +0000, Mark Rutland wrote:
> > On Wed, Jan 25, 2017 at 08:56:42AM -0800, Furquan Shaikh wrote:
> > > That is the reason why the recent change to add ACPI support to fixed
> > > regulators was done
> > > (
> > To be honest, I'm surprised this got merged.
> My understanding was that it was instantiated from another device as an
> implementation detail of that device, letting it say "this GPIO should
> be handled as a regulator".
> > Mark, this was added in this cycle; can we please rip that out for now?
> If it's instantiated directly we probably should.
> > We can certainly come up with something that allows drivers to support
> > both, but trying to do this without updating drivers opens a huge set of
> > problems.
> I think there's a reasonable chance that any ACPI specs could be written
> in such a way as to allow transparent support in Linux, the main thing
> I'd worry about is naming issues.

So if I am reading this correctly, currently ACPI does not expose power
supplies directly, but rather ties them to the device power state (D0,
D3cold, etc). Linux drivers do not usually follow that state model and
expect to have all their power supplies be given to them and then
figures out what to do with them itself. Given that, what do we do? Do
we map only entries from _PR3 so they are available to drivers via
regulator_get()? Or we ask the standard to add method enumerating all



Powered by blists - more mailing lists