linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
	linux-pm@vger.kernel.org,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [PATCH 0/7] thermal: rcar: add interrupt and DT support
Date: Wed, 06 Feb 2013 13:48:17 +0800	[thread overview]
Message-ID: <1360129697.2982.29.camel@rzhang1-mobl4> (raw)
In-Reply-To: <87y5f9pvxv.wl%kuninori.morimoto.gx@renesas.com>

On Thu, 2013-01-31 at 01:02 -0800, Kuninori Morimoto wrote:
> Hi Zhang
> 
> These patches add interrupt and DT support to R-Car thermal sensor driver.
> There are 2 versions of R-Car thermal sensor (old/new),
> but the interrupt methods were different.
> 
> This patch adds interrupt support for NEW generation chip only,
> since the OLD generation interrupt controller had never been used before,
> and will never be used in the future.
> 
> But this driver is still keeping compatible for Old generation sensor without interrupt support
> 
> Kuninori Morimoto (7):
>       thermal: rcar: use parenthesis on macro
>       thermal: rcar: enable CPCTL to use hardware TSC deciding
>       thermal: rcar: use mutex lock instead of spin lock
>       thermal: rcar: multi channel support
>       thermal: rcar: add read/write functions for common/priv data
>       thermal: rcar: add interrupt support
>       thermal: rcar: add Device Tree support
> 
patch 1~6, and patch 8 applied to thermal -next.

thanks,
rui
>  .../devicetree/bindings/thermal/rcar-thermal.txt   |   29 ++
>  drivers/thermal/rcar_thermal.c                     |  437 ++++++++++++++------
>  2 files changed, 341 insertions(+), 125 deletions(-)



      parent reply	other threads:[~2013-02-06  5:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  9:02 [PATCH 0/7] thermal: rcar: add interrupt and DT support Kuninori Morimoto
2013-01-31  9:02 ` [PATCH 1/7] thermal: rcar: use parenthesis on macro Kuninori Morimoto
2013-01-31  9:03 ` [PATCH 2/7] thermal: rcar: enable CPCTL to use hardware TSC deciding Kuninori Morimoto
2013-01-31  9:03 ` [PATCH 3/7] thermal: rcar: use mutex lock instead of spin lock Kuninori Morimoto
2013-01-31  9:03 ` [PATCH 4/7] thermal: rcar: multi channel support Kuninori Morimoto
2013-01-31  9:03 ` [PATCH 5/7] thermal: rcar: add read/write functions for common/priv data Kuninori Morimoto
2013-01-31  9:04 ` [PATCH 6/7] thermal: rcar: add interrupt support Kuninori Morimoto
2013-01-31  9:05 ` [PATCH 7/7] thermal: rcar: add Device Tree support Kuninori Morimoto
2013-02-06  5:37   ` Zhang Rui
2013-02-06  8:30     ` Kuninori Morimoto
2013-02-06  8:36       ` Zhang Rui
2013-02-06  8:37         ` Kuninori Morimoto
2013-01-31  9:26 ` [PATCH 8/7] thermal: rcar: remove machine_power_off() from rcar_thermal_notify() Kuninori Morimoto
2013-02-06  5:48 ` Zhang Rui [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=1360129697.2982.29.camel@rzhang1-mobl4 \
    --to=rui.zhang@intel.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=magnus.damm@gmail.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).