From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
poshao.chen@mediatek.com
Subject: Re: [PATCH] PM: EM: Force device drivers to provide power in uW
Date: Thu, 14 Mar 2024 11:57:48 +0000 [thread overview]
Message-ID: <1135db48-6430-4a36-b75a-2f0ededd4612@arm.com> (raw)
In-Reply-To: <CAJZ5v0g_UcJzRy2-16kjOZpOyB=-FsdgH63LJBzmHRhsARYjVA@mail.gmail.com>
On 3/13/24 19:49, Rafael J. Wysocki wrote:
> On Fri, Mar 8, 2024 at 1:31 PM Lukasz Luba <lukasz.luba@arm.com> wrote:
>>
>> The EM only supports power in uW. Make sure that it is not possible to
>> register some downstream driver which doesn't provide power in uW.
>> The only exception is artificial EM, but that EM is ignored by the rest of
>> kernel frameworks (thermal, powercap, etc).
>>
>> Reported-by: PoShao Chen <poshao.chen@mediatek.com>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>>
>> Hi all,
>>
>> The was an issue reported recently that the EM could be used with
>> not aligned drivers which provide milli-Watts. This patch prevents such
>> drivers to register EM (although there are no such in upstream).
>>
>> Regards,
>> Lukasz
>>
>> kernel/power/energy_model.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/kernel/power/energy_model.c b/kernel/power/energy_model.c
>> index b686ac0345bd9..9e1c9aa399ea9 100644
>> --- a/kernel/power/energy_model.c
>> +++ b/kernel/power/energy_model.c
>> @@ -612,6 +612,17 @@ int em_dev_register_perf_domain(struct device *dev, unsigned int nr_states,
>> else if (cb->get_cost)
>> flags |= EM_PERF_DOMAIN_ARTIFICIAL;
>>
>> + /*
>> + * EM only supports uW (exception is artificial EM).
>> + * Therefore, check and force the drivers to provide
>> + * power in uW.
>> + */
>> + if (!microwatts && !(flags & EM_PERF_DOMAIN_ARTIFICIAL)) {
>> + dev_err(dev, "EM: only supports uW power values\n");
>> + ret = -EINVAL;
>> + goto unlock;
>> + }
>> +
>> ret = em_create_pd(dev, nr_states, cb, cpus, flags);
>> if (ret)
>> goto unlock;
>> --
>
> Applied as 6.9-rc material, thanks!
Thank you Rafael!
prev parent reply other threads:[~2024-03-14 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 12:32 Lukasz Luba
2024-03-13 19:49 ` Rafael J. Wysocki
2024-03-14 11:57 ` Lukasz Luba [this message]
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=1135db48-6430-4a36-b75a-2f0ededd4612@arm.com \
--to=lukasz.luba@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=poshao.chen@mediatek.com \
--cc=rafael@kernel.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®