From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Daniel Lezcano
<daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH V2 3/3] ARM: tegra114: cpuidle: add powered-down state
Date: Wed, 12 Jun 2013 11:41:28 -0600 [thread overview]
Message-ID: <51B8B2C8.1090006@wwwdotorg.org> (raw)
In-Reply-To: <51AE5EE3.3010607-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On 06/04/2013 03:40 PM, Daniel Lezcano wrote:
> On 06/04/2013 12:48 PM, Joseph Lo wrote:
>> This supports CPU core power down on each CPU when CPU idle. When CPU go
>> into this state, it saves it's context and needs a proper configuration
>> in flow controller to power gate the CPU when CPU runs into WFI
>> instruction. And the CPU also needs to set the IRQ as CPU power down idle
>> wake up event in flow controller.
>>
>> Signed-off-by: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> I would like to understand why there is a WARN with the
> CPUIDLE_FLAG_TIMER_STOP flag set before queuing this patch and ensure it
> is not the tree hiding the forest.
Joseph, are you planning to post an updated series or respond to resolve
Daniel's question?
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/3] ARM: tegra114: cpuidle: add powered-down state
Date: Wed, 12 Jun 2013 11:41:28 -0600 [thread overview]
Message-ID: <51B8B2C8.1090006@wwwdotorg.org> (raw)
In-Reply-To: <51AE5EE3.3010607@linaro.org>
On 06/04/2013 03:40 PM, Daniel Lezcano wrote:
> On 06/04/2013 12:48 PM, Joseph Lo wrote:
>> This supports CPU core power down on each CPU when CPU idle. When CPU go
>> into this state, it saves it's context and needs a proper configuration
>> in flow controller to power gate the CPU when CPU runs into WFI
>> instruction. And the CPU also needs to set the IRQ as CPU power down idle
>> wake up event in flow controller.
>>
>> Signed-off-by: Joseph Lo <josephl@nvidia.com>
>
> I would like to understand why there is a WARN with the
> CPUIDLE_FLAG_TIMER_STOP flag set before queuing this patch and ensure it
> is not the tree hiding the forest.
Joseph, are you planning to post an updated series or respond to resolve
Daniel's question?
next prev parent reply other threads:[~2013-06-12 17:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 10:47 [PATCH V2 0/3] ARM: tegra114: cpuidle: add power down state Joseph Lo
2013-06-04 10:47 ` Joseph Lo
[not found] ` <1370342880-422-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-04 10:47 ` [PATCH V2 1/3] ARM: tegra114: Reprogram GIC CPU interface to bypass IRQ on CPU PM entry Joseph Lo
2013-06-04 10:47 ` Joseph Lo
2013-06-04 10:47 ` [PATCH V2 2/3] ARM: tegra114: add low level support for CPU idle powered-down mode Joseph Lo
2013-06-04 10:47 ` Joseph Lo
2013-06-04 10:48 ` [PATCH V2 3/3] ARM: tegra114: cpuidle: add powered-down state Joseph Lo
2013-06-04 10:48 ` Joseph Lo
[not found] ` <1370342880-422-4-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-04 21:40 ` Daniel Lezcano
2013-06-04 21:40 ` Daniel Lezcano
[not found] ` <51AE5EE3.3010607-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-06-12 17:41 ` Stephen Warren [this message]
2013-06-12 17:41 ` Stephen Warren
[not found] ` <51B8B2C8.1090006-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-13 2:13 ` Joseph Lo
2013-06-13 2:13 ` Joseph Lo
[not found] ` <1371089619.1681.21.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-06-13 9:30 ` Daniel Lezcano
2013-06-13 9:30 ` Daniel Lezcano
[not found] ` <51B99151.5010107-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-06-13 14:32 ` Joseph Lo
2013-06-13 14:32 ` Joseph Lo
[not found] ` <1371133960.1631.13.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-06-13 15:02 ` Daniel Lezcano
2013-06-13 15:02 ` Daniel Lezcano
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=51B8B2C8.1090006@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@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.