From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm: kernel: implement cpuidle_ops with psci backend
Date: Wed, 8 Jul 2015 20:51:06 +0800 [thread overview]
Message-ID: <1436359868-6176-1-git-send-email-jszhang@marvell.com> (raw)
We'd like to use cpuidle-arm.c for both arm and arm64 with psci as backend.
For arm64, it works. But for arm, we miss cpuidle_ops, these patches try to
address this issue.
Has been tested on Marvell Berlin SoCs. These patches are rebased on the Mark
Rutland's latest psci unification work and Lorenzo Pieralisi's psci related
work[1].
[PATCH 1/2] move psci's cpu_suspend handling to generic code as suggested
by Lorenzo.
[PATCH 2/2] implement cpuidle_ops with psci finally.
Since v1:
- add a new file psci_cpuidle.c to implment cpuidle_ops
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-May/347352.html
Jisheng Zhang (2):
firmware: psci: move cpu_suspend handling to generic code
arm: kernel: implement cpuidle_ops with psci backend
arch/arm/kernel/Makefile | 1 +
arch/arm/kernel/psci_cpuidle.c | 29 +++++++++++++
arch/arm64/kernel/psci.c | 95 ------------------------------------------
drivers/firmware/psci.c | 95 ++++++++++++++++++++++++++++++++++++++++++
include/linux/psci.h | 2 +
5 files changed, 127 insertions(+), 95 deletions(-)
create mode 100644 arch/arm/kernel/psci_cpuidle.c
--
2.1.4
next reply other threads:[~2015-07-08 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:51 Jisheng Zhang [this message]
2015-07-08 12:51 ` [PATCH v2 1/2] firmware: psci: move cpu_suspend handling to generic code Jisheng Zhang
2015-07-08 17:32 ` Lorenzo Pieralisi
2015-07-08 12:51 ` [PATCH v2 2/2] arm: kernel: implement cpuidle_ops with psci backend Jisheng Zhang
2015-07-08 17:34 ` Lorenzo Pieralisi
2015-07-09 6:35 ` Jisheng Zhang
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=1436359868-6176-1-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.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).