From: Lukasz Luba <lukasz.luba@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com,
rafael@kernel.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 v2 0/2] Introduce 'advanced' Energy Model in DT
Date: Wed, 23 Feb 2022 11:22:28 +0000 [thread overview]
Message-ID: <94d3f2a3-4145-afdc-d810-61f2120df579@arm.com> (raw)
In-Reply-To: <20220223104341.jh5hjcv6ugaexgoa@vireshk-i7>
On 2/23/22 10:43, Viresh Kumar wrote:
> On 23-02-22, 10:52, Daniel Lezcano wrote:
>> why not extend the energy model to any kind of devices?
>
> FWIW, the OPP core supports a wide range of devices now, not just CPUs.
>
Is that the "opp-level" thing which would allow that?
I can see some DT files with regulators(?) using it e.g. [1].
It looks flexible, the opp-hz is not hard requirement,
the opp-level can be used instead IIUC.
It might be a next step which might meet Daniel's needs.
If that 'level' can be any number and frequency is not available
then EM must have 'level' filed in the struct em_perf_state
for this kind of new devices. I'm open for such change.
We can discuss this as a next step. We would need to find some examples
how this new thing would be used.
[1]
https://elixir.bootlin.com/linux/v5.17-rc5/source/arch/arm/boot/dts/tegra20-peripherals-opp.dtsi#L4
next prev parent reply other threads:[~2022-02-23 11:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 14:07 [PATCH v2 0/2] Introduce 'advanced' Energy Model in DT Lukasz Luba
2022-02-22 14:07 ` [[PATCH v2 1/2] dt-bindings: opp: Add 'opp-microwatt' entry in the OPP Lukasz Luba
2022-02-23 5:50 ` Viresh Kumar
2022-02-23 8:39 ` Lukasz Luba
2022-02-23 8:45 ` Viresh Kumar
2022-02-22 14:07 ` [[PATCH v2 2/2] OPP: Add 'opp-microwatt' parsing for advanced EM registration Lukasz Luba
2022-02-22 14:58 ` Matthias Kaehlcke
2022-02-22 15:21 ` Lukasz Luba
2022-02-23 5:53 ` Viresh Kumar
2022-02-23 8:59 ` Lukasz Luba
2022-02-23 9:10 ` Viresh Kumar
2022-02-23 9:13 ` Lukasz Luba
2022-02-23 9:52 ` [PATCH v2 0/2] Introduce 'advanced' Energy Model in DT Daniel Lezcano
2022-02-23 10:16 ` Lukasz Luba
2022-02-23 10:43 ` Viresh Kumar
2022-02-23 11:22 ` Lukasz Luba [this message]
2022-02-23 11:27 ` Viresh Kumar
2022-02-23 11:40 ` 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=94d3f2a3-4145-afdc-d810-61f2120df579@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