From: Lukasz Luba <lukasz.luba@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
Dietmar.Eggemann@arm.com, cristian.marussi@arm.com,
morten.rasmussen@arm.com, viresh.kumar@linaro.org,
rafael@kernel.org
Subject: Re: [PATCH 1/2] firmware: arm_scmi: Add power_scale_mw_get() interface
Date: Wed, 25 Nov 2020 09:18:11 +0000 [thread overview]
Message-ID: <2a8a4fd0-dfb7-69a2-5bae-7b5c0d2a1e3e@arm.com> (raw)
In-Reply-To: <20201124165624.glxnmlxavq4bhppm@bogus>
On 11/24/20 4:56 PM, Sudeep Holla wrote:
> On Tue, Nov 24, 2020 at 10:43:45AM +0000, Lukasz Luba wrote:
>> Add a new interface to the existing perf_ops and export the information
>> about the power values scale.
>>
>> This would be used by the cpufreq driver and Energy Model framework to
>> set the performance domains scale: milli-Watts or abstract scale.
>>
>
> Looks good to me. I saw this after I sent pull request this afternoon.
> In case you want to take it via PM tree:
>
> Acked-by: Sudeep Holla <sudeep.holla@arm.com>
>
Thank you Sudeep!
Regards,
Lukasz
next prev parent reply other threads:[~2020-11-25 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 10:43 [PATCH 0/2] SCMI performance protocol power scale interface Lukasz Luba
2020-11-24 10:43 ` [PATCH 1/2] firmware: arm_scmi: Add power_scale_mw_get() interface Lukasz Luba
2020-11-24 16:56 ` Sudeep Holla
2020-11-25 9:18 ` Lukasz Luba [this message]
2020-11-24 10:43 ` [PATCH 2/2] cpufreq: arm_scmi: Discover the power scale in performance protocol Lukasz Luba
2020-11-25 9:29 ` [PATCH 0/2] SCMI performance protocol power scale interface Lukasz Luba
2020-12-07 7:13 ` Viresh Kumar
2020-12-08 4:48 ` Viresh Kumar
2020-12-08 8:36 ` 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=2a8a4fd0-dfb7-69a2-5bae-7b5c0d2a1e3e@arm.com \
--to=lukasz.luba@arm.com \
--cc=Dietmar.Eggemann@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=rafael@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®