linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM: Cortex-A9: Enable dynamic clock gating
Date: Fri, 11 Mar 2011 17:08:07 +0000	[thread overview]
Message-ID: <1299863287.7239.37.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <1298433325-16810-1-git-send-email-toddpoynor@google.com>

On Wed, 2011-02-23 at 03:55 +0000, Todd Poynor wrote:
> Enable dynamic high level clock gating for Cortex-A9 CPUs, as
> described in 2.3.3 "Dynamic high level clock gating" of the
> Cortex-A9 TRM.  This may cut the clock of the integer core,
> system control block, and Data Engine in certain conditions.
> 
> Add ARM errata 720791 to avoid corrupting the Jazelle
> instruction stream on earlier Cortex-A9 revisions.
> 
> Signed-off-by: Todd Poynor <toddpoynor@google.com>
> ---
> Can anyone advise whether this feature should be selectively
> enabled (or otherwise modified) due to secured register access,
> introduced latencies observed, etc.?
> 
> This has been tested on a few Tegra 2 boards without problems
> observed thus far, and some preliminary testing indicates it
> may result in fairly significant power savings.  Any additional
> testing greatly appreciated.

I haven't done any benchmarks on this, so can't comment on this.

My view is that something like the boot monitor/firmware should set this
up, though that's not always the case. On some OMAP boards Linux runs in
non-secure mode and it will fault when trying to set this bit.

-- 
Catalin

  reply	other threads:[~2011-03-11 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  3:55 [RFC] ARM: Cortex-A9: Enable dynamic clock gating Todd Poynor
2011-03-11 17:08 ` Catalin Marinas [this message]
2011-03-11 17:23   ` Santosh Shilimkar

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=1299863287.7239.37.camel@e102109-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.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).