From: Jisheng Zhang <jszhang@marvell.com>
To: <daniel.lezcano@linaro.org>, <lorenzo.pieralisi@arm.com>,
<lina.iyer@linaro.org>, <linux@armlinux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Jisheng Zhang <jszhang@marvell.com>
Subject: [PATCH v4 0/2] make arm_cpuidle_suspend() a bit more efficient
Date: Wed, 6 Jul 2016 14:15:53 +0800 [thread overview]
Message-ID: <1467785755-3488-1-git-send-email-jszhang@marvell.com> (raw)
There's one corner case need to be fixed: !cpuidle_ops[cpu].init.
patch1 tries to address this corner case.
patch2 tries to improve arm_cpuidle_suspend() a bit by moving .suspend
check into arm_cpuidle_read_ops().
Since v3:
- rebased on 4.7-rc1
Since v2:
- add back patch1.
Since v1:
- drop patch1, I.E "ARM: cpuidle: fix !cpuidle_ops[cpu].init case
during init", because there may be platforms which doesn't need the
init member at all.
- adopt Daniel's suggestion to move the cpuidle_ops.suspend check to
arm_cpuidle_read_ops().
Jisheng Zhang (2):
ARM: cpuidle: fix !cpuidle_ops[cpu].init case during init
ARM: cpuidle: make arm_cpuidle_suspend() a bit more efficient
arch/arm/kernel/cpuidle.c | 23 +++++++++++++----------
1 file changed, 13 insertions(+), 10 deletions(-)
--
2.8.1
next reply other threads:[~2016-07-06 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 6:15 Jisheng Zhang [this message]
2016-07-06 6:15 ` [PATCH v4 1/2] ARM: cpuidle: fix !cpuidle_ops[cpu].init case during init Jisheng Zhang
2016-07-07 13:45 ` Daniel Lezcano
2016-07-06 6:15 ` [PATCH v4 2/2] ARM: cpuidle: make arm_cpuidle_suspend() a bit more efficient Jisheng Zhang
2016-07-07 13:46 ` Daniel Lezcano
2016-07-08 6:17 ` Jisheng Zhang
2016-07-08 10:50 ` Daniel Lezcano
2016-07-08 10:58 ` Jisheng Zhang
2016-07-14 15:31 ` Russell King - ARM Linux
2016-07-15 7:38 ` 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=1467785755-3488-1-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.com \
--cc=daniel.lezcano@linaro.org \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
/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).