From: Javi Merino <javi.merino@arm.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Rui Zhang <rui.zhang@intel.com>,
"ezequiel.garcia@free-electrons.com"
<ezequiel.garcia@free-electrons.com>,
"amit.kachhap@linaro.org" <amit.kachhap@linaro.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"amit.daniel@samsung.com" <amit.daniel@samsung.com>,
"hongbo.zhang@linaro.com" <hongbo.zhang@linaro.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"peter@piie.net" <peter@piie.net>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"aaron.lu@intel.com" <aaron.lu@intel.com>,
"caesar.wang@rock-chips.com" <caesar.wang@rock-chips.com>,
"b.zolnierkie@samsung.com" <b.zolnierkie@samsung.com>,
"l.majewski@samsung.com" <l.majewski@samsung.com>,
"vincenzo.frascino@st.com" <vincenzo.frascino@st.com>,
"mperttunen@nvidia.com" <mperttunen@nvidia.com>,
"mikko.perttunen@kapsi.fi" <mikko.perttunen@kapsi.fi>,
srinivas.pandruvada@lin
Subject: Re: [PATCH RFC 02/12] Documentation: thermal docbook: add glossary
Date: Wed, 18 Feb 2015 11:52:21 +0000 [thread overview]
Message-ID: <20150218115221.GD2990@e104805> (raw)
In-Reply-To: <1423517653-11359-3-git-send-email-edubezval@gmail.com>
Hi Eduardo,
On Mon, Feb 09, 2015 at 09:34:03PM +0000, Eduardo Valentin wrote:
> This change introduces a section in the Introduction Chapter to
> list concepts used by the Thermal Framework.
>
> Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
> ---
> Documentation/DocBook/thermal.tmpl | 129 ++++++++++++++++++++++++++++++++++++-
> 1 file changed, 128 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/DocBook/thermal.tmpl b/Documentation/DocBook/thermal.tmpl
> index f8fb8a2..66efed3 100644
> --- a/Documentation/DocBook/thermal.tmpl
> +++ b/Documentation/DocBook/thermal.tmpl
> @@ -84,5 +84,132 @@
> devices.
> </para>
>
> - </chapter>
> + <sect1 id="glossary">
> + <title>Glossary</title>
> + <para>The Linux Kernel Thermal Framework uses a
> + specific terminology to represent the entities involved
> + in thermal constrained environments. This section
> + summaries the terminology as dictionary. These terms are
> + in use within the present document and in the source
> + code of the Linux Kernel Thermal Framework.
> + </para>
> + <glossary>
> + <glossentry>
> + <glossterm>Thermal Zone</glossterm>
> + <glossdef>
> + <para>Thermal zones represent
> + what is the current status of a
> + thermal constrained zone in the
> + hardware. The zone usually is a
> + device or component. The status
> + of a thermal zone is mainly with
> + respect to temperature.
> + Currently, the Linux Kernel
> + Thermal Framework represents
> + temperature in miliCelsius. The
> + current abstraction covers for
> + non negative temperatures and
> + constraints.
> + </para>
Shall we point out that a thermal zone doesn't necessarily imply a
thermal sensor? I find it very common to assume that if you have 10
sensors, you should have 10 thermal zones. From my point of view, a
thermal zone is an area that has similar thermal characteristics.
Therefore, the temperature of the thermal zone doesn't necessarily
have to come from on sensor, and can be defined as a combination of
the input from multiple thermal sensors.
I don't know how to put this in proper words for the documentation,
but I think it's worth hinting it here.
Cheers,
Javi
WARNING: multiple messages have this Message-ID (diff)
From: Javi Merino <javi.merino@arm.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Rui Zhang <rui.zhang@intel.com>,
"ezequiel.garcia@free-electrons.com"
<ezequiel.garcia@free-electrons.com>,
"amit.kachhap@linaro.org" <amit.kachhap@linaro.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"amit.daniel@samsung.com" <amit.daniel@samsung.com>,
"hongbo.zhang@linaro.com" <hongbo.zhang@linaro.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"peter@piie.net" <peter@piie.net>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"aaron.lu@intel.com" <aaron.lu@intel.com>,
"caesar.wang@rock-chips.com" <caesar.wang@rock-chips.com>,
"b.zolnierkie@samsung.com" <b.zolnierkie@samsung.com>,
"l.majewski@samsung.com" <l.majewski@samsung.com>,
"vincenzo.frascino@st.com" <vincenzo.frascino@st.com>,
"mperttunen@nvidia.com" <mperttunen@nvidia.com>,
"mikko.perttunen@kapsi.fi" <mikko.perttunen@kapsi.fi>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>,
"bcousson@baylibre.com" <bcousson@baylibre.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH RFC 02/12] Documentation: thermal docbook: add glossary
Date: Wed, 18 Feb 2015 11:52:21 +0000 [thread overview]
Message-ID: <20150218115221.GD2990@e104805> (raw)
In-Reply-To: <1423517653-11359-3-git-send-email-edubezval@gmail.com>
Hi Eduardo,
On Mon, Feb 09, 2015 at 09:34:03PM +0000, Eduardo Valentin wrote:
> This change introduces a section in the Introduction Chapter to
> list concepts used by the Thermal Framework.
>
> Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
> ---
> Documentation/DocBook/thermal.tmpl | 129 ++++++++++++++++++++++++++++++++++++-
> 1 file changed, 128 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/DocBook/thermal.tmpl b/Documentation/DocBook/thermal.tmpl
> index f8fb8a2..66efed3 100644
> --- a/Documentation/DocBook/thermal.tmpl
> +++ b/Documentation/DocBook/thermal.tmpl
> @@ -84,5 +84,132 @@
> devices.
> </para>
>
> - </chapter>
> + <sect1 id="glossary">
> + <title>Glossary</title>
> + <para>The Linux Kernel Thermal Framework uses a
> + specific terminology to represent the entities involved
> + in thermal constrained environments. This section
> + summaries the terminology as dictionary. These terms are
> + in use within the present document and in the source
> + code of the Linux Kernel Thermal Framework.
> + </para>
> + <glossary>
> + <glossentry>
> + <glossterm>Thermal Zone</glossterm>
> + <glossdef>
> + <para>Thermal zones represent
> + what is the current status of a
> + thermal constrained zone in the
> + hardware. The zone usually is a
> + device or component. The status
> + of a thermal zone is mainly with
> + respect to temperature.
> + Currently, the Linux Kernel
> + Thermal Framework represents
> + temperature in miliCelsius. The
> + current abstraction covers for
> + non negative temperatures and
> + constraints.
> + </para>
Shall we point out that a thermal zone doesn't necessarily imply a
thermal sensor? I find it very common to assume that if you have 10
sensors, you should have 10 thermal zones. From my point of view, a
thermal zone is an area that has similar thermal characteristics.
Therefore, the temperature of the thermal zone doesn't necessarily
have to come from on sensor, and can be defined as a combination of
the input from multiple thermal sensors.
I don't know how to put this in proper words for the documentation,
but I think it's worth hinting it here.
Cheers,
Javi
next prev parent reply other threads:[~2015-02-18 11:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 21:34 [PATCH RFC 00/12] The Linux Kernel Thermal Framework Docbook Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 01/12] Documentation: Introduce Linux Kernel Thermal Framework DocBook Eduardo Valentin
2015-02-10 22:50 ` Randy Dunlap
2015-02-16 15:17 ` Eduardo Valentin
2015-02-18 11:13 ` Javi Merino
2015-02-18 11:13 ` Javi Merino
2015-02-09 21:34 ` [PATCH RFC 02/12] Documentation: thermal docbook: add glossary Eduardo Valentin
2015-02-10 22:50 ` Randy Dunlap
2015-02-16 15:19 ` Eduardo Valentin
2015-02-16 13:01 ` Mikko Perttunen
2015-02-17 3:22 ` Eduardo Valentin
2015-02-18 11:52 ` Javi Merino [this message]
2015-02-18 11:52 ` Javi Merino
2015-02-18 16:58 ` Srinivas Pandruvada
2015-02-18 16:58 ` Srinivas Pandruvada
2015-02-17 3:27 ` Eduardo Valentin
2015-02-17 3:27 ` Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 03/12] thermal: cpu_cooling: remove duplicate documentation entries Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 04/12] thermal: of-thermal: remove kernel doc warn Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 05/12] thermal: thermal.h: minor kernel doc fix Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 06/12] thermal: thermal_core: correct kernel doc wording on thermal_zone_get_temp Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 07/12] Documentation: thermal docbook: introduce API reference chapter Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 08/12] thermal: fair share: fix kernel doc entry Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 09/12] thermal: user space: " Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 10/12] thermal: bang bang: " Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 11/12] thermal: step wise: " Eduardo Valentin
2015-02-09 21:34 ` [PATCH RFC 12/12] Documentation: thermal docbook: introduce governor chapter Eduardo Valentin
2015-02-18 16:21 ` Javi Merino
2015-02-18 16:21 ` Javi Merino
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=20150218115221.GD2990@e104805 \
--to=javi.merino@arm.com \
--cc=aaron.lu@intel.com \
--cc=amit.daniel@samsung.com \
--cc=amit.kachhap@linaro.org \
--cc=andrew@lunn.ch \
--cc=b.zolnierkie@samsung.com \
--cc=caesar.wang@rock-chips.com \
--cc=durgadoss.r@intel.com \
--cc=edubezval@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=hongbo.zhang@linaro.com \
--cc=l.majewski@samsung.com \
--cc=mikko.perttunen@kapsi.fi \
--cc=mperttunen@nvidia.com \
--cc=peter@piie.net \
--cc=rui.zhang@intel.com \
--cc=shawn.guo@linaro.org \
--cc=srinivas.pandruvada@lin \
--cc=vincenzo.frascino@st.com \
--cc=viresh.kumar@linaro.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 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.