linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Abraham <ta.omasab@gmail.com>
To: Kevin Hilman <khilman@kernel.org>
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>,
	"Tomasz Figa" <tomasz.figa@gmail.com>,
	"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 4/6] ARM: Exynos: switch to using generic cpufreq driver for Exynos4210/5250/5420
Date: Fri, 21 Nov 2014 23:31:20 +0900	[thread overview]
Message-ID: <CAJuA9agpbDZrtmiQYexuAcS5GZeeB2YY22HTFQRPxnA+CLWb3Q@mail.gmail.com> (raw)
In-Reply-To: <CAMAWPa_V2rO9Ymezf0xPqeQNykCFq9QwLsNOG3EgPZfP-8MRBQ@mail.gmail.com>

Hi Kevin,

On Thu, Nov 20, 2014 at 2:30 AM, Kevin Hilman <khilman@kernel.org> wrote:
> Hi Thomas,
>
> On Mon, Oct 20, 2014 at 4:41 AM, Thomas Abraham <thomas.ab@samsung.com> wrote:
>> The new CPU clock type allows the use of generic CPUfreq drivers. So for
>> Exynos4210/5250, switch to using generic cpufreq driver. For Exynos5420,
>> which did not have CPUfreq driver support, enable the use of generic
>> CPUfreq driver.
>>
>> Suggested-by: Tomasz Figa <tomasz.figa@gmail.com>
>> Cc: Kukjin Kim <kgene.kim@samsung.com>
>> Signed-off-by: Thomas Abraham <thomas.ab@samsung.com>
>> Reviewed-by: Tomasz Figa <tomasz.figa@gmail.com>
>> Tested-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>> Tested-by: Chander Kashyap <k.chander@samsung.com>
>
> What's the status of the exynos5 CPUfreq support for upstream?  This
> was pretty broadly reviewed and tested, but I still don't see this
> either in linux-next or Kukjin's for-next.

The rebased version of the patches have been posted [1]. My apologies
for the delay in following up on this patch series.

Thanks,
Thomas.

[1] http://www.spinics.net/lists/arm-kernel/msg380011.html

>
> Kevin
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2014-11-21 14:31 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
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 [this message]
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=CAJuA9agpbDZrtmiQYexuAcS5GZeeB2YY22HTFQRPxnA+CLWb3Q@mail.gmail.com \
    --to=ta.omasab@gmail.com \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=khilman@kernel.org \
    --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=tomasz.figa@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).