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 3/4] OPP: Add support of "opp-microwatt" for advanced EM registration
Date: Thu, 24 Feb 2022 09:33:18 +0000 [thread overview]
Message-ID: <9c8f15a3-563f-3bed-61a4-2f72b0c20e89@arm.com> (raw)
In-Reply-To: <20220224091346.xmnpj27vllpa4cuy@vireshk-i7>
On 2/24/22 09:13, Viresh Kumar wrote:
> On 24-02-22, 08:11, Lukasz Luba wrote:
>> diff --git a/drivers/opp/of.c b/drivers/opp/of.c
>>
>> +/*
>> + * Callback function provided to the Energy Model framework upon registration.
>> + * It provides the power used by @dev at @kHz if it is the frequency of an
>> + * existing OPP, or at the frequency of the first OPP above @kHz otherwise
>> + * (see dev_pm_opp_find_freq_ceil()). This function updates @kHz to the ceiled
>> + * frequency and @mW to the associated power.
>> + *
>> + * Returns 0 on success or a proper -EINVAL value in case of error.
>> + */
>> +static int __maybe_unused
>> +_get_opp_power(unsigned long *mW, unsigned long *kHz, struct device *dev)
>
> Lets call it _get_dt_opp_power() or _get_dt_power() ?
OK, I'll return to _get_dt_power()
>
>> +{
>> + struct dev_pm_opp *opp;
>> + unsigned long opp_freq, opp_power;
>> +
>> + /* Find the right frequency and related OPP */
>> + opp_freq = *kHz * 1000;
>> + opp = dev_pm_opp_find_freq_ceil(dev, &opp_freq);
>> + if (IS_ERR(opp))
>> + return -EINVAL;
>> +
>> + opp_power = dev_pm_opp_get_power(opp);
>
> As I said in 2/4, this should really give the total instead.
make sense
>
>> + dev_pm_opp_put(opp);
>> + if (!opp_power)
>> + return -EINVAL;
>> +
>> + *kHz = opp_freq / 1000;
>> + *mW = opp_power / 1000;
>> +
>> + return 0;
>> +}
>> +
>> /*
>> * Callback function provided to the Energy Model framework upon registration.
>> * This computes the power estimated by @dev at @kHz if it is the frequency
>> @@ -1488,6 +1520,24 @@ static int __maybe_unused _get_power(unsigned long *mW, unsigned long *kHz,
>> return 0;
>> }
>>
>> +static bool _of_has_opp_microwatt_property(struct device *dev)
>> +{
>> + unsigned long power, freq = 0;
>> + struct dev_pm_opp *opp;
>> +
>> + /* Check if at least one OPP has needed property */
>> + opp = dev_pm_opp_find_freq_ceil(dev, &freq);
>> + if (IS_ERR(opp))
>> + return false;
>> +
>> + power = dev_pm_opp_get_power(opp);
>> + dev_pm_opp_put(opp);
>> + if (!power)
>
> What if this particular frequency has 0 power mentioned for some
> reason :)
If that power 0 would be allowed here, then in next step when EM
calls active_power() we check !power and report dev_err().
IPA design would also not accept the power=0
>
> Instead of this heavy stuff, just pick the first OPP from the opp
> table and see its power-value.
It is the first opp: freq=0.
You mean by parsing the the DT node instead, like I had in v2 version?
>
>> + return false;
>> +
>> + return true;
>> +}
>> +
>> /**
>> * dev_pm_opp_of_register_em() - Attempt to register an Energy Model
>> * @dev : Device for which an Energy Model has to be registered
>> @@ -1517,6 +1567,14 @@ int dev_pm_opp_of_register_em(struct device *dev, struct cpumask *cpus)
>> goto failed;
>> }
>>
>> + /* First, try to find more precised Energy Model in DT */
>> + if (_of_has_opp_microwatt_property(dev)) {
>> + struct em_data_callback em_dt_cb = EM_DATA_CB(_get_opp_power);
>> +
>> + return em_dev_register_perf_domain(dev, nr_opp, &em_dt_cb,
>> + cpus, true);
>> + }
>> +
>
> We have another em_dev_register_perf_domain() down the line, lets keep
> only one such call and get it a callback that should be set in an
> if/else loop.
OK
next prev parent reply other threads:[~2022-02-24 9:33 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 [this message]
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
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=9c8f15a3-563f-3bed-61a4-2f72b0c20e89@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).