From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>
Cc: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra <linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH V4 5/5] ARM: tegra20: cpuidle: apply coupled cpuidle for powered-down mode
Date: Wed, 16 Jan 2013 14:31:13 -0700 [thread overview]
Message-ID: <50F71C21.20904@wwwdotorg.org> (raw)
In-Reply-To: <CAMbhsRTmGVrjnKa_z+zonGypU+U4r2iE=D-Zfvyoq8chY68QKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 01/16/2013 11:55 AM, Colin Cross wrote:
> On Wed, Jan 16, 2013 at 12:11 AM, Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> wrote:
>> The "powered-down" cpuidle mode of Tegra20 needs the CPU0 be the last one
>> core to go into this mode before other core. The coupled cpuidle framework
>> can help to sync the MPCore to coupled state then go into "powered-down"
>> idle mode together. The driver can just assume the MPCore come into
>> "powered-down" mode at the same time. No need to take care if the CPU_0
>> goes into this mode along and only can put it into safe idle mode (WFI).
>>
>> The powered-down state of Tegra20 requires power gating both CPU cores.
>> When the secondary CPU requests to enter powered-down state, it saves
>> its own contexts and then enters WFI for waiting CPU0 in the same state.
>> When the CPU0 requests powered-down state, it attempts to put the secondary
>> CPU into reset to prevent it from waking up. Then power down both CPUs
>> together and power off the cpu rail.
>>
>> Be aware of that, you may see the legacy power state "LP2" in the code
Colin, since you only raised a few small issues on this series, does
that mean you're OK with it once those issues are fixed?
Joseph, we'll be merging Tegra114 in the near future. How will this
patch series affect Tegra114? Will the cpuidle driver simply fail to
register on Tegra114 (which would be fine until we explicitly add
support), or would we need to disable cpuidle in Kconfig to get a
working Tegra114 kernel. Does this patch series affect the answer to the
previous question? Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 5/5] ARM: tegra20: cpuidle: apply coupled cpuidle for powered-down mode
Date: Wed, 16 Jan 2013 14:31:13 -0700 [thread overview]
Message-ID: <50F71C21.20904@wwwdotorg.org> (raw)
In-Reply-To: <CAMbhsRTmGVrjnKa_z+zonGypU+U4r2iE=D-Zfvyoq8chY68QKQ@mail.gmail.com>
On 01/16/2013 11:55 AM, Colin Cross wrote:
> On Wed, Jan 16, 2013 at 12:11 AM, Joseph Lo <josephl@nvidia.com> wrote:
>> The "powered-down" cpuidle mode of Tegra20 needs the CPU0 be the last one
>> core to go into this mode before other core. The coupled cpuidle framework
>> can help to sync the MPCore to coupled state then go into "powered-down"
>> idle mode together. The driver can just assume the MPCore come into
>> "powered-down" mode at the same time. No need to take care if the CPU_0
>> goes into this mode along and only can put it into safe idle mode (WFI).
>>
>> The powered-down state of Tegra20 requires power gating both CPU cores.
>> When the secondary CPU requests to enter powered-down state, it saves
>> its own contexts and then enters WFI for waiting CPU0 in the same state.
>> When the CPU0 requests powered-down state, it attempts to put the secondary
>> CPU into reset to prevent it from waking up. Then power down both CPUs
>> together and power off the cpu rail.
>>
>> Be aware of that, you may see the legacy power state "LP2" in the code
Colin, since you only raised a few small issues on this series, does
that mean you're OK with it once those issues are fixed?
Joseph, we'll be merging Tegra114 in the near future. How will this
patch series affect Tegra114? Will the cpuidle driver simply fail to
register on Tegra114 (which would be fine until we explicitly add
support), or would we need to disable cpuidle in Kconfig to get a
working Tegra114 kernel. Does this patch series affect the answer to the
previous question? Thanks.
next prev parent reply other threads:[~2013-01-16 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 8:11 [PATCH V4 5/5] ARM: tegra20: cpuidle: apply coupled cpuidle for powered-down mode Joseph Lo
2013-01-16 8:11 ` Joseph Lo
[not found] ` <1358323873-30525-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-16 18:55 ` Colin Cross
2013-01-16 18:55 ` Colin Cross
[not found] ` <CAMbhsRTmGVrjnKa_z+zonGypU+U4r2iE=D-Zfvyoq8chY68QKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-16 21:31 ` Stephen Warren [this message]
2013-01-16 21:31 ` Stephen Warren
[not found] ` <50F71C21.20904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-16 22:51 ` Colin Cross
2013-01-16 22:51 ` Colin Cross
2013-01-17 2:30 ` Joseph Lo
2013-01-17 2:30 ` Joseph Lo
[not found] ` <1358389815.1667.32.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-01-17 16:48 ` Stephen Warren
2013-01-17 16:48 ` Stephen Warren
2013-01-17 2:05 ` Joseph Lo
2013-01-17 2:05 ` Joseph Lo
[not found] ` <1358388332.1667.7.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-01-17 2:32 ` Colin Cross
2013-01-17 2:32 ` Colin Cross
[not found] ` <CAMbhsRQpEE_bkLTZCKno_kDAHh5ggXm6qBSJ91K+ezqwoCsY5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-17 2:35 ` Joseph Lo
2013-01-17 2: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=50F71C21.20904@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@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 \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@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.