From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 4/8] arm64: kernel: introduce cpu_init_idle CPU operation
Date: Mon, 18 Aug 2014 15:21:06 +0100 [thread overview]
Message-ID: <20140818142106.GE20043@localhost> (raw)
In-Reply-To: <1407945127-27554-5-git-send-email-lorenzo.pieralisi@arm.com>
On Wed, Aug 13, 2014 at 04:52:03PM +0100, Lorenzo Pieralisi wrote:
> The CPUidle subsystem on ARM64 machines requires the idle states
> implementation back-end to initialize idle states parameter upon
> boot. This patch adds a hook in the CPU operations structure that
> should be initialized by the CPU operations back-end in order to
> provide a function that initializes cpu idle states.
>
> This patch also adds the infrastructure to arm64 kernel required
> to export the CPU operations based initialization interface, so
> that drivers (ie CPUidle) can use it when they are initialized
> at probe time.
>
> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> ---
> arch/arm64/include/asm/cpu_ops.h | 3 +++
> arch/arm64/include/asm/cpuidle.h | 13 +++++++++++++
> arch/arm64/kernel/Makefile | 1 +
> arch/arm64/kernel/cpuidle.c | 29 +++++++++++++++++++++++++++++
> 4 files changed, 46 insertions(+)
> create mode 100644 arch/arm64/include/asm/cpuidle.h
> create mode 100644 arch/arm64/kernel/cpuidle.c
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2014-08-18 14:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:51 [PATCH v7 0/8] ARM generic idle states Lorenzo Pieralisi
2014-08-13 15:52 ` [PATCH v7 1/8] arm64: kernel: refactor the CPU suspend API for retention states Lorenzo Pieralisi
2014-08-18 7:47 ` Hanjun Guo
2014-08-18 14:20 ` Catalin Marinas
2014-08-13 15:52 ` [PATCH v7 2/8] Documentation: arm: define DT idle states bindings Lorenzo Pieralisi
2014-08-13 19:25 ` Lina Iyer
2014-08-13 22:11 ` Lorenzo Pieralisi
2014-08-15 17:20 ` Lina Iyer
2014-08-15 17:51 ` Lorenzo Pieralisi
2014-08-18 14:20 ` Catalin Marinas
2014-08-13 15:52 ` [PATCH v7 3/8] drivers: cpuidle: implement DT based idle states infrastructure Lorenzo Pieralisi
2014-08-13 16:31 ` Nicolas Pitre
2014-08-13 17:04 ` Lorenzo Pieralisi
2014-08-13 17:29 ` Nicolas Pitre
2014-08-14 11:29 ` Lorenzo Pieralisi
2014-08-14 15:47 ` Nicolas Pitre
2014-08-14 16:02 ` Lorenzo Pieralisi
2014-08-18 14:21 ` Catalin Marinas
2014-08-13 15:52 ` [PATCH v7 4/8] arm64: kernel: introduce cpu_init_idle CPU operation Lorenzo Pieralisi
2014-08-18 14:21 ` Catalin Marinas [this message]
2014-08-13 15:52 ` [PATCH v7 5/8] arm64: add PSCI CPU_SUSPEND based cpu_suspend support Lorenzo Pieralisi
2014-08-18 14:21 ` Catalin Marinas
2014-08-13 15:52 ` [PATCH v7 6/8] drivers: cpuidle: CPU idle ARM64 driver Lorenzo Pieralisi
2014-08-18 14:21 ` Catalin Marinas
2014-08-18 22:30 ` Lorenzo Pieralisi
2014-08-18 14:21 ` Catalin Marinas
2014-08-18 22:25 ` Lorenzo Pieralisi
2014-08-13 15:52 ` [PATCH v7 7/8] drivers: cpuidle: initialize big.LITTLE driver through DT Lorenzo Pieralisi
2014-08-18 14:21 ` Catalin Marinas
2014-08-13 15:52 ` [PATCH v7 8/8] drivers: cpuidle: initialize Exynos " Lorenzo Pieralisi
2014-08-15 21:12 ` Lina Iyer
2014-08-15 21:40 ` Lorenzo Pieralisi
2014-08-15 21:45 ` Lina Iyer
2014-08-15 21:52 ` Lorenzo Pieralisi
2014-08-18 14:22 ` Catalin Marinas
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=20140818142106.GE20043@localhost \
--to=catalin.marinas@arm.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).