From: Stephen Warren <swarren@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
Russell King <linux@arm.linux.org.uk>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v1 0/3] Add support for LP3
Date: Thu, 26 Jan 2012 10:33:40 -0800 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF178CB823CD@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1327594923-21822-1-git-send-email-pdeschrijver@nvidia.com>
Peter De Schrijver wrote at Thursday, January 26, 2012 9:22 AM:
> Introduce support for LP3 (CPU core clockgating) for Tegra20 and Tegra30.
The series,
Acked-by: Stephen Warren <swarren@nvidia.com>
(although I'm not very familiar with cpuidle, so a review from e.g.
Colin would be great too)
Tested-by: Stephen Warren <swarren@nvidia.com>
(On Harmony, observed /sys/devices/system/cpu/cpu*/cpuidle/state0/usage
incrementing over time. Tested audio playback as well)
--
nvpublic
next prev parent reply other threads:[~2012-01-26 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:22 Peter De Schrijver
2012-01-26 16:22 ` [PATCH v1 1/3] ARM: tegra: definitions for flow controller Peter De Schrijver
2012-01-27 2:17 ` Olof Johansson
2012-01-27 8:15 ` Olof Johansson
2012-01-26 16:22 ` [PATCH v1 2/3] ARM: tegra: assembler code for LP3 Peter De Schrijver
2012-01-26 16:22 ` [PATCH v1 3/3] ARM: tegra: cpuidle driver for tegra Peter De Schrijver
2012-01-26 19:11 ` Mark Brown
2012-01-27 9:09 ` Bedia, Vaibhav
2012-01-27 6:59 ` Bedia, Vaibhav
2012-01-27 7:10 ` Colin Cross
2012-01-27 8:39 ` Bedia, Vaibhav
2012-02-01 7:35 ` Olof Johansson
2012-01-26 18:33 ` Stephen Warren [this message]
2012-01-26 21:49 ` [PATCH v1 0/3] Add support for LP3 Colin Cross
2012-02-01 7:35 ` Olof Johansson
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=74CDBE0F657A3D45AFBB94109FB122FF178CB823CD@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=pdeschrijver@nvidia.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
all inboxes | Powered by JetHome®