From: Viresh Kumar <viresh.kumar@linaro.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
vireshk@kernel.org, rafael@kernel.org, daniel.lezcano@linaro.org,
Dietmar.Eggemann@arm.com, amitk@kernel.org, rui.zhang@intel.com,
cw00.choi@samsung.com, myungjoo.ham@samsung.com,
kyungmin.park@samsung.com
Subject: Re: [RFC][PATCH 0/3] New thermal interface allowing IPA to get max power
Date: Wed, 27 Jan 2021 14:45:40 +0530 [thread overview]
Message-ID: <20210127091540.xesvwoeavyaf37jn@vireshk-i7> (raw)
In-Reply-To: <20210126104001.20361-1-lukasz.luba@arm.com>
On 26-01-21, 10:39, Lukasz Luba wrote:
> As it's a RFC, it still misses the cpufreq sysfs implementation, but would
> be addressed if all agree.
Not commenting on the whole stuff but if you ever need something for cpufreq, it
is already there. Look for these.
store_one(scaling_min_freq, min);
store_one(scaling_max_freq, max);
Hopefully they will work just fine.
--
viresh
next prev parent reply other threads:[~2021-01-27 9:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 10:39 [RFC][PATCH 0/3] New thermal interface allowing IPA to get max power Lukasz Luba
2021-01-26 10:39 ` [RFC][PATCH 1/3] PM /devfreq: add user frequency limits into devfreq struct Lukasz Luba
2021-02-03 10:11 ` Chanwoo Choi
2021-02-03 10:21 ` Lukasz Luba
2021-02-11 11:07 ` Lukasz Luba
2021-02-11 22:27 ` Lukasz Luba
2021-02-15 15:00 ` Chanwoo Choi
2021-02-16 10:41 ` Lukasz Luba
2021-02-24 8:04 ` Chanwoo Choi
2021-01-26 10:40 ` [RFC][PATCH 2/3] thermal: devfreq_cooling: add new callback to get user limit for min state Lukasz Luba
2021-01-26 10:40 ` [RFC][PATCH 3/3] thermal: power_allocator: get proper max power limited by user Lukasz Luba
2021-01-27 9:15 ` Viresh Kumar [this message]
2021-01-27 10:11 ` [RFC][PATCH 0/3] New thermal interface allowing IPA to get max power Lukasz Luba
2021-01-27 10:13 ` Viresh Kumar
2021-02-01 11:23 ` Lukasz Luba
2021-02-01 14:21 ` Daniel Lezcano
2021-02-01 16:37 ` Lukasz Luba
2021-02-02 9:31 ` Chanwoo Choi
2021-02-02 9:56 ` Lukasz Luba
2021-02-01 14:19 ` Rafael J. Wysocki
2021-02-01 16:37 ` Lukasz Luba
2021-02-22 10:22 ` Daniel Lezcano
2021-02-22 12:10 ` 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=20210127091540.xesvwoeavyaf37jn@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=Dietmar.Eggemann@arm.com \
--cc=amitk@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=vireshk@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;
as well as URLs for NNTP newsgroup(s).