From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/5] ARM: Exynos: switch to using generic cpufreq driver for Exynos4x12
Date: Mon, 3 Aug 2015 16:10:44 +0530 [thread overview]
Message-ID: <20150803104044.GB21529@linux> (raw)
In-Reply-To: <4532306.AVvo5hem3c@amdc1976>
On 03-08-15, 12:36, Bartlomiej Zolnierkiewicz wrote:
> I would really like it to be dependency not an option (+ I think
> that ideally it should be checked at runtime, IOW we should be
> checking from cpufreq-dt driver if the thermal support is enabled
> before enabling boost support).
I don't think boost has any dependency on thermal support. Yeah, it
may be true for your platform but we can't force it. People might have
different algorithms to control boost modes, thermal is just one
option they may look at. For few, enabling boost may not be a thermal
issue, but power. So, they want to allow it only when they want, but
that wouldn't burn their chip.
So, a platform can choose how it wants to have it. :)
--
viresh
next prev parent reply other threads:[~2015-08-03 10:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 18:49 [PATCH v3 0/5] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Bartlomiej Zolnierkiewicz
2015-07-31 18:49 ` [PATCH v3 1/5] clk: samsung: exynos4x12: add cpu clock configuration data and instantiate cpu clock Bartlomiej Zolnierkiewicz
2015-07-31 18:49 ` [PATCH v3 2/5] ARM: dts: Exynos4x12: add CPU OPP and regulator supply property Bartlomiej Zolnierkiewicz
2015-08-01 10:48 ` Viresh Kumar
2015-07-31 18:49 ` [PATCH v3 3/5] ARM: Exynos: switch to using generic cpufreq driver for Exynos4x12 Bartlomiej Zolnierkiewicz
2015-08-01 7:43 ` Krzysztof Kozlowski
2015-08-03 10:31 ` Bartlomiej Zolnierkiewicz
2015-08-01 11:17 ` Viresh Kumar
2015-08-03 10:17 ` Bartlomiej Zolnierkiewicz
2015-08-03 10:29 ` Viresh Kumar
2015-08-03 10:36 ` Bartlomiej Zolnierkiewicz
2015-08-03 10:40 ` Viresh Kumar [this message]
2015-08-03 10:47 ` Bartlomiej Zolnierkiewicz
2015-08-03 11:15 ` Krzysztof Kozlowski
2015-08-03 13:55 ` Bartlomiej Zolnierkiewicz
2015-08-03 15:50 ` Viresh Kumar
2015-08-03 15:57 ` Bartlomiej Zolnierkiewicz
2015-08-04 0:43 ` Krzysztof Kozlowski
2015-07-31 18:49 ` [PATCH v3 4/5] cpufreq: exynos: remove Exynos4x12 specific cpufreq driver support Bartlomiej Zolnierkiewicz
2015-08-01 10:50 ` Viresh Kumar
2015-07-31 18:49 ` [PATCH v3 5/5] cpufreq: remove no longer needed CPU_FREQ_BOOST_SW config option Bartlomiej Zolnierkiewicz
2015-08-01 11:15 ` Viresh Kumar
2015-08-03 17:12 ` Pandruvada, Srinivas
2015-08-04 1:09 ` Rafael J. Wysocki
2015-08-03 20:55 ` [PATCH v3 0/5] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Tobias Jakobi
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=20150803104044.GB21529@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).