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 15:27:55 -0800
From:   Dmitry Torokhov <>
To:     Al Stone <>
Cc:     Mark Brown <>,
        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 02:44:10PM -0700, Al Stone wrote:
> But, to the point of some of the other discussion on the thread, this ACPI sort
> of power management is a very, very different model than DT so that intertwining
> the two models is highly unlikely to work, IMHO.

And yet this is something that is sorely needed. If you look, for
example, at drivers in drivers/input/*, then all non-SOC-specific
devices can easily find their way onto both ACPI-based and DT-based
systems (not mentioning legacy-style boards). Having two distinct power
schemes implemented in drivers will lead to many problems.

Having unified way of describing hardware is how _DSD came about, right?
Nobody wanted to write and maintain and test two separate ways of
describing properties when one was already implemented and working.



Powered by blists - more mailing lists