From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [CPUFREQ] S3C6410: Support 800MHz operation in cpufreq
Date: Wed, 8 Jun 2011 10:02:38 -0400 [thread overview]
Message-ID: <20110608140238.GB7204@redhat.com> (raw)
In-Reply-To: <1307540955-10086-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, Jun 08, 2011 at 02:49:15PM +0100, Mark Brown wrote:
> At least some newer S3C6410 silicon supports operation up to 800MHz rather
> than just 667MHz. Unfortunately I don't have access to any of documentation
> of this other than some running systems, add a new cpufreq table entry for
> this based on the behaviour of those systems.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>
> Kukjin already indicated on several occasions that he was happy with
> this change but it never seems to get applied or an actual ack.
applied, thanks.
Dave
next prev parent reply other threads:[~2011-06-08 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 13:49 [PATCH] [CPUFREQ] S3C6410: Support 800MHz operation in cpufreq Mark Brown
2011-06-08 14:02 ` Dave Jones [this message]
2011-06-09 18:29 ` 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=20110608140238.GB7204@redhat.com \
--to=davej@redhat.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;
as well as URLs for NNTP newsgroup(s).