From: Eduardo Valentin <edubezval@gmail.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Narendran Rajan <nrajan@codeaurora.org>,
Zhang Rui <rui.zhang@intel.com>,
Linux ARM MSM <linux-arm-msm@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Siddartha Mohanadoss <smohanad@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: [PATCH] thermal: Add msm tsens thermal sensor driver
Date: Sat, 31 Jan 2015 14:17:00 -0400 [thread overview]
Message-ID: <20150131181658.GA17425@developer.hsd1.ca.comcast.net> (raw)
In-Reply-To: <1422607148.11083.10.camel@mm-sol.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
On Fri, Jan 30, 2015 at 10:39:08AM +0200, Ivan T. Ivanov wrote:
>
> On Thu, 2015-01-29 at 18:39 -0400, Eduardo Valentin wrote:
> > On Mon, Jan 26, 2015 at 08:09:46PM -0800, Narendran Rajan wrote:
> > > TSENS supports reading temperature from multiple thermal
> > > sensors present in QCOM SOCs.
> > > TSENS HW is enabled only when the main sensor is requested.
> > > The TSENS block is disabled if the main senors is disabled
> > > irrespective of any other sensors that are being enabled.
> > > TSENS driver supports configurable threshold for temperature
> > > monitoring in which case it can generate an interrupt when specific
> > > thresholds are reached
> > >
> > > Based on code by Siddartha Mohanadoss and Stephen Boyd.
> > >
> > > Cc: Siddartha Mohanadoss <smohanad@codeaurora.org>
> > > Cc: Stephen Boyd <sboyd@codeaurora.org>
> > > Signed-off-by: Narendran Rajan <nrajan@codeaurora.org>
> >
> > I know this might not be completely related, but since you are sending
> > QCOM code, can you please check my comments on your PMIC thermal code?
> > https://patchwork.kernel.org/patch/5013021/
> >
> > Ivan seams to have disappeared.
>
>
>
> Mm no, sorry, just distracted by other tasks. PMIC thermal driver is in the
> road map. I will try to accelerate rework.
Great news Ivan!
Let me know if you have doubts or need any support / extension on the OF
thermal API in order to get the PMIC thermal properly implemented.
>
> Regards,
> Ivan
Eduardo Valentin
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-31 18:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 4:09 [PATCH] thermal: Add msm tsens thermal sensor driver Narendran Rajan
2015-01-27 7:15 ` Srinivas Kandagatla
2015-01-27 22:31 ` Narendran Rajan
2015-01-28 23:52 ` 'Stephen Boyd'
2015-01-29 22:53 ` Eduardo Valentin
2015-01-30 0:55 ` Narendran Rajan
2015-01-29 6:05 ` Srinivas Kandagatla
2015-01-30 0:52 ` Narendran Rajan
2015-01-27 16:03 ` Lina Iyer
2015-01-28 0:55 ` Narendran Rajan
2015-01-28 1:18 ` Lina Iyer
2015-01-28 17:01 ` Lina Iyer
2015-01-30 1:06 ` Narendran Rajan
2015-01-29 1:46 ` Stephen Boyd
2015-01-30 1:36 ` Narendran Rajan
2015-01-29 22:39 ` Eduardo Valentin
2015-01-30 8:39 ` Ivan T. Ivanov
2015-01-31 18:17 ` Eduardo Valentin [this message]
2015-01-29 22:49 ` Eduardo Valentin
2015-01-30 1:42 ` Narendran Rajan
2015-01-31 18:23 ` Eduardo Valentin
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=20150131181658.GA17425@developer.hsd1.ca.comcast.net \
--to=edubezval@gmail.com \
--cc=iivanov@mm-sol.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nrajan@codeaurora.org \
--cc=rui.zhang@intel.com \
--cc=sboyd@codeaurora.org \
--cc=smohanad@codeaurora.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).