From: l.majewski@samsung.com (Lukasz Majewski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v12 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
Date: Mon, 16 Feb 2015 10:52:17 +0100 [thread overview]
Message-ID: <20150216105217.79315ffd@amdc2363> (raw)
In-Reply-To: <CAJKOXPfyPH7tyce6YB=q4krSP078aJVAmqObg89qCnLrL_Nbhg@mail.gmail.com>
Hi Krzysztof, Thomas,
> 2015-01-08 22:17 GMT+01:00 Kevin Hilman <khilman@kernel.org>:
> > On Fri, Nov 21, 2014 at 5:31 AM, Thomas Abraham
> > <thomas.ab@samsung.com> wrote:
> >> Changes since v11:
> >> - Rebased on top of git://linuxtv.org/snawrocki/samsung.git
> >> for-v3.19-exynos-clk
> >>
> >> This patch series removes the use of Exynos4210 and Exynos5250
> >> specific cpufreq drivers and enables the use of cpufreq-dt driver
> >> for these platforms. This series also enables cpufreq support for
> >> Exynos5420 using arm_big_little cpufreq driver.
> >>
> >> This series is based on the following branch.
> >> git://linuxtv.org/snawrocki/samsung.git for-v3.19-exynos-clk
> >>
> >> This series depends on the following patch which can be picked from
> >> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> >> samsung/dt e540920cf21c (ARM: dts: add CPU nodes for Exynos4 SoCs).
> >>
> >> This patch series has been tested on Exynos4210/5250/5420 based
> >> boards. Tomasz Figa had plans to take this in the Samsung clock
> >> tree for v3.19
> >> (http://www.spinics.net/lists/linux-samsung-soc/msg37933.html).
> >> Sylwester, could you consider to merge this in your tree?
> >
> > CPUfreq for exynos is still not upstream. What's the status of this
> > series? It's been ver a month since there's been any activity here
> > (or any responses to the issues I reported.)
> >
> > On a related note, this series only does frequency scaling. Is there
> > any work going on to also enable voltage scaling for the CPU rails
> > as well?
>
> Hi Thomas,
>
> Do you plan to continue with this work? It would be very helpful.
+1 from me.
>
> I also wonder if Exynos 4412 could be re-added (without the boost if
> these bindings are not ready)?
I would prefer to have all platforms converted at once, since it might
happen that some parts of the work would get lost.
>
> Best regards,
> Krzysztof
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2015-02-16 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 13:31 [PATCH v12 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Thomas Abraham
2014-11-21 13:31 ` [PATCH v12 1/6] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham
2014-11-21 13:31 ` [PATCH v12 2/6] clk: samsung: add cpu clock configuration data and instantiate cpu clock Thomas Abraham
2014-11-21 13:31 ` [PATCH v12 3/6] ARM: dts: Exynos: add CPU OPP and regulator supply property Thomas Abraham
2014-11-21 13:31 ` [PATCH v12 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420 Thomas Abraham
2014-11-21 13:31 ` [PATCH v12 5/6] cpufreq: exynos: remove exynos4210/5250 specific cpufreq driver support Thomas Abraham
2014-11-21 13:31 ` [PATCH v12 6/6] clk: samsung: remove unused clock aliases and update clock flags Thomas Abraham
2014-11-21 14:11 ` [PATCH v12 3/6] ARM: dts: Exynos: add CPU OPP and regulator supply property Andreas Färber
2014-11-24 15:14 ` [PATCH v12 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Sylwester Nawrocki
2014-11-24 18:58 ` Kevin Hilman
2014-11-25 19:57 ` Kevin Hilman
2014-11-26 18:27 ` Kevin Hilman
2015-01-08 21:17 ` Kevin Hilman
2015-02-10 11:10 ` Krzysztof Kozlowski
2015-02-16 9:52 ` Lukasz Majewski [this message]
2015-02-17 20:25 ` Tobias Jakobi
2015-03-18 9:31 ` Javier Martinez Canillas
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=20150216105217.79315ffd@amdc2363 \
--to=l.majewski@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