From: josephl@nvidia.com (Joseph Lo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/6] ARM: tegra20: cpuidle: add power-down state
Date: Wed, 5 Dec 2012 18:01:47 +0800 [thread overview]
Message-ID: <1354701715-24150-1-git-send-email-josephl@nvidia.com> (raw)
This adds a "powered-down" state in cpuidle for Tegra20. It requires power
gating both CPU cores. When the CPU1 requests to enter "powered-down"
state, it saves its own state and then enters WFI. When the CPU0 requests
the same state, it attempts to put the CPU1 into reset to prevent it from
waking up. Then power down both CPUs together and turn off the CPU rail.
If the CPU1 be woken up before CPU0 entering powered-down state, then it
needs to restore it's CPU state and waits for next chance.
V2:
* add a new patch for checking if there is any pending SGI
* if there is a SGI pending for the CPU, then we will abort the
"powered-down" idle for the both CPUs that already in coupled state
Verified on Seaboard(Tegra20) and Cardhu(Tegra30).
Joseph Lo (6):
ARM: tegra: add pending SGI checking API
ARM: tegra20: cpuidle: add powered-down state for secondary CPU
ARM: tegra20: clocks: add CPU low-power function into
tegra_cpu_car_ops
ARM: tegra20: flowctrl: add support for cpu_suspend_enter/exit
ARM: tegra20: cpuidle: add powered-down state for CPU0
ARM: tegra20: cpuidle: apply coupled cpuidle for powered-down mode
arch/arm/mach-tegra/Kconfig | 1 +
arch/arm/mach-tegra/cpuidle-tegra20.c | 191 +++++++++++++++++++++++++++++++
arch/arm/mach-tegra/flowctrl.c | 38 ++++++-
arch/arm/mach-tegra/flowctrl.h | 4 +
arch/arm/mach-tegra/irq.c | 17 +++-
arch/arm/mach-tegra/irq.h | 22 ++++
arch/arm/mach-tegra/pm.c | 2 +
arch/arm/mach-tegra/sleep-tegra20.S | 198 +++++++++++++++++++++++++++++++++
arch/arm/mach-tegra/sleep.S | 19 +++
arch/arm/mach-tegra/sleep.h | 26 +++++
arch/arm/mach-tegra/tegra20_clocks.c | 99 ++++++++++++++++
11 files changed, 610 insertions(+), 7 deletions(-)
create mode 100644 arch/arm/mach-tegra/irq.h
next reply other threads:[~2012-12-05 10:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 10:01 Joseph Lo [this message]
2012-12-05 10:01 ` [PATCH V2 1/6] ARM: tegra: add pending SGI checking API Joseph Lo
2012-12-05 22:09 ` Stephen Warren
2012-12-06 7:04 ` Joseph Lo
2012-12-06 18:52 ` Stephen Warren
2012-12-05 10:01 ` [PATCH V2 2/6] ARM: tegra20: cpuidle: add powered-down state for secondary CPU Joseph Lo
2012-12-05 10:50 ` Lorenzo Pieralisi
2012-12-06 8:25 ` Joseph Lo
2012-12-06 18:56 ` Stephen Warren
2013-01-11 7:20 ` Joseph Lo
2013-01-11 12:24 ` Lorenzo Pieralisi
2013-01-15 3:00 ` Joseph Lo
2013-01-15 11:34 ` Lorenzo Pieralisi
2013-01-16 3:17 ` Joseph Lo
2013-01-12 17:33 ` Nicolas Pitre
2012-12-05 22:18 ` Stephen Warren
2012-12-06 7:22 ` Joseph Lo
2012-12-06 18:59 ` Stephen Warren
2012-12-05 10:01 ` [PATCH V2 3/6] ARM: tegra20: clocks: add CPU low-power function into tegra_cpu_car_ops Joseph Lo
2012-12-05 10:01 ` [PATCH V2 4/6] ARM: tegra20: flowctrl: add support for cpu_suspend_enter/exit Joseph Lo
2012-12-05 10:01 ` [PATCH V2 5/6] ARM: tegra20: cpuidle: add powered-down state for CPU0 Joseph Lo
2012-12-05 10:01 ` [PATCH V2 6/6] ARM: tegra20: cpuidle: apply coupled cpuidle for powered-down mode Joseph Lo
2012-12-05 10:01 ` Joseph Lo
2012-12-05 10:10 ` Joseph Lo
2012-12-06 11:03 ` Grant Likely
2012-12-05 10:01 ` Joseph Lo
2012-12-05 10:11 ` 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=1354701715-24150-1-git-send-email-josephl@nvidia.com \
--to=josephl@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).