From: sbkim73@samsung.com (Sangbeom Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: S3C6410: Support 800MHz operation in cpufreq
Date: Wed, 01 Jun 2011 19:30:42 +0900 [thread overview]
Message-ID: <037201cc2046$f5cc53b0$e164fb10$@com> (raw)
In-Reply-To: <1306921493-30911-4-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi, Mark
800Mhz S3C6410 is only supplied by customer request.
800Mhz dvfs operation should be controlled carefully.
(Stable VDD_ARM should be supplied)
To optimize s3c6410 dvfs operation, not only ARMCLK
But also HCLK should do dvfs.
In other words, VDD_INT, as well as VDD_ARM should be controlled.
Thanks and regards,
SB Kim
On Wed, Jun 1, 2011 at 6:45 PM, Mark Brown
> 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>
> ---
> drivers/cpufreq/s3c64xx.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/cpufreq/s3c64xx.c b/drivers/cpufreq/s3c64xx.c
> index fc3f180..fc69178 100644
> --- a/drivers/cpufreq/s3c64xx.c
> +++ b/drivers/cpufreq/s3c64xx.c
> @@ -31,6 +31,7 @@ static struct s3c64xx_dvfs s3c64xx_dvfs_table[] = {
> [1] = { 1050000, 1150000 },
> [2] = { 1100000, 1150000 },
> [3] = { 1200000, 1350000 },
> + [4] = { 1300000, 1350000 },
> };
>
> static struct cpufreq_frequency_table s3c64xx_freq_table[] = {
> @@ -43,6 +44,7 @@ static struct cpufreq_frequency_table
> s3c64xx_freq_table[] = {
> { 2, 532000 },
> { 2, 533000 },
> { 3, 667000 },
> + { 4, 800000 },
> { 0, CPUFREQ_TABLE_END },
> };
> #endif
> --
> 1.7.5.3
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2011-06-01 10:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 9:43 [PATCH 0/5] S3C64xx updates Mark Brown
2011-06-01 9:44 ` [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq Mark Brown
2011-06-01 9:44 ` [PATCH 2/5] ARM: SAMSUNG: Add support for pre-sleep/post-restore gpio control Mark Brown
2011-06-01 9:44 ` [PATCH 3/5] ARM: S3C64XX: Ensure VIC based IRQs can be resumed from Mark Brown
2011-06-01 9:44 ` [PATCH 4/5] ARM: S3C6410: Support 800MHz operation in cpufreq Mark Brown
2011-06-01 10:30 ` Sangbeom Kim [this message]
2011-06-01 10:40 ` Mark Brown
2011-06-02 0:11 ` Sangbeom Kim
2011-06-02 8:28 ` Mark Brown
2011-06-02 9:41 ` Sangbeom Kim
2011-06-02 9:44 ` Kyungmin Park
2011-06-02 9:50 ` Jassi Brar
2011-06-02 9:55 ` Vasily Khoruzhick
2011-06-02 9:56 ` Mark Brown
2011-06-02 9:57 ` Kyungmin Park
2011-06-01 9:44 ` [PATCH 5/5] ARM: S3C6410: Add some lower frequencies for 800MHz base clock operation Mark Brown
2011-06-01 9:55 ` [PATCH 1/5] CPUFREQ/S3C64xx: Move S3C64xx CPUfreq driver into drivers/cpufreq Kyungmin Park
2011-06-01 9:58 ` Mark Brown
2011-06-01 16:45 ` Dave Jones
2011-06-07 0:59 ` Dave Jones
2011-06-01 20:00 ` Kukjin Kim
2011-06-01 20:01 ` Mark Brown
2011-06-01 20:30 ` 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='037201cc2046$f5cc53b0$e164fb10$@com' \
--to=sbkim73@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;
as well as URLs for NNTP newsgroup(s).