From: Marek Szyprowski <m.szyprowski@samsung.com>
To: "'Mark Brown'" <broonie@opensource.wolfsonmicro.com>,
"'Kukjin Kim'" <kgene.kim@samsung.com>
Cc: "'Jeongbae Seo'" <jeongbae.seo@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Changhwan Youn'" <chaos.youn@samsung.com>,
linux-arm-kernel@lists.infradead.org, lrg@slimlogic.co.uk
Subject: RE: [PATCH] regulator: Add support samsung power domain
Date: Fri, 17 Sep 2010 13:45:36 +0200 [thread overview]
Message-ID: <007b01cb565d$db4376d0$91ca6470$%szyprowski@samsung.com> (raw)
In-Reply-To: <20100917113050.GA4322@rakim.wolfsonmicro.main>
Hello,
On Friday, September 17, 2010 1:31 PM Mark Brown wrote:
> Another option to consider here is using runtime PM - other platforms
> seem to be going down that route, and are using it to also factor clock
> management for the IP blocks out (so that the block's clocks get enabled
> and disabled automatically when the block is active without needing any
> code in the driver).
The approach with merging power domains with clocks have some disadvantages.
In some cases the clock gating and power gating should be distinguished.
Just assume an IP like a video codec. It has it's own internal state machine.
It gets reset when the ip is power gated, but it is preserved during clock
gating. The driver might want to do a clock gating when it is waiting for a
new frame to decode, but should do power gating only when the device has
been closed. Having a set of fake clocks just for power gating imho doesn't
look good.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
next prev parent reply other threads:[~2010-09-17 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 9:58 [PATCH] regulator: Add support samsung power domain Kukjin Kim
2010-09-17 11:30 ` Mark Brown
2010-09-17 11:45 ` Marek Szyprowski [this message]
2010-09-17 12:07 ` Mark Brown
2010-09-20 6:12 ` Kukjin Kim
2010-09-20 9:50 ` Mark Brown
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='007b01cb565d$db4376d0$91ca6470$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=chaos.youn@samsung.com \
--cc=jeongbae.seo@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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