From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Colin Cross <ccross@android.com>
Cc: Kevin Hilman <khilman@ti.com>, Len Brown <len.brown@intel.com>,
Russell King <linux@arm.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org,
Amit Kucheria <amit.kucheria@linaro.org>,
linux-pm@lists.linux-foundation.org,
Arjan van de Ven <arjan@linux.intel.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 0/4] coupled cpuidle state support
Date: Fri, 18 May 2012 16:06:01 +0530 [thread overview]
Message-ID: <4FB62611.7080908@ti.com> (raw)
In-Reply-To: <1336438662-10484-1-git-send-email-ccross@android.com>
On Tuesday 08 May 2012 06:27 AM, Colin Cross wrote:
> On some ARM SMP SoCs (OMAP4460, Tegra 2, and probably more), the
> cpus cannot be independently powered down, either due to
> sequencing restrictions (on Tegra 2, cpu 0 must be the last to
> power down), or due to HW bugs (on OMAP4460, a cpu powering up
> will corrupt the gic state unless the other cpu runs a work
> around). Each cpu has a power state that it can enter without
> coordinating with the other cpu (usually Wait For Interrupt, or
> WFI), and one or more "coupled" power states that affect blocks
> shared between the cpus (L2 cache, interrupt controller, and
> sometimes the whole SoC). Entering a coupled power state must
> be tightly controlled on both cpus.
>
[...]
> This series has been tested and reviewed by Santosh and Kevin
> for OMAP4, which has a cpuidle series ready for 3.5, and Tegra
> and Exynos5 patches are in progress. I think this is ready to
> go in. Lean, are you maintaining a cpuidle tree for linux-next?
> If not, I can publish a tree for linux-next, or this could go in
> through Arnd's tree.
I haven't seen any response so far on who is lining up this
series for 3.5 ? Not sure if it made it to linux-next either.
Regards
santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/4] coupled cpuidle state support
Date: Fri, 18 May 2012 16:06:01 +0530 [thread overview]
Message-ID: <4FB62611.7080908@ti.com> (raw)
In-Reply-To: <1336438662-10484-1-git-send-email-ccross@android.com>
On Tuesday 08 May 2012 06:27 AM, Colin Cross wrote:
> On some ARM SMP SoCs (OMAP4460, Tegra 2, and probably more), the
> cpus cannot be independently powered down, either due to
> sequencing restrictions (on Tegra 2, cpu 0 must be the last to
> power down), or due to HW bugs (on OMAP4460, a cpu powering up
> will corrupt the gic state unless the other cpu runs a work
> around). Each cpu has a power state that it can enter without
> coordinating with the other cpu (usually Wait For Interrupt, or
> WFI), and one or more "coupled" power states that affect blocks
> shared between the cpus (L2 cache, interrupt controller, and
> sometimes the whole SoC). Entering a coupled power state must
> be tightly controlled on both cpus.
>
[...]
> This series has been tested and reviewed by Santosh and Kevin
> for OMAP4, which has a cpuidle series ready for 3.5, and Tegra
> and Exynos5 patches are in progress. I think this is ready to
> go in. Lean, are you maintaining a cpuidle tree for linux-next?
> If not, I can publish a tree for linux-next, or this could go in
> through Arnd's tree.
I haven't seen any response so far on who is lining up this
series for 3.5 ? Not sure if it made it to linux-next either.
Regards
santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Colin Cross <ccross@android.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-pm@lists.linux-foundation.org,
Kevin Hilman <khilman@ti.com>, Len Brown <len.brown@intel.com>,
Trinabh Gupta <g.trinabh@gmail.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kay Sievers <kay.sievers@vrfy.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCHv3 0/4] coupled cpuidle state support
Date: Fri, 18 May 2012 16:06:01 +0530 [thread overview]
Message-ID: <4FB62611.7080908@ti.com> (raw)
In-Reply-To: <1336438662-10484-1-git-send-email-ccross@android.com>
On Tuesday 08 May 2012 06:27 AM, Colin Cross wrote:
> On some ARM SMP SoCs (OMAP4460, Tegra 2, and probably more), the
> cpus cannot be independently powered down, either due to
> sequencing restrictions (on Tegra 2, cpu 0 must be the last to
> power down), or due to HW bugs (on OMAP4460, a cpu powering up
> will corrupt the gic state unless the other cpu runs a work
> around). Each cpu has a power state that it can enter without
> coordinating with the other cpu (usually Wait For Interrupt, or
> WFI), and one or more "coupled" power states that affect blocks
> shared between the cpus (L2 cache, interrupt controller, and
> sometimes the whole SoC). Entering a coupled power state must
> be tightly controlled on both cpus.
>
[...]
> This series has been tested and reviewed by Santosh and Kevin
> for OMAP4, which has a cpuidle series ready for 3.5, and Tegra
> and Exynos5 patches are in progress. I think this is ready to
> go in. Lean, are you maintaining a cpuidle tree for linux-next?
> If not, I can publish a tree for linux-next, or this could go in
> through Arnd's tree.
I haven't seen any response so far on who is lining up this
series for 3.5 ? Not sure if it made it to linux-next either.
Regards
santosh
next prev parent reply other threads:[~2012-05-18 10:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 0:57 [PATCHv3 0/4] coupled cpuidle state support Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-08 0:57 ` [PATCHv4 1/4] cpuidle: refactor out cpuidle_enter_state Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-09 21:03 ` Rafael J. Wysocki
2012-05-09 21:03 ` Rafael J. Wysocki
2012-05-09 21:03 ` Rafael J. Wysocki
2012-05-08 0:57 ` [PATCHv4 2/4] cpuidle: fix error handling in __cpuidle_register_device Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-09 21:04 ` Rafael J. Wysocki
2012-05-09 21:04 ` Rafael J. Wysocki
2012-05-09 21:04 ` Rafael J. Wysocki
2012-05-08 0:57 ` [PATCHv4 3/4] cpuidle: add support for states that affect multiple cpus Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-09 21:19 ` Rafael J. Wysocki
2012-05-09 21:19 ` Rafael J. Wysocki
2012-05-09 21:19 ` Rafael J. Wysocki
2012-05-08 0:57 ` [PATCHv4 4/4] cpuidle: coupled: add parallel barrier function Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-08 0:57 ` Colin Cross
2012-05-09 21:31 ` Rafael J. Wysocki
2012-05-09 21:31 ` Rafael J. Wysocki
2012-05-09 21:31 ` Rafael J. Wysocki
2012-05-10 22:47 ` Colin Cross
2012-05-10 22:47 ` Colin Cross
2012-05-10 22:47 ` Colin Cross
2012-05-11 18:32 ` Rafael J. Wysocki
2012-05-11 18:32 ` Rafael J. Wysocki
2012-05-11 18:32 ` Rafael J. Wysocki
2012-05-18 10:36 ` Santosh Shilimkar [this message]
2012-05-18 10:36 ` [PATCHv3 0/4] coupled cpuidle state support Santosh Shilimkar
2012-05-18 10:36 ` Santosh Shilimkar
2012-05-18 19:03 ` Rafael J. Wysocki
2012-05-18 19:03 ` Rafael J. Wysocki
2012-05-18 19:03 ` Rafael J. Wysocki
2012-05-18 20:18 ` Colin Cross
2012-05-18 20:18 ` Colin Cross
2012-05-18 20:18 ` Colin Cross
2012-05-19 7:04 ` Shilimkar, Santosh
2012-05-19 7:04 ` Shilimkar, Santosh
2012-05-19 7:04 ` Shilimkar, Santosh
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=4FB62611.7080908@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=amit.kucheria@linaro.org \
--cc=arjan@linux.intel.com \
--cc=arnd.bergmann@linaro.org \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kay.sievers@vrfy.org \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux@arm.linux.org.uk \
/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.