linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: Robert Lee <rob.lee@linaro.org>
Cc: kernel@pengutronix.de, amit.kucheria@linaro.org,
	daniel.lezcano@linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
	patches@linaro.org, jj@chaosbits.net
Subject: Re: [PATCH v2 0/3] Add imx cpuidle
Date: Wed, 2 May 2012 11:03:39 +0800	[thread overview]
Message-ID: <20120502030337.GS2194@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1335924760-796-1-git-send-email-rob.lee@linaro.org>

On Tue, May 01, 2012 at 09:12:37PM -0500, Robert Lee wrote:
> Add common imx cpuidle initialization functionality and add a i.MX5 and i.MX6Q
> platform cpuidle implementation.
> 
> Based on v3.4-rc5 plus recently submitted device tree late_initcall patch:

Just to clarify, this is not a device tree late_initcall but a machine
specific late_initcall time hook.  It has nothing to do with device
tree.

Regards,
Shawn

>  http://www.spinics.net/lists/arm-kernel/msg171620.html
> 
> Changes since v1:
>  * Removed some unnecessary  spaces
>  * Added return value for an error message
>  * Reworked init scheme to use device tree late_initcall.
>  * Moved imx6q and imx5 cpuidle functionality to existing files.
> 
> Robert Lee (3):
>   ARM: imx: Add common imx cpuidle init functionality.
>   ARM: imx: Add imx5 cpuidle driver
>   ARM: imx: Add imx6q cpuidle driver
> 
>  arch/arm/mach-imx/cpuidle-imx6q.c        |   33 ++++++++++++
>  arch/arm/mach-imx/mach-imx6q.c           |   18 +++++++
>  arch/arm/mach-imx/mm-imx5.c              |   42 ++++++++++++++--
>  arch/arm/plat-mxc/Makefile               |    1 +
>  arch/arm/plat-mxc/cpuidle.c              |   80 ++++++++++++++++++++++++++++++
>  arch/arm/plat-mxc/include/mach/cpuidle.h |   22 ++++++++
>  6 files changed, 193 insertions(+), 3 deletions(-)
>  create mode 100644 arch/arm/mach-imx/cpuidle-imx6q.c
>  create mode 100644 arch/arm/plat-mxc/cpuidle.c
>  create mode 100644 arch/arm/plat-mxc/include/mach/cpuidle.h
> 
> -- 
> 1.7.10
> 

      parent reply	other threads:[~2012-05-02  3:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  2:12 [PATCH v2 0/3] Add imx cpuidle Robert Lee
2012-05-02  2:12 ` [PATCH v2 1/3] ARM: imx: Add common imx cpuidle init functionality Robert Lee
2012-05-02  3:13   ` Shawn Guo
2012-05-02 13:59     ` Rob Lee
2012-05-02 14:07       ` Shawn Guo
2012-05-02 14:09         ` Rob Lee
2012-05-02  7:27   ` Sascha Hauer
2012-05-02 19:16     ` Rob Lee
2012-05-02 20:21       ` Sascha Hauer
2012-05-02  2:12 ` [PATCH v2 2/3] ARM: imx: Add imx5 cpuidle driver Robert Lee
2012-05-02  7:33   ` Sascha Hauer
2012-05-02 20:11     ` Rob Lee
2012-05-03  6:39       ` Sascha Hauer
2012-05-02  2:12 ` [PATCH v2 3/3] ARM: imx: Add imx6q " Robert Lee
2012-05-02  3:23   ` Shawn Guo
2012-05-02 13:50     ` Rob Lee
2012-05-02 13:53       ` Shawn Guo
2012-05-02  3:03 ` Shawn Guo [this message]

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=20120502030337.GS2194@S2101-09.ap.freescale.net \
    --to=shawn.guo@linaro.org \
    --cc=amit.kucheria@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=jj@chaosbits.net \
    --cc=kernel@pengutronix.de \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rob.lee@linaro.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).