From: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
To: Amit Kucheria <kucheria.amit@gmail.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: Alternative Concept
Date: Tue, 20 Mar 2007 18:08:06 +0300 [thread overview]
Message-ID: <45FFF8D6.5050507@gmail.com> (raw)
In-Reply-To: <52d486620703200726i6fab332eoa843eb689cd4cf21@mail.gmail.com>
Amit Kucheria wrote:
> On 3/20/07, David Brownell <david-b@pacbell.net> wrote:
>> On Monday 19 March 2007 7:12 am, Scott E. Preece wrote:
>>> Could you guys present a clear definition of exactly what you mean by
>>> "clock domain" and "power domain"? I can think of several different ways
>>> to interpret the phrases, and I'd like to end up with the same meaning
>>> that you are arguing from...
>> A set of devices that use the same power supply or clock are
>> in the same "power domain" or "clock domain" (respectively).
>>
>> The domains will often be hierarchical, e.g. a base clock
>> rooting other clocks, derived from it by dividers, PLL,
>> or clock gates.
>>
>> Sometimes domains overlap ... e.g. a controller that needs
>> to use one logic level for on-chip logic and another for the
>> external interface; or similarly, different clock rates.
>>
>> Simple chips may not have many domains. Nowadays I think
>> most SOCs have at least a decent selection of clock domains,
>> to eliminate the power drain involved in driving transistors
>> through clock ticks. I understand it's more complicated to
>> have multiple power domains, but the incentive to shrink the
>> leakage current is strong. (So adding on-chip power domains
>> involves tricks to constrain leakage, and not just an ability
>> to operate without a given power rail.)
>
> For the sake of completeness, there is also the Voltage domain. A
> groups of modules supplied by the same regulator would belong to a
> single Voltage domain. Multiple voltage domains allow independent
> scaling of voltages to different domains.
If you forget ability of scaling voltage for the domain, does the domain
become a power domain, IOW is a power domain the simplest case of
voltage domain which doesn't not support voltage scalinig in any of
its states (no scaling in active mode, no scaling in idle mode, no
scaling in
retention mode)?
Thanks,
Dmitry
next prev parent reply other threads:[~2007-03-20 15:08 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 14:12 Alternative Concept Scott E. Preece
2007-03-20 7:56 ` David Brownell
2007-03-20 14:26 ` Amit Kucheria
2007-03-20 15:08 ` Dmitry Krivoschekov [this message]
2007-03-20 17:04 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2007-03-15 14:00 Scott E. Preece
2007-03-15 14:38 ` Eugeny S. Mints
2007-03-15 17:33 ` Woodruff, Richard
2007-03-15 13:29 Scott E. Preece
2007-03-15 23:07 ` David Brownell
2007-03-15 13:21 Scott E. Preece
2007-03-14 22:08 Scott E. Preece
2007-03-14 23:23 ` David Brownell
2007-03-15 7:25 ` Ikhwan Lee
2007-03-15 8:14 ` Amit Kucheria
2007-03-15 10:55 ` Eugeny S. Mints
2007-03-15 10:46 ` Eugeny S. Mints
2007-03-15 10:33 ` Eugeny S. Mints
2006-08-24 1:23 [RFC] CPUFreq PowerOP integration, Intro 0/3 Eugeny S. Mints
2006-10-07 2:36 ` Alternative Concept [Was: Re: [RFC] CPUFreq PowerOP integration, Intro 0/3] Dominik Brodowski
2007-03-13 0:57 ` Alternative Concept Matthew Locke
2007-03-13 11:08 ` Pavel Machek
2007-03-13 20:34 ` Mark Gross
2007-03-14 2:30 ` Ikhwan Lee
2007-03-14 10:43 ` Eugeny S. Mints
2007-03-14 17:19 ` David Brownell
2007-03-14 18:12 ` Igor Stoppa
2007-03-14 18:45 ` David Brownell
2007-03-15 9:53 ` Eugeny S. Mints
2007-03-15 13:04 ` Igor Stoppa
2007-03-16 2:21 ` David Brownell
2007-03-16 3:56 ` Ikhwan Lee
2007-03-16 6:17 ` David Brownell
2007-03-19 2:27 ` Ikhwan Lee
2007-03-19 6:07 ` David Brownell
2007-03-16 13:06 ` Dmitry Krivoschekov
2007-03-16 18:03 ` David Brownell
2007-03-18 20:25 ` Dmitry Krivoschekov
2007-03-19 4:04 ` David Brownell
2007-03-20 0:03 ` Dmitry Krivoschekov
2007-03-20 8:07 ` David Brownell
2007-03-20 9:45 ` Dmitry Krivoschekov
2007-03-20 10:30 ` Igor Stoppa
2007-03-20 12:13 ` Eugeny S. Mints
2007-03-20 12:39 ` Igor Stoppa
2007-03-20 13:44 ` Dmitry Krivoschekov
2007-03-20 21:03 ` David Brownell
2007-03-20 13:07 ` Dmitry Krivoschekov
2007-03-20 13:52 ` Igor Stoppa
2007-03-20 14:58 ` Dmitry Krivoschekov
2007-03-20 15:36 ` Pavel Machek
2007-03-20 19:16 ` Dmitry Krivoschekov
2007-03-20 20:45 ` Pavel Machek
2007-03-20 22:04 ` David Brownell
2007-03-20 22:06 ` Pavel Machek
2007-03-20 23:29 ` David Brownell
2007-03-20 15:36 ` Igor Stoppa
2007-03-20 19:17 ` Dmitry Krivoschekov
2007-03-20 20:17 ` David Brownell
2007-03-20 20:21 ` David Brownell
2007-03-20 19:58 ` David Brownell
2007-03-14 3:19 ` Dominik Brodowski
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=45FFF8D6.5050507@gmail.com \
--to=dmitry.krivoschekov@gmail.com \
--cc=kucheria.amit@gmail.com \
--cc=linux-pm@lists.osdl.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