From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Paul Walmsley <paul@pwsan.com>, Stephen Boyd <sboyd@codeaurora.org>
Cc: Tero Kristo <t-kristo@ti.com>, Tony Lindgren <tony@atomide.com>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>,
Mike Turquette <mturquette@linaro.org>,
<linux-clk@vger.kernel.org>
Subject: Re: [PATCHv3 10/10] CLK: TI: always enable DESHDCP clock
Date: Fri, 22 May 2015 09:27:07 +0300 [thread overview]
Message-ID: <555ECC3B.6000701@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505210254330.7960@utopia.booyaka.com>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On 21/05/15 06:06, Paul Walmsley wrote:
>> Enable falls under the "critical clocks" discussion that is ongoing. I
>> assume that this is some sort of critical clock that can't be turned off?
>
> It only needs to be enabled for this particular display IP subsystem to
> function:
>
> http://marc.info/?l=linux-omap&m=142071550111482&w=2
>
> I believe Tomi is taking this approach (enabling it unconditionally) to
> avoid adding support for a secondary IP block "main clock" to the hwmod
Right. I don't think that would be a simple task (correct me if I'm
wrong), and that would all be only for this one IP on this particular
SoC type.
> code. Apparently, the chips that contain this clock gating bit are not
> intended to be used for power-critical use cases, so there's not much
> motivation to switch it on and off with the display controller.
Even in power-critical use cases the the power use difference should be
negligible.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-05-22 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430906938-26128-1-git-send-email-tomi.valkeinen@ti.com>
[not found] ` <1430906938-26128-11-git-send-email-tomi.valkeinen@ti.com>
[not found] ` <555C744C.6070901@ti.com>
[not found] ` <555C74E8.5010105@ti.com>
[not found] ` <555CE1BF.4050506@codeaurora.org>
2015-05-21 3:06 ` [PATCHv3 10/10] CLK: TI: always enable DESHDCP clock Paul Walmsley
2015-05-22 6:27 ` Tomi Valkeinen [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=555ECC3B.6000701@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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).