On Thu, 2013-08-08 at 09:53 +0100, Mark Rutland wrote:

On Wed, Aug 07, 2013 at 09:18:29PM +0100, Eduardo Valentin wrote:

quoted

Pawel, all,

On 06-08-2013 07:14, Pawel Moll wrote:

quoted

Apologies about the delay, I was "otherwise engaged" for a week...

I do also excuse for my delay, as I was also "engaged" for a week or so.

quoted

I hope you haven't lost all motivation to work on this subject, as it's
really worth the while!

Not really! quite the opposite. Although I was looking at some other
stuff, I got this series also tested on different boards and wrote down
a couple of improvements I will be working in the coming days. Indeed,
it is worth moving forward with this work.

quoted

On Fri, 2013-07-26 at 20:55 +0100, Eduardo Valentin wrote:

quoted

On 25-07-2013 13:33, Pawel Moll wrote:

quoted

On Thu, 2013-07-25 at 18:20 +0100, Eduardo Valentin wrote:

quoted

quoted

quoted

	thermal_zone {
		type = "CPU";

So what does this exactly mean? What is so special about CPU? What other
types you've got there? (Am I just lazy not looking at the numerous
links you provided? ;-)

Hehehe. OK. Type is supposed to describe what your zone is representing.

As in "a name"? So, for example "The board", "PSU"? What I meant to ask
was: does the string carry any meaning?

You haven't commended on this...

The string is supposed to carry meaning, yes. Couple of common used:
CPU, GPU, PCB, LCD

I think the point Pawel was getting at is that the string doesn't have a
*well-defined* meaning that always allows an OS to figure out the set of
relevant devices. If we have a thermal zone for "LCD", and have multiple
LCDs, which LCDs are covered? If we have a "PCB" zone, does this cover all
the devices attached to the PCB, a subset thereof, or the substrate of
the PCB itself?

Or: what happens if I type "lcd" instead of "LCD"? Would there be any
decision made based on this string? Or is it just a label to be used
somewhere in debugging messages?

Paweł