From: Lukasz Luba <lukasz.luba@arm.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, daniel.lezcano@linaro.org,
qperret@google.com
Cc: robh+dt@kernel.org, amitk@kernel.org, corbet@lwn.net,
Dietmar.Eggemann@arm.com, morten.rasmussen@arm.com,
dianders@chromium.org, mka@chromium.org, rnayak@codeaurora.org,
rafael@kernel.org, sudeep.holla@arm.com, viresh.kumar@linaro.org,
sboyd@kernel.org, nm@ti.com
Subject: Re: [PATCH v3 0/4] Clarify abstract scale usage for power values in Energy Model, EAS and IPA
Date: Mon, 2 Nov 2020 08:54:38 +0000 [thread overview]
Message-ID: <d3c64655-dc31-73dc-8483-bf5805a9d389@arm.com> (raw)
In-Reply-To: <20201019140601.3047-1-lukasz.luba@arm.com>
On 10/19/20 3:05 PM, Lukasz Luba wrote:
> Hi all,
>
> The Energy Model supports power values expressed in an abstract scale.
> This has an impact on Intelligent Power Allocation (IPA) and should be
> documented properly. Kernel sub-systems like EAS, IPA and DTPM
> (new comming PowerCap framework) would use the new flag to capture
> potential miss-configuration where the devices have registered different
> power scales, thus cannot operate together.
>
> There was a discussion below v2 of this patch series, which might help
> you to get context of these changes [2].
>
> The agreed approach is to have the DT as a source of power values expressed
> always in milli-Watts and the only way to submit with abstract scale values
> is via the em_dev_register_perf_domain() API.
>
> Changes:
> v3:
> - added boolean flag to struct em_perf_domain and registration function
> indicating if EM holds real power values in milli-Watts (suggested by
> Daniel and aggreed with Quentin)
> - updated documentation regarding this new flag
> - dropped DT binding change for 'sustainable-power'
> - added more maintainers on CC (due to patch 1/4 touching different things)
> v2 [2]:
> - updated sustainable power section in IPA documentation
> - updated DT binding for the 'sustainable-power'
> v1 [1]:
> - simple documenation update with new 'abstract scale' in EAS, EM, IPA
>
> Regards,
> Lukasz Luba
>
> [1] https://lore.kernel.org/linux-doc/20200929121610.16060-1-lukasz.luba@arm.com/
> [2] https://lore.kernel.org/lkml/20201002114426.31277-1-lukasz.luba@arm.com/
>
> Lukasz Luba (4):
> PM / EM: Add a flag indicating units of power values in Energy Model
> docs: Clarify abstract scale usage for power values in Energy Model
> PM / EM: update the comments related to power scale
> docs: power: Update Energy Model with new flag indicating power scale
>
> .../driver-api/thermal/power_allocator.rst | 13 +++++++-
> Documentation/power/energy-model.rst | 30 +++++++++++++++----
> Documentation/scheduler/sched-energy.rst | 5 ++++
> drivers/cpufreq/scmi-cpufreq.c | 3 +-
> drivers/opp/of.c | 2 +-
> include/linux/energy_model.h | 20 ++++++++-----
> kernel/power/energy_model.c | 26 ++++++++++++++--
> 7 files changed, 81 insertions(+), 18 deletions(-)
>
Gentle ping to Quentin and Daniel for sharing opinion on this patch set.
If you are OK, then I could use this as a base for next work.
As you probably know I am working also on 'sustainable power' estimation
which could be used when there is no DT value but it comes from FW.
That would meet requirement from Doug, when the DT cannot be used,
but we have sustainable levels from FW [1].
Regards,
Lukasz
[1] https://lore.kernel.org/lkml/20201028140847.1018-5-lukasz.luba@arm.com/
next prev parent reply other threads:[~2020-11-02 8:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 14:05 Lukasz Luba
2020-10-19 14:05 ` [PATCH v3 1/4] PM / EM: Add a flag indicating units of power values in Energy Model Lukasz Luba
2020-10-20 0:17 ` Doug Anderson
2020-10-29 12:08 ` Lukasz Luba
2020-11-02 13:43 ` Quentin Perret
2020-11-03 8:26 ` Lukasz Luba
2020-10-19 14:05 ` [PATCH v3 2/4] docs: Clarify abstract scale usage for " Lukasz Luba
2020-11-02 13:45 ` Quentin Perret
2020-11-03 8:28 ` Lukasz Luba
2020-10-19 14:06 ` [PATCH v3 3/4] PM / EM: update the comments related to power scale Lukasz Luba
2020-11-02 13:48 ` Quentin Perret
2020-10-19 14:06 ` [PATCH v3 4/4] docs: power: Update Energy Model with new flag indicating " Lukasz Luba
2020-11-02 13:51 ` Quentin Perret
2020-10-20 0:15 ` [PATCH v3 0/4] Clarify abstract scale usage for power values in Energy Model, EAS and IPA Doug Anderson
2020-10-29 12:37 ` Lukasz Luba
2020-10-29 15:39 ` Doug Anderson
2020-10-29 16:15 ` Lukasz Luba
2020-11-02 8:54 ` Lukasz Luba [this message]
2020-11-02 13:54 ` Quentin Perret
2020-11-03 0:41 ` Doug Anderson
2020-11-03 8:29 ` 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=d3c64655-dc31-73dc-8483-bf5805a9d389@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=amitk@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=morten.rasmussen@arm.com \
--cc=nm@ti.com \
--cc=qperret@google.com \
--cc=rafael@kernel.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--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
all inboxes | Powered by JetHome®