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 12:49:11 +0000
From:   Mark Brown <>
To:     Furquan Shaikh <>
Cc:     "Rafael J . Wysocki" <>,
        Liam Girdwood <>,
        Tony Lindgren <>,
        Dmitry Torokhov <>,
        Len Brown <>,
        Greg Kroah-Hartman <>,
        Lorenzo Pieralisi <>,
        Hanjun Guo <>,
        Will Deacon <>,
        Rob Herring <>,
        Sathyanarayana Nujella <>,
        Heikki Krogerus <>,
        Adam Thomson <>,
        Linus Walleij <>,
        Alexandre Courbot <>,,,,,
Subject: Re: [PATCH 0/7] Implement generic regulator constraints parsing for
 ACPI and OF

On Tue, Jan 24, 2017 at 04:06:34PM -0800, Furquan Shaikh wrote:

> Since regulator properties remain the same across OF and ACPI
> regulators, this series of patches provides common routine for
> obtaining regulation constraints from device tree and ACPI nodes. In

As Lorenzo explained this is really not a good idea, ACPI has a power
management model which is just being ignored here.  If you're producing
systems using ACPI you really need to use ACPI in a joined up fashion
rather than just blindly importing all DT bindings into ACPI.  While
there are many areas where ACPI just doesn't do anything and as a result
it does make sense to reuse existing DT bindings there are also plenty
of areas where work has been done on the ACPI side.  Regulators and
power management are definitely one of those areas.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists