From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: linux@maxim.org.za, nicolas.ferre@atmel.com, plagnioj@jcrosoft.com
Cc: linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: [RFC PATCH 0/2] ARM: at91: cpuidle: encapsulate and move the driver to drivers/cpuidle
Date: Thu, 26 Sep 2013 18:06:05 +0200 [thread overview]
Message-ID: <1380211567-2972-1-git-send-email-daniel.lezcano@linaro.org> (raw)
Several patches were send to encapsulate the standby code.
Creating a platform driver model allows to finish to encapsulate this code more
and make possible to move the driver to the drivers/cpuidle directory.
I was not able to test the patchset, I don't have the hardware.
Daniel Lezcano (2):
ARM: at91: cpuidle: convert to platform driver
ARM: at91: cpuidle: Move driver to drivers/cpuidle
arch/arm/mach-at91/Makefile | 1 -
arch/arm/mach-at91/cpuidle.c | 68 ---------------------------------------
arch/arm/mach-at91/pm.c | 16 +++++++++-
drivers/cpuidle/Kconfig.arm | 6 ++++
drivers/cpuidle/Makefile | 1 +
drivers/cpuidle/cpuidle-at91.c | 69 ++++++++++++++++++++++++++++++++++++++++
6 files changed, 91 insertions(+), 70 deletions(-)
delete mode 100644 arch/arm/mach-at91/cpuidle.c
create mode 100644 drivers/cpuidle/cpuidle-at91.c
--
1.7.9.5
next reply other threads:[~2013-09-26 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 16:06 Daniel Lezcano [this message]
2013-09-26 16:06 ` [RFC PATCH 1/2] ARM: at91: cpuidle: convert to platform driver Daniel Lezcano
2013-09-26 16:06 ` [RFC PATCH 2/2] ARM: at91: cpuidle: Move driver to drivers/cpuidle Daniel Lezcano
2013-10-03 12:59 ` Bartlomiej Zolnierkiewicz
2013-10-02 13:01 ` [RFC PATCH 0/2] ARM: at91: cpuidle: encapsulate and move the " Daniel Lezcano
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=1380211567-2972-1-git-send-email-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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).