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: <8f448883-f8cf-76fc-6275-ed5d887f16c8@linaro.org>
Date:   Sun, 30 Jan 2022 20:10:55 +0100
From:   Daniel Lezcano <daniel.lezcano@...aro.org>
To:     rjw@...ysocki.net
Cc:     heiko@...ech.de, robh@...nel.org, lukasz.luba@....com,
        arnd@...aro.org, linux-kernel@...r.kernel.org,
        linux-pm@...r.kernel.org
Subject: Re: [PATCH v8 0/6] powercap/drivers/dtpm: Create the dtpm hierarchy

On 28/01/2022 17:35, Daniel Lezcano wrote:
> The DTPM hierarchy is the base to build on top of it a power budget allocator.
> It reflects the power consumption of the group of devices and allows to cap
> their power.
> 
> The core code is there but there is no way to describe the desired hierarchy
> yet.
> 
> A first proposal introduced the description through configfs [1] but was
> rejected [2].
> 
> A second proposal based on the device tree with a binding similar to the power
> domains [3] was proposed but finally rejected [4].
> 
> This version delegates the hierarchy creation to the SoC with a specific and
> self-encapsulated code using an array to describe the tree. The SoC DTPM driver
> defines an array of nodes pointing to their parents.  The hierarchy description
> can integrate a DT node and in the future a SCMI node, that means the
> description can mix different type of nodes.
> 
> As the DTPM tree depends on different devices which could be modules, the SoC
> specific description must always be compiled as a module and describe the
> module softdeps in order to let the userspace to handle proper loading
> ordering.
> 
> In addition to the hierarchy creation, the devfreq dtpm support is also
> integrated into this series.
> 
> This series was tested on a rock960 (revision B - rk3399 based) and a db845c
> (Qualcomm sdm845 based).
> 
> [1] https://lore.kernel.org/all/20210401183654.27214-1-daniel.lezcano@linaro.org/
> [2] https://lore.kernel.org/all/YGYg6ZeZ1181%2FpXk@kroah.com/
> [3] https://lore.kernel.org/all/20211205231558.779698-1-daniel.lezcano@linaro.org/
> [4] https://lore.kernel.org/all/YbfFapsmsjs4qnsg@robh.at.kernel.org/
> 

Applied for v5.18



-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ