From: Viresh Kumar <viresh.kumar@linaro.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Kukjin Kim <kgene@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
'Thomas Abraham' <thomas.ab@samsung.com>,
'Sylwester Nawrocki' <s.nawrocki@samsung.com>,
'Michael Turquette' <mturquette@baylibre.com>,
'Tomasz Figa' <tomasz.figa@gmail.com>,
'Lukasz Majewski' <l.majewski@samsung.com>,
'Heiko Stuebner' <heiko@sntech.de>,
'Chanwoo Choi' <cw00.choi@samsung.com>,
'Kevin Hilman' <khilman@linaro.org>,
'Javier Martinez Canillas' <javier@dowhile0.org>,
'Tobias Jakobi' <tjakobi@math.uni-bielefeld.de>,
'Anand Moon' <linux.amoon@gmail.com>,
linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform
Date: Fri, 7 Aug 2015 17:09:50 +0530 [thread overview]
Message-ID: <20150807113950.GG6939@linux> (raw)
In-Reply-To: <2061119.GBaoSb4YSL@amdc1976>
On 07-08-15, 13:31, Bartlomiej Zolnierkiewicz wrote:
> Users don't need to enable the config option to get boost
> functionality working. It is only needed to get scaling_boost_freqs
> sysfs attribute visible (which lists available boost freqs) when
> using cpufreq-dt driver. Also the config option in question is not
> user visible.
By users I meant the people who will prepare the build images for the
release. They can just enable the config option :)
> The worst thing that happens if these 2 PM patches don't make it
> in time is that there will be no scaling_boost_freqs available
> when using cpufreq-dt driver. Which is not very important from
> Exynos4x12 POV as it only supports single boost freq currently.
Right. So, now that your patch is Acked, send 1/6 and 6/6 separately
to pm-list and Rafael can get them merged himself..
I hope, your 6/6 patch will change a bit now ?
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform
Date: Fri, 7 Aug 2015 17:09:50 +0530 [thread overview]
Message-ID: <20150807113950.GG6939@linux> (raw)
In-Reply-To: <2061119.GBaoSb4YSL@amdc1976>
On 07-08-15, 13:31, Bartlomiej Zolnierkiewicz wrote:
> Users don't need to enable the config option to get boost
> functionality working. It is only needed to get scaling_boost_freqs
> sysfs attribute visible (which lists available boost freqs) when
> using cpufreq-dt driver. Also the config option in question is not
> user visible.
By users I meant the people who will prepare the build images for the
release. They can just enable the config option :)
> The worst thing that happens if these 2 PM patches don't make it
> in time is that there will be no scaling_boost_freqs available
> when using cpufreq-dt driver. Which is not very important from
> Exynos4x12 POV as it only supports single boost freq currently.
Right. So, now that your patch is Acked, send 1/6 and 6/6 separately
to pm-list and Rafael can get them merged himself..
I hope, your 6/6 patch will change a bit now ?
--
viresh
next prev parent reply other threads:[~2015-08-07 11:39 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 13:41 [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` [PATCH v4 1/6] cpufreq: make scaling_boost_freqs sysfs attr available when boost is enabled Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-07 3:41 ` Viresh Kumar
2015-08-07 3:41 ` Viresh Kumar
2015-08-07 10:34 ` Bartlomiej Zolnierkiewicz
2015-08-07 10:34 ` Bartlomiej Zolnierkiewicz
2015-08-07 10:41 ` Viresh Kumar
2015-08-07 10:41 ` Viresh Kumar
2015-08-07 11:12 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:12 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:37 ` Viresh Kumar
2015-08-07 11:37 ` Viresh Kumar
2015-08-07 22:21 ` Rafael J. Wysocki
2015-08-07 22:21 ` Rafael J. Wysocki
2015-08-08 2:06 ` Viresh Kumar
2015-08-08 2:06 ` Viresh Kumar
2015-08-06 13:41 ` [PATCH v4 2/6] clk: samsung: exynos4x12: add cpu clock configuration data and instantiate cpu clock Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-25 18:40 ` Michael Turquette
2015-08-25 18:40 ` Michael Turquette
2015-08-25 18:40 ` Michael Turquette
2015-08-25 18:40 ` Michael Turquette
2015-08-06 13:41 ` [PATCH v4 3/6] ARM: dts: Exynos4x12: add CPU OPP and regulator supply property Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` [PATCH v4 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4x12 Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` [PATCH v4 5/6] cpufreq: exynos: remove Exynos4x12 specific cpufreq driver support Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` [PATCH v4 6/6] cpufreq: remove no longer needed CPU_FREQ_BOOST_SW config option Bartlomiej Zolnierkiewicz
2015-08-06 13:41 ` Bartlomiej Zolnierkiewicz
2015-08-07 4:31 ` Viresh Kumar
2015-08-07 4:31 ` Viresh Kumar
2015-08-06 23:53 ` [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Kukjin Kim
2015-08-06 23:53 ` Kukjin Kim
2015-08-07 3:50 ` Viresh Kumar
2015-08-07 3:50 ` Viresh Kumar
2015-08-07 3:51 ` Viresh Kumar
2015-08-07 3:51 ` Viresh Kumar
2015-08-07 4:13 ` Krzysztof Kozlowski
2015-08-07 4:13 ` Krzysztof Kozlowski
2015-08-07 4:30 ` Viresh Kumar
2015-08-07 4:30 ` Viresh Kumar
2015-08-07 4:52 ` Krzysztof Kozlowski
2015-08-07 4:52 ` Krzysztof Kozlowski
2015-08-07 5:18 ` Viresh Kumar
2015-08-07 5:18 ` Viresh Kumar
2015-08-07 11:31 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:31 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:39 ` Viresh Kumar [this message]
2015-08-07 11:39 ` Viresh Kumar
2015-08-07 11:47 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:47 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:56 ` Viresh Kumar
2015-08-07 11:56 ` Viresh Kumar
2015-08-07 22:24 ` Rafael J. Wysocki
2015-08-07 22:24 ` Rafael J. Wysocki
2015-08-08 2:07 ` Viresh Kumar
2015-08-08 2:07 ` Viresh Kumar
2015-08-08 7:27 ` Krzysztof Kozlowski
2015-08-08 7:27 ` Krzysztof Kozlowski
2015-08-08 13:59 ` Viresh Kumar
2015-08-08 13:59 ` Viresh Kumar
2015-08-10 1:27 ` Kukjin Kim
2015-08-10 1:27 ` Kukjin Kim
2015-08-11 2:20 ` Krzysztof Kozlowski
2015-08-11 2:20 ` Krzysztof Kozlowski
2015-08-11 7:51 ` Kukjin Kim
2015-08-11 7:51 ` Kukjin Kim
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=20150807113950.GG6939@linux \
--to=viresh.kumar@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=heiko@sntech.de \
--cc=javier@dowhile0.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=s.nawrocki@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=tjakobi@math.uni-bielefeld.de \
--cc=tomasz.figa@gmail.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.