From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] cpufreq: use generic cpufreq drivers for Exynos4x12 platform
Date: Fri, 07 Aug 2015 13:47:26 +0200 [thread overview]
Message-ID: <2359635.Hxe4cb8zKm@amdc1976> (raw)
In-Reply-To: <20150807113950.GG6939@linux>
On Friday, August 07, 2015 05:09:50 PM Viresh Kumar wrote:
> 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 :)
OK.
> > 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 ?
Hmm, wait. Patch 6/6 depends on earlier changes. I cannot remove
the config option in question now as it is currently used by
exynos-cpufreq specific boost support. Patch 1/6 can be applied
now but 6/6 needs to wait for patches 2-5 to be applied first.
Actually 6/6 is trivial and can be applied later in v4.3 cycle or
even in v4.4 one.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2015-08-07 11:47 UTC|newest]
Thread overview: 34+ 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 ` [PATCH v4 1/6] cpufreq: make scaling_boost_freqs sysfs attr available when boost is enabled Bartlomiej Zolnierkiewicz
2015-08-07 3:41 ` Viresh Kumar
2015-08-07 10:34 ` Bartlomiej Zolnierkiewicz
2015-08-07 10:41 ` Viresh Kumar
2015-08-07 11:12 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:37 ` Viresh Kumar
2015-08-07 22:21 ` Rafael J. Wysocki
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-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 ` [PATCH v4 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4x12 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 ` [PATCH v4 6/6] cpufreq: remove no longer needed CPU_FREQ_BOOST_SW config option Bartlomiej Zolnierkiewicz
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-07 3:50 ` Viresh Kumar
2015-08-07 3:51 ` Viresh Kumar
2015-08-07 4:13 ` Krzysztof Kozlowski
2015-08-07 4:30 ` Viresh Kumar
2015-08-07 4:52 ` Krzysztof Kozlowski
2015-08-07 5:18 ` Viresh Kumar
2015-08-07 11:31 ` Bartlomiej Zolnierkiewicz
2015-08-07 11:39 ` Viresh Kumar
2015-08-07 11:47 ` Bartlomiej Zolnierkiewicz [this message]
2015-08-07 11:56 ` Viresh Kumar
2015-08-07 22:24 ` Rafael J. Wysocki
2015-08-08 2:07 ` Viresh Kumar
2015-08-08 7:27 ` Krzysztof Kozlowski
2015-08-08 13:59 ` Viresh Kumar
2015-08-10 1:27 ` Kukjin Kim
2015-08-11 2:20 ` Krzysztof Kozlowski
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=2359635.Hxe4cb8zKm@amdc1976 \
--to=b.zolnierkie@samsung.com \
--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