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: Thu, 02 Jun 2011 18:41:05 +0900 [thread overview]
Message-ID: <039601cc2109$319c9770$94d5c650$@com> (raw)
In-Reply-To: <20110602082830.GA3085@opensource.wolfsonmicro.com>
On Wed, Jun 2, 2011 at 9:11 AM, Mark Brown
>
> It's really unfortunate that there's no software visible method I'm
> aware of :/
Unfortunately, There is no method to detect 800Mhz s3c6410 by software.
> I'm not sure it's a particular concern for the 800MHz part above others
> simply because it's such a universal issue.
Because Voltage margin(VDD_ARM) of s3c6410 800Mhz is particularly weak.
Under 667Mhz, There is no issue for dvfs.
next prev parent reply other threads:[~2011-06-02 9:41 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
2011-06-02 0:11 ` Sangbeom Kim
2011-06-02 8:28 ` Mark Brown
2011-06-02 9:41 ` Sangbeom Kim [this message]
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='039601cc2109$319c9770$94d5c650$@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).