All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Durgadoss R <durgadoss.r@intel.com>,
	"Zhang, Rui" <rui.zhang@intel.com>, Wei Ni <wni@nvidia.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RFC: device thermal limits represented in device tree nodes
Date: Thu, 25 Jul 2013 17:38:14 +0100	[thread overview]
Message-ID: <1374770294.3213.35.camel@hornet> (raw)
In-Reply-To: <1374768928.3213.31.camel@hornet>

On Thu, 2013-07-25 at 17:15 +0100, Pawel Moll wrote:
> > Another way, as I mentioned in the original RFC, an option would be to
> > have the thermal_zone node not embedded in any device node. But them, we
> > would need to firmly link it to other device nodes, to describe what is
> > monitored and what is used for monitoring. 
> 
> You mean the zone nodes would live at the top level of the tree? To my
> mind the root represents the device (the board, whatever you call it),

What I wanted to say was: ... so the zone would still be embedded in a
device node :-)

Pawel

WARNING: multiple messages have this Message-ID (diff)
From: Pawel Moll <pawel.moll@arm.com>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Durgadoss R <durgadoss.r@intel.com>,
	"Zhang, Rui" <rui.zhang@intel.com>, Wei Ni <wni@nvidia.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] RFC: device thermal limits represented in device tree nodes
Date: Thu, 25 Jul 2013 16:38:14 +0000	[thread overview]
Message-ID: <1374770294.3213.35.camel@hornet> (raw)
In-Reply-To: <1374768928.3213.31.camel@hornet>

On Thu, 2013-07-25 at 17:15 +0100, Pawel Moll wrote:
> > Another way, as I mentioned in the original RFC, an option would be to
> > have the thermal_zone node not embedded in any device node. But them, we
> > would need to firmly link it to other device nodes, to describe what is
> > monitored and what is used for monitoring. 
> 
> You mean the zone nodes would live at the top level of the tree? To my
> mind the root represents the device (the board, whatever you call it),

What I wanted to say was: ... so the zone would still be embedded in a
device node :-)

Pawel



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2013-07-25 16:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 14:25 RFC: device thermal limits represented in device tree nodes Eduardo Valentin
2013-07-22 14:25 ` Eduardo Valentin
2013-07-22 14:25 ` [lm-sensors] " Eduardo Valentin
2013-07-24  1:44 ` Stephen Warren
2013-07-24  1:44   ` [lm-sensors] " Stephen Warren
2013-07-24 10:45   ` Mark Rutland
2013-07-24 10:45     ` [lm-sensors] " Mark Rutland
2013-07-24 13:29     ` Eduardo Valentin
2013-07-24 13:29       ` Eduardo Valentin
2013-07-24 13:29       ` [lm-sensors] " Eduardo Valentin
2013-07-24 11:19   ` Pawel Moll
2013-07-24 11:19     ` [lm-sensors] " Pawel Moll
2013-07-24 15:04     ` Eduardo Valentin
2013-07-24 15:04       ` [lm-sensors] " Eduardo Valentin
2013-07-25 16:15       ` Pawel Moll
2013-07-25 16:15         ` [lm-sensors] " Pawel Moll
2013-07-25 16:38         ` Pawel Moll [this message]
2013-07-25 16:38           ` Pawel Moll
2013-07-25 17:21           ` Eduardo Valentin
2013-07-25 17:21             ` [lm-sensors] " Eduardo Valentin
2013-07-25 17:20         ` Eduardo Valentin
2013-07-25 17:20           ` [lm-sensors] " Eduardo Valentin
2013-07-25 17:33           ` Pawel Moll
2013-07-25 17:33             ` [lm-sensors] " Pawel Moll
2013-07-26 19:55             ` Eduardo Valentin
2013-07-26 19:55               ` [lm-sensors] " Eduardo Valentin
2013-08-06 11:14               ` Pawel Moll
2013-08-06 11:14                 ` [lm-sensors] " Pawel Moll
2013-08-07 20:18                 ` Eduardo Valentin
2013-08-07 20:18                   ` [lm-sensors] " Eduardo Valentin
2013-08-08  8:53                   ` Mark Rutland
2013-08-08  8:53                     ` [lm-sensors] " Mark Rutland
2013-08-08 13:45                     ` Pawel Moll
2013-08-08 13:45                       ` [lm-sensors] " Pawel Moll
2013-07-24 13:24   ` Eduardo Valentin
2013-07-24 13:24     ` Eduardo Valentin
2013-07-24 13:24     ` Eduardo Valentin
2013-07-24 13:24     ` [lm-sensors] " Eduardo Valentin
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 14:19 Eduardo Valentin
2013-07-22 14:19 ` Eduardo Valentin
2013-07-22 14:19 ` [lm-sensors] " 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=1374770294.3213.35.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=durgadoss.r@intel.com \
    --cc=eduardo.valentin@ti.com \
    --cc=grant.likely@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=rob.herring@calxeda.com \
    --cc=rui.zhang@intel.com \
    --cc=swarren@wwwdotorg.org \
    --cc=wni@nvidia.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.