linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Thomas Abraham <ta.omasab@gmail.com>
Cc: "Lukasz Majewski" <l.majewski@samsung.com>,
	"Kukjin Kim" <kgene.kim@samsung.com>,
	"Mike Turquette" <mturquette@linaro.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Chanwoo Choi" <cw00.choi@samsung.com>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v11 0/6] cpufreq: use generic cpufreq drivers for exynos platforms
Date: Mon, 20 Oct 2014 16:18:10 +0200	[thread overview]
Message-ID: <544519A2.8010604@gmail.com> (raw)
In-Reply-To: <CAJuA9ajv_e0FriiPL0aHWLv7+AoZAF2E+G-0r6UGC6RzxM_wmA@mail.gmail.com>



On 20.10.2014 13:48, Thomas Abraham wrote:
> Hi Tomasz,
> 
> On Mon, Oct 20, 2014 at 5:05 PM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
>> On 20.10.2014 13:41, Thomas Abraham wrote:
>>> Changes since v10:
>>> - Rebased on top of v3.18-rc1
>>>
>>> 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 patch series is based and tested on v3.18-rc1 and depends on the patch
>>> - "clk: exynos4: remove duplicate div_core2 divider clock instantiation"
>>>   (http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34859.html)
>>>   This patch has been merged in "arm-soc/samsung/dt3" branch of arm-soc tree.
>>>
>>
>> That patch actually went through clock tree, but it doesn't matter,
>> because AFAIK all the dependencies for this series are already in
>> 3.18-rc1. I'll try to apply it in next days
> 
> Thanks. The patch "clk: exynos4: remove duplicate div_core2 divider
> clock instantiation" is not available in 3.18-rc1. So for testing, I
> picked this patch from samsung/dt3 branch from arm-soc tree.

Hmm? I can see it there:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/clk/samsung?id=v3.18-rc1

Best regards,
Tomasz

  reply	other threads:[~2014-10-20 14:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 11:41 [PATCH v11 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Thomas Abraham
2014-10-20 11:35 ` Tomasz Figa
2014-10-20 11:48   ` Thomas Abraham
2014-10-20 14:18     ` Tomasz Figa [this message]
2014-10-20 11:41 ` [PATCH v11 1/6] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham
2014-10-20 11:41   ` [PATCH v11 2/6] clk: samsung: add cpu clock configuration data and instantiate cpu clock Thomas Abraham
2014-10-20 11:41     ` [PATCH v11 3/6] ARM: dts: Exynos: add CPU OPP and regulator supply property Thomas Abraham
2014-10-20 11:41       ` [PATCH v11 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420 Thomas Abraham
2014-10-20 11:41         ` [PATCH v11 5/6] cpufreq: exynos: remove exynos4210/5250 specific cpufreq driver support Thomas Abraham
2014-10-20 11:32           ` Viresh Kumar
2014-10-20 11:38             ` Thomas Abraham
2014-10-20 12:09               ` Thomas Abraham
2014-10-20 11:41           ` [PATCH v11 6/6] clk: samsung: remove unused clock aliases and update clock flags Thomas Abraham
2014-11-12  6:03         ` [PATCH v11 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420 Amit Kucheria
2014-11-21 14:32           ` Thomas Abraham
2014-11-19 17:30         ` Kevin Hilman
2014-11-21 14:31           ` Thomas Abraham
2014-11-19 19:28         ` Sudeep Holla
2014-11-20  3:48           ` Viresh Kumar
2014-11-24 13:44             ` Sudeep Holla
2014-11-25 11:02               ` Viresh Kumar

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=544519A2.8010604@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=l.majewski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=ta.omasab@gmail.com \
    --cc=viresh.kumar@linaro.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).