linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] ARM: S3C6410: Support 800MHz operation in cpufreq
Date: Wed, 1 Jun 2011 11:40:42 +0100	[thread overview]
Message-ID: <20110601104042.GA15387@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <037201cc2046$f5cc53b0$e164fb10$@com>

On Wed, Jun 01, 2011 at 07:30:42PM +0900, Sangbeom Kim wrote:
> Hi, Mark

Don't top post.

> 800Mhz S3C6410 is only supplied by customer request.
> 800Mhz dvfs operation should be controlled carefully.
> (Stable VDD_ARM should be supplied)

The fact that the chip is only on limited distribution isn't really an
issue for supporting it in mainline - many CPUs currently supported in
Linux, including some Samsung ones, are only available to certain
customers.

Similarly, stable power supplies are a basic system design thing that
we shouldn't be worrying about here.

> 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.

I don't have any access to documentation on this part here and in any
case we've already got code in mainline which is doing DVFS on S3C6410
without varying VDD_INT so that's a bit of a moot point.  We need to add
the 800MHz support in order to have the existing code understand the
state the device boots up in on the system I'm currently working with,
never mind actually change anything at runtime.  

As things stand the system will boot and then immediately scale the
voltage down to 400MHz as it's the only supported rate for 800MHz (we're
only doing scaling by division of the ARM clock) so adding the operating
point for 800MHz at least means that the performance governor will do
the right thing.

  reply	other threads:[~2011-06-01 10:40 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
2011-06-01 10:40       ` Mark Brown [this message]
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=20110601104042.GA15387@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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).