From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH V3 0/7] ARM: tegra30: cpuidle: add a powered-down state Date: Tue, 30 Oct 2012 16:45:10 -0600 Message-ID: <50905876.70108@wwwdotorg.org> References: <1351506501-600-1-git-send-email-josephl@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1351506501-600-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Joseph Lo Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-tegra@vger.kernel.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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Tue, 30 Oct 2012 16:45:10 -0600 Subject: [PATCH V3 0/7] ARM: tegra30: cpuidle: add a powered-down state In-Reply-To: <1351506501-600-1-git-send-email-josephl@nvidia.com> References: <1351506501-600-1-git-send-email-josephl@nvidia.com> Message-ID: <50905876.70108@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.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.