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]
Date:   Thu, 24 Feb 2022 09:25:17 +0000
From:   Lukasz Luba <lukasz.luba@....com>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     linux-kernel@...r.kernel.org, dietmar.eggemann@....com,
        rafael@...nel.org, daniel.lezcano@...aro.org, nm@...com,
        sboyd@...nel.org, mka@...omium.org, dianders@...omium.org,
        robh+dt@...nel.org, devicetree@...r.kernel.org,
        linux-pm@...r.kernel.org
Subject: Re: [PATCH v3 4/4] Documentation: EM: Describe new registration
 method using DT



On 2/24/22 09:15, Viresh Kumar wrote:
> On 24-02-22, 08:11, Lukasz Luba wrote:
>> The new registration method allows to get power values from the DT OPP
>> definition. The new OPP entry property "opp-microwatt" contains total
>> power expressed in micro-Watts. Align the EM documentation with this
>> new possible registration method of 'advanced' EM.
>>
>> Signed-off-by: Lukasz Luba <lukasz.luba@....com>
>> ---
>>   Documentation/power/energy-model.rst | 10 ++++++++++
>>   1 file changed, 10 insertions(+)
>>
>> diff --git a/Documentation/power/energy-model.rst b/Documentation/power/energy-model.rst
>> index 5ac62a7b4b7c..719253fd5215 100644
>> --- a/Documentation/power/energy-model.rst
>> +++ b/Documentation/power/energy-model.rst
>> @@ -113,6 +113,16 @@ to: return warning/error, stop working or panic.
>>   See Section 3. for an example of driver implementing this
>>   callback, or Section 2.4 for further documentation on this API
>>   
>> +Registration of 'advanced' EM using DT
> 
> I am not really sure if this should be called *Advanced*. Just call it
> registration of EM using DT.

Our partners had a lot of issues with EM+EAS, because they were not
aware of the internals of EM and limitations.

We've started to name two types of EM: 'advanced' and 'simple'.
The 'simple' is the one which causes issues. Now when we contact with
partners we ask if they use 'simple' EM and see some issues in EAS.
This is a needed clarification and naming convention that we use.

Here the paragraph name is stressing the fact explicitly that
from today we have the option to provide real power measurements using
DT and it will be the 'advanced' EM.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ