From: Sekhar Nori <nsekhar@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [Query] CPUFreq: Does these machines have separate clock domains for CPUs?
Date: Thu, 29 Aug 2013 10:35:14 +0000 [thread overview]
Message-ID: <521F2112.5070501@ti.com> (raw)
In-Reply-To: <CAKohponWn-RN7-6sdhghd6RGCOd357G+TKLsxHfqnSCuMD7xxw@mail.gmail.com>
On Thursday 29 August 2013 03:45 PM, Viresh Kumar wrote:
> Hi,
>
> I have been doing some CPUFreq cleanup work and
> wanted to know if the below mentioned machines have separate
> clock domains for their CPUs or all share the same domain?
On DaVinci (DA850), there is an async domain available to keep some
peripheral clocks insulated from cpu frequency changes. But there are a
bunch of other clocks which do get affected by CPU frequency change
(they need to run at a fixed ratio to CPU frequency).
Thanks,
Sekhar
next prev parent reply other threads:[~2013-08-29 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 10:27 [Query] CPUFreq: Does these machines have separate clock domains for CPUs? Viresh Kumar
2013-08-29 10:35 ` Sekhar Nori [this message]
2013-08-29 10:42 ` Viresh Kumar
2013-08-29 10:39 ` Sekhar Nori
2013-08-29 10:45 ` Viresh Kumar
2013-08-29 22:41 ` Aaro Koskinen
2013-08-30 4:21 ` Mikael Starvik
2013-08-30 6:48 ` Magnus Damm
2013-08-30 7:45 ` Viresh Kumar
2013-09-04 7:27 ` Magnus Damm
2013-08-30 8:49 ` Benjamin Herrenschmidt
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=521F2112.5070501@ti.com \
--to=nsekhar@ti.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).