From: Lukasz Luba <lukasz.luba@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com,
rafael@kernel.org, daniel.lezcano@linaro.org, nm@ti.com,
sboyd@kernel.org, mka@chromium.org, dianders@chromium.org,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 4/4] Documentation: EM: Describe new registration method using DT
Date: Thu, 24 Feb 2022 09:25:17 +0000 [thread overview]
Message-ID: <02d16fbe-d4d6-a7f1-d81f-39f05dff76fc@arm.com> (raw)
In-Reply-To: <20220224091508.fp7emu2zyhavkfkt@vireshk-i7>
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@arm.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.
next prev parent reply other threads:[~2022-02-24 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 8:11 [PATCH v3 0/4] Introduce "opp-microwatt" and 'advanced' Energy Model from DT Lukasz Luba
2022-02-24 8:11 ` [PATCH v3 1/4] dt-bindings: opp: Add "opp-microwatt" entry in the OPP Lukasz Luba
2022-02-24 9:01 ` Viresh Kumar
2022-02-24 9:14 ` Lukasz Luba
2022-02-24 8:11 ` [PATCH v3 2/4] OPP: Add "opp-microwatt" supporting code Lukasz Luba
2022-02-24 9:03 ` Viresh Kumar
2022-02-24 9:34 ` Lukasz Luba
2022-02-24 9:14 ` Viresh Kumar
2022-02-24 9:33 ` Lukasz Luba
2022-02-24 8:11 ` [PATCH v3 3/4] OPP: Add support of "opp-microwatt" for advanced EM registration Lukasz Luba
2022-02-24 9:13 ` Viresh Kumar
2022-02-24 9:33 ` Lukasz Luba
2022-02-24 9:42 ` Viresh Kumar
2022-02-24 9:43 ` Lukasz Luba
2022-02-24 8:11 ` [PATCH v3 4/4] Documentation: EM: Describe new registration method using DT Lukasz Luba
2022-02-24 9:15 ` Viresh Kumar
2022-02-24 9:25 ` Lukasz Luba [this message]
2022-02-24 9:37 ` Viresh Kumar
2022-02-24 9:39 ` Lukasz Luba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02d16fbe-d4d6-a7f1-d81f-39f05dff76fc@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).