From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Lukasz Majewski <l.majewski@samsung.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Jonghwa Lee <jonghwa3.lee@samsung.com>,
Lukasz Majewski <l.majewski@majess.pl>,
linux-kernel <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Myungjoo Ham <myungjoo.ham@samsung.com>,
Yadwinder Singh Brar <yadi.brar01@gmail.com>,
Tomasz Figa <t.figa@samsung.com>
Subject: Re: [PATCH v2 0/2] cpufreq: exynos: Fixes for v3.12
Date: Fri, 11 Oct 2013 14:10:53 +0200 [thread overview]
Message-ID: <2822925.9aRTDAMrLp@vostro.rjw.lan> (raw)
In-Reply-To: <1457107.oQjJi4YKRz@vostro.rjw.lan>
On Friday, October 11, 2013 01:22:57 PM Rafael J. Wysocki wrote:
> On Wednesday, October 09, 2013 02:08:41 PM Lukasz Majewski wrote:
> > Attached commits provide cpufreq regression fixes for Trats and Trats2
> > Exynos4 boards.
> > Since v3.12 Exynos4 uses common clock framework for clock manipulation.
> > Those patches restore correct output for cpuinfo_cur_freq [1] sysfs
> > attribute.
> > Without them, the [1] provides default frequency (800 MHz) set at driver
> > initialization.
> >
> >
> > Lukasz Majewski (2):
> > cpufreq: exynos4x12: Use the common clock framework to set APLL clock
> > rate
> > cpufreq: exynos4210: Use the common clock framework to set APLL clock
> > rate
> >
> > drivers/cpufreq/exynos4210-cpufreq.c | 67 ++++-----------------------------
> > drivers/cpufreq/exynos4x12-cpufreq.c | 69 ++++------------------------------
> > 2 files changed, 16 insertions(+), 120 deletions(-)
>
> Can you please resend [1/2], it got lost somewhere (at least I can't see it
> now)?
Scratch this, it's there in patchwork.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-10-11 11:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 11:22 [PATCH 0/2] cpufreq: exynos: Fixes for v3.12 Lukasz Majewski
2013-09-25 11:22 ` [PATCH 1/2] cpufreq: exynos4x12: Use the common clock framework to set APLL clock rate Lukasz Majewski
2013-09-25 11:35 ` Sachin Kamat
2013-09-25 13:10 ` Lukasz Majewski
2013-09-25 13:55 ` Yadwinder Singh Brar
2013-09-25 14:03 ` Tomasz Figa
2013-09-26 6:14 ` Yadwinder Singh Brar
2013-09-26 9:16 ` Lukasz Majewski
2013-09-25 11:22 ` [PATCH 2/2] cpufreq: exynos4210: " Lukasz Majewski
2013-10-09 12:08 ` [PATCH v2 0/2] cpufreq: exynos: Fixes for v3.12 Lukasz Majewski
2013-10-09 12:08 ` [PATCH v2 1/2] cpufreq: exynos4x12: Use the common clock framework to set APLL clock rate Lukasz Majewski
2013-10-09 12:08 ` [PATCH v2 2/2] cpufreq: exynos4210: " Lukasz Majewski
2013-10-16 22:58 ` Rafael J. Wysocki
2013-10-11 6:06 ` [PATCH v2 0/2] cpufreq: exynos: Fixes for v3.12 Yadwinder Singh Brar
2013-10-11 11:22 ` Rafael J. Wysocki
2013-10-11 12:10 ` Rafael J. Wysocki [this message]
2013-10-14 5:55 ` Lukasz Majewski
2013-10-14 11:55 ` Rafael J. Wysocki
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=2822925.9aRTDAMrLp@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=b.zolnierkie@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=jonghwa3.lee@samsung.com \
--cc=l.majewski@majess.pl \
--cc=l.majewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=t.figa@samsung.com \
--cc=viresh.kumar@linaro.org \
--cc=yadi.brar01@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox