All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Javi Merino <javi.merino@arm.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	rui.zang@intel.com, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH v3 1/4] thermal: Add support for hierarchical thermal zones
Date: Wed, 2 Mar 2016 19:23:27 -0800	[thread overview]
Message-ID: <20160303032326.GE3379@localhost.localdomain> (raw)
In-Reply-To: <20160303031244.GA3379@localhost.localdomain>

On Wed, Mar 02, 2016 at 07:12:46PM -0800, Eduardo Valentin wrote:
> 
> Thanks for moving this forward Javi,
> 
> Few comments inline.
> 
> On Wed, Nov 25, 2015 at 03:09:43PM +0000, Javi Merino wrote:
> > Add the ability to stack thermal zones on top of each other, creating a
> > hierarchy of thermal zones.

> > +
> > +	if (!tz->ops->get_temp) {
> > +		ret = get_subtz_temp(tz, temp);
> > +		goto unlock;
> > +	}

In fact, if we follow the semantics in DT, we should allow both,
regular sensors (.get_temp) and subtzs.

  reply	other threads:[~2016-03-03  3:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 15:09 [PATCH v3 0/4] Hierarchical thermal zones Javi Merino
2015-11-25 15:09 ` [PATCH v3 1/4] thermal: Add support for hierarchical " Javi Merino
2016-03-03  3:12   ` Eduardo Valentin
2016-03-03  3:23     ` Eduardo Valentin [this message]
2015-11-25 15:09 ` [PATCH v3 2/4] devicetree: bindings: let thermal-sensor point to other " Javi Merino
2015-11-25 17:54   ` Mark Rutland
2015-11-25 18:41     ` Javi Merino
2015-11-25 18:41       ` Javi Merino
2016-01-04 14:17   ` Sascha Hauer
2016-03-03  3:21     ` Eduardo Valentin
2016-03-21 11:55       ` Javi Merino
2016-03-22 15:13         ` Eduardo Valentin
2016-03-22 15:13           ` Eduardo Valentin
2016-03-03  3:19   ` Eduardo Valentin
2015-11-25 15:09 ` [PATCH v3 3/4] thermal: of: parse stacked thermal zones from device tree Javi Merino
2015-11-25 15:09 ` [PATCH v3 4/4] thermal: show the sub thermal zones in sysfs Javi Merino
2016-03-03  3:17   ` Eduardo Valentin
2016-03-16 22:06   ` 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=20160303032326.GE3379@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=javi.merino@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zang@intel.com \
    --cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.