From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] cpufreq: Add S3C2416/S3C2450 cpufreq driver
Date: Fri, 30 Dec 2011 13:00:42 +0100 [thread overview]
Message-ID: <201112301300.43730.heiko@sntech.de> (raw)
In-Reply-To: <20111230082319.GC2414@b20223-02.ap.freescale.net>
Hi Richard,
Am Freitag 30 Dezember 2011, 09:23:21 schrieb Richard Zhao:
> would it be possible to use clk-reg-cpufreq driver I sent out?
I thought about it when your driver was introduced first. It would be possible
if the frequency scaling would only happen on the armdiv.
But as you probably saw in the code the S3C2416 has two clock sources for the
armclk (armdiv and hclk) and also special requirements on the switch of those
(i.e. when switching to armdiv, force the frequency to be the same as the
hclk, to prevent stability issues).
Therefore I don't think these behaviour requirements can be modelled with your
clk-reg-cpufreq driver.
Heiko
prev parent reply other threads:[~2011-12-30 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 19:58 [RFC] cpufreq: Add S3C2416/S3C2450 cpufreq driver Heiko Stübner
2011-12-30 7:48 ` Dron Gus
2011-12-30 12:07 ` Heiko Stübner
2011-12-30 8:23 ` Richard Zhao
2011-12-30 12:00 ` Heiko Stübner [this message]
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=201112301300.43730.heiko@sntech.de \
--to=heiko@sntech.de \
--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).