From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V3 0/7] ARM: tegra30: cpuidle: add a powered-down state
Date: Tue, 30 Oct 2012 16:45:10 -0600 [thread overview]
Message-ID: <50905876.70108@wwwdotorg.org> (raw)
In-Reply-To: <1351506501-600-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 10/29/2012 04:28 AM, Joseph Lo wrote:
> This adds a "powered-down" state for cpuidle. It's a power gating idle
> mode. It supports the secondary CPUs (i.e., CPU1-CPU3) to go into
> powered-down state independently. When any of the secondary CPUs go into
> this state, it can be power gated alone. There is a limitation on CPU0.
> The CPU0 can go into powered-down state only when all secondary CPU is
> offline. After CPU0 is in powered-down state, the CPU rail can be turned
> off.
This series doesn't seem to apply to Tegra's current for-next, nor
next-20121029. What is it based on?
Note: I did try merging "ARM: tegra: rename the file of "sleep-tXX" to
"sleep-tegraXX"" first, since I assume that's a dependency.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/7] ARM: tegra30: cpuidle: add a powered-down state
Date: Tue, 30 Oct 2012 16:45:10 -0600 [thread overview]
Message-ID: <50905876.70108@wwwdotorg.org> (raw)
In-Reply-To: <1351506501-600-1-git-send-email-josephl@nvidia.com>
On 10/29/2012 04:28 AM, Joseph Lo wrote:
> This adds a "powered-down" state for cpuidle. It's a power gating idle
> mode. It supports the secondary CPUs (i.e., CPU1-CPU3) to go into
> powered-down state independently. When any of the secondary CPUs go into
> this state, it can be power gated alone. There is a limitation on CPU0.
> The CPU0 can go into powered-down state only when all secondary CPU is
> offline. After CPU0 is in powered-down state, the CPU rail can be turned
> off.
This series doesn't seem to apply to Tegra's current for-next, nor
next-20121029. What is it based on?
Note: I did try merging "ARM: tegra: rename the file of "sleep-tXX" to
"sleep-tegraXX"" first, since I assume that's a dependency.
next prev parent reply other threads:[~2012-10-30 22:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 10:28 [PATCH V3 0/7] ARM: tegra30: cpuidle: add a powered-down state Joseph Lo
2012-10-29 10:28 ` Joseph Lo
[not found] ` <1351506501-600-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-29 10:28 ` [PATCH V3 1/7] ARM: tegra: cpuidle: separate cpuidle driver for different chips Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-29 10:28 ` [PATCH V3 2/7] ARM: tegra: cpuidle: add CPU resume function Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-29 10:28 ` [PATCH V3 3/7] ARM: tegra30: cpuidle: add powered-down state for secondary CPUs Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-29 10:28 ` [PATCH V3 4/7] ARM: tegra30: common: enable csite clock Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-29 10:28 ` [PATCH V3 5/7] ARM: tegra30: clocks: add CPU low-power function into tegra_cpu_car_ops Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-29 10:28 ` [PATCH V3 6/7] ARM: tegra30: flowctrl: add cpu_suspend_exter/exit function Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-29 10:28 ` [PATCH V3 7/7] ARM: tegra30: cpuidle: add powered-down state for CPU0 Joseph Lo
2012-10-29 10:28 ` Joseph Lo
2012-10-30 22:45 ` Stephen Warren [this message]
2012-10-30 22:45 ` [PATCH V3 0/7] ARM: tegra30: cpuidle: add a powered-down state Stephen Warren
[not found] ` <50905876.70108-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-31 1:35 ` Joseph Lo
2012-10-31 1:35 ` Joseph Lo
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=50905876.70108@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.