From: Viresh Kumar <viresh.kumar@linaro.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rui.zhang@intel.com, rjw@rjwysocki.net, edubezval@gmail.com,
linux-pm@vger.kernel.org, amit.kucheria@linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/4] thermal/drivers/Kconfig: Convert the CPU cooling device to a choice
Date: Tue, 3 Dec 2019 12:13:43 +0530 [thread overview]
Message-ID: <20191203064343.4lu3ut6rs6kyq7nh@vireshk-i7> (raw)
In-Reply-To: <20191202202815.22731-1-daniel.lezcano@linaro.org>
On 02-12-19, 21:28, Daniel Lezcano wrote:
> The next changes will add a new way to cool down a CPU by injecting
> idle cycles. With the current configuration, a CPU cooling device is
> the cpufreq cooling device. As we want to add a new CPU cooling
> device, let's convert the CPU cooling to a choice giving a list of CPU
> cooling devices. At this point, there is obviously only one CPU
> cooling device.
>
> There is no functional changes.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
> V2:
> - Default CPU_FREQ_COOLING when CPU_THERMAL is set (Viresh Kumar)
> ---
> drivers/thermal/Kconfig | 14 ++++++++++++--
> drivers/thermal/Makefile | 2 +-
> include/linux/cpu_cooling.h | 6 +++---
> 3 files changed, 16 insertions(+), 6 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
prev parent reply other threads:[~2019-12-03 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 20:28 [PATCH V2 1/4] thermal/drivers/Kconfig: Convert the CPU cooling device to a choice Daniel Lezcano
2019-12-02 20:28 ` [PATCH V2 2/4] thermal/drivers/cpu_cooling: Add idle cooling device documentation Daniel Lezcano
2019-12-03 6:44 ` Viresh Kumar
2019-12-02 20:28 ` [PATCH V2 3/4] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver Daniel Lezcano
2019-12-03 8:14 ` Viresh Kumar
2019-12-03 8:24 ` Viresh Kumar
2019-12-02 20:28 ` [PATCH V2 4/4] thermal/drivers/cpu_cooling: Rename to cpufreq_cooling Daniel Lezcano
2019-12-03 8:20 ` Viresh Kumar
2019-12-03 6:43 ` Viresh Kumar [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=20191203064343.4lu3ut6rs6kyq7nh@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
/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.