From: Matthias Kaehlcke <mka@chromium.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
viresh.kumar@linaro.org, edubezval@gmail.com,
swboyd@chromium.org, dianders@chromium.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 04/10] cpufreq: qcom-hw: Register as a cpufreq cooling device
Date: Mon, 14 Jan 2019 12:54:35 -0800 [thread overview]
Message-ID: <20190114205435.GM261387@google.com> (raw)
In-Reply-To: <bd172905b0208b958f8c4f239b55ac3e345c60a8.1547481320.git.amit.kucheria@linaro.org>
On Mon, Jan 14, 2019 at 10:04:56PM +0530, Amit Kucheria wrote:
> Add the CPUFREQ_AUTO_REGISTER_COOLING_DEV flag to allow the cpufreq core
> to auto-register the driver as a cooling device.
>
> Signed-off-by: Amit Kucheria <amit.kucheria@linaro.org>
> ---
> drivers/cpufreq/qcom-cpufreq-hw.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
> index d83939a1b3d4..ed32849a3d40 100644
> --- a/drivers/cpufreq/qcom-cpufreq-hw.c
> +++ b/drivers/cpufreq/qcom-cpufreq-hw.c
> @@ -231,7 +231,8 @@ static struct freq_attr *qcom_cpufreq_hw_attr[] = {
>
> static struct cpufreq_driver cpufreq_qcom_hw_driver = {
> .flags = CPUFREQ_STICKY | CPUFREQ_NEED_INITIAL_FREQ_CHECK |
> - CPUFREQ_HAVE_GOVERNOR_PER_POLICY,
> + CPUFREQ_HAVE_GOVERNOR_PER_POLICY |
> + CPUFREQ_AUTO_REGISTER_COOLING_DEV,
> .verify = cpufreq_generic_frequency_table_verify,
> .target_index = qcom_cpufreq_hw_target_index,
> .get = qcom_cpufreq_hw_get,
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Tested-by: Matthias Kaehlcke <mka@chromium.org>
next prev parent reply other threads:[~2019-01-14 20:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 16:34 [PATCH v1 00/10] cpufreq: Add flag to auto-register as cooling device Amit Kucheria
2019-01-14 16:34 ` Amit Kucheria
2019-01-14 16:34 ` Amit Kucheria
2019-01-14 16:34 ` [PATCH v1 01/10] cpufreq: Add thermal_cooling_device pointer to struct cpufreq_policy Amit Kucheria
2019-01-16 22:56 ` Rafael J. Wysocki
2019-01-21 15:35 ` Amit Kucheria
2019-01-14 16:34 ` [PATCH v1 02/10] cpufreq: Add a flag to auto-register a cooling device Amit Kucheria
2019-01-14 20:51 ` Matthias Kaehlcke
2019-01-16 23:03 ` Rafael J. Wysocki
2019-01-17 4:42 ` Viresh Kumar
2019-01-21 14:23 ` Amit Kucheria
2019-01-14 16:34 ` [PATCH v1 03/10] cpufreq: Replace open-coded << with BIT() Amit Kucheria
2019-01-15 19:05 ` Stephen Boyd
2019-01-16 22:55 ` Rafael J. Wysocki
2019-01-21 8:48 ` Amit Kucheria
2019-01-14 16:34 ` [PATCH v1 04/10] cpufreq: qcom-hw: Register as a cpufreq cooling device Amit Kucheria
2019-01-14 20:54 ` Matthias Kaehlcke [this message]
2019-01-14 16:34 ` [PATCH v1 05/10] cpufreq: imx6q: Use auto-registration of thermal " Amit Kucheria
2019-01-17 4:49 ` Viresh Kumar
2019-01-14 16:34 ` [PATCH v1 06/10] cpufreq: cpufreq-dt: " Amit Kucheria
2019-01-14 16:34 ` [PATCH v1 07/10] cpufreq: mediatek: " Amit Kucheria
2019-01-14 16:34 ` Amit Kucheria
2019-01-14 16:35 ` [PATCH v1 08/10] cpufreq: qoriq: " Amit Kucheria
2019-01-14 16:35 ` [PATCH v1 09/10] cpufreq: scmi: " Amit Kucheria
2019-01-14 16:35 ` Amit Kucheria
2019-01-15 10:37 ` Sudeep Holla
2019-01-15 10:37 ` Sudeep Holla
2019-01-14 16:35 ` [PATCH v1 10/10] cpufreq: scpi: " Amit Kucheria
2019-01-14 16:35 ` Amit Kucheria
2019-01-17 5:49 ` [PATCH v1 00/10] cpufreq: Add flag to auto-register as " Viresh Kumar
2019-01-17 5:49 ` Viresh Kumar
2019-01-17 5:49 ` Viresh Kumar
2019-01-17 10:08 ` Rafael J. Wysocki
2019-01-17 10:08 ` Rafael J. Wysocki
2019-01-17 10:08 ` Rafael J. Wysocki
2019-01-17 10:14 ` Rafael J. Wysocki
2019-01-17 10:14 ` Rafael J. Wysocki
2019-01-17 10:14 ` Rafael J. Wysocki
2019-01-17 10:28 ` Viresh Kumar
2019-01-17 10:28 ` Viresh Kumar
2019-01-17 10:28 ` Viresh Kumar
2019-01-17 10:31 ` Rafael J. Wysocki
2019-01-17 10:31 ` Rafael J. Wysocki
2019-01-17 10:31 ` Rafael J. Wysocki
2019-01-17 10:21 ` Viresh Kumar
2019-01-17 10:21 ` Viresh Kumar
2019-01-17 10:21 ` Viresh Kumar
2019-01-17 10:29 ` Rafael J. Wysocki
2019-01-17 10:29 ` Rafael J. Wysocki
2019-01-17 10:29 ` Rafael J. Wysocki
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=20190114205435.GM261387@google.com \
--to=mka@chromium.org \
--cc=amit.kucheria@linaro.org \
--cc=dianders@chromium.org \
--cc=edubezval@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.