public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:43:52 +0000	[thread overview]
Message-ID: <eb49beb7-584d-152d-0c61-bad66056505c@arm.com> (raw)
In-Reply-To: <20220224094216.mtxjjx65bbjzalqx@vireshk-i7>



On 2/24/22 09:42, Viresh Kumar wrote:
> On 24-02-22, 09:33, Lukasz Luba wrote:
>> 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
> 
>>>> +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)
>>>
>>> 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?
> 
> No, I was thinking if you can simply do:
> 
> opp = list_first_entry(&opp_table->opp_list, struct dev_pm_opp, node);
> 
> But that requires locking, etc as well. So maybe this is fine.
>   

OK, so I'll leave it as is now.

Thank you for the comments. I'll work on v4

  reply	other threads:[~2022-02-24  9:43 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 [this message]
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=eb49beb7-584d-152d-0c61-bad66056505c@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