LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Rui Zhang <rui.zhang@intel.com>,
	ezequiel.garcia@free-electrons.com, amit.kachhap@linaro.org,
	viresh.kumar@linaro.org, amit.daniel@samsung.com,
	hongbo.zhang@linaro.com, andrew@lunn.ch, durgadoss.r@intel.com,
	peter@piie.net, shawn.guo@linaro.org, aaron.lu@intel.com,
	caesar.wang@rock-chips.com, b.zolnierkie@samsung.com,
	l.majewski@samsung.com, vincenzo.frascino@st.com,
	mperttunen@nvidia.com, mikko.perttunen@kapsi.fi,
	srinivas.pandruvada@linux.intel.com,
	jacob.jun.pan@linux.intel.com, bcousson@baylibre.com,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH RFC 01/12] Documentation: Introduce Linux Kernel Thermal Framework DocBook
Date: Mon, 16 Feb 2015 11:17:43 -0400	[thread overview]
Message-ID: <20150216151742.GC8648@developer.hsd1.ca.comcast.net> (raw)
In-Reply-To: <54DA8B3C.9040607@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 2866 bytes --]

On Tue, Feb 10, 2015 at 02:50:36PM -0800, Randy Dunlap wrote:
> On 02/09/15 13:34, Eduardo Valentin wrote:
> 
> > +	<chapter id="introduction">
> > +		<title>Introduction</title>
> > +		<para>Thermal management is any method or technique implied to
> > +		mitigate emergencies caused by operating devices within
> > +		unsupported temperatures. The challenge consists of designing a
> 
> I would flip the ending of that sentence:
> 		                     caused by operating devices outside of
> 		supported temperatures.
> 
> > +		product keeping the junction temperature of the IC components.
> > +		The operating temperature of IC components used on products must
> > +		operate within their design limits. Besides, temperature towards
> > +		device enclosure must be in a comfort level for the user.
> > +		Therefore, thermal management, by the time of this writing,
> > +		starts in very early device design phase. Managing thermal may
> > +		involve different disciplines, at different stages, such as
> > +		temperature monitoring, floorplanning, microarchitectural
> > +		techniques, compiler techniques, OS techniques, liquid cooling,
> > +		and thermal reliability or security. This document covers what
> > +		the Linux Kernel Thermal Framework provides as abstraction to
> > +		users with respect to thermal management.  
> > +		</para>
> > +		<para>One of the first proposals to provide a solution to cover
> > +		the thermal problem appears in the Advanced Configuration and
> > +		Power Interface (ACPI) specification. ACPI provides an open
> > +		standard for device configuration and power management by the
> > +		operating system. However, several computing devices which may
> > +		have thermal issues in the market disregard the ACPI standard.
> > +		Therefore, the Linux Kernel Thermal Framework has been designed
> > +		to serve as abstraction for ACPI and non-ACPI systems. The core
> > +		concepts applies in both types of systems. 
> > +		</para>
> > +		<para>The Linux Kernel Thermal Framework has a design which
> > +		represents the different thermal constraints found in an
> 
> drop:		                                                      an^^
> 
> > +		end-products. The thermal constraints exist to serve different
> > +		purposes. There two major types of thermal constraints. The
> 
> 		          There are two
> 
> > +		first is related to components junction temperature. The second
> > +		is related to the level of comfort while end users are handling
> > +		devices.
> > +		</para>
> > +
> > +  </chapter>
> > +</book>
> > 
> 
> 
> -- 
> ~Randy

Thanks Randy for checking this up. I apologize for forgetting Ccing you
in my original post. I will fix the text as per your suggestions and
also copy you in next version.

Thanks for you time.

Eduardo Valentin


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-02-16 20:14 UTC|newest]

Thread overview: 24+ 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 [this message]
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
2015-02-18 16:58     ` Srinivas Pandruvada
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

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=20150216151742.GC8648@developer.hsd1.ca.comcast.net \
    --to=edubezval@gmail.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=bcousson@baylibre.com \
    --cc=caesar.wang@rock-chips.com \
    --cc=durgadoss.r@intel.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=hongbo.zhang@linaro.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=l.majewski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mikko.perttunen@kapsi.fi \
    --cc=mperttunen@nvidia.com \
    --cc=peter@piie.net \
    --cc=rdunlap@infradead.org \
    --cc=rui.zhang@intel.com \
    --cc=shawn.guo@linaro.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=vincenzo.frascino@st.com \
    --cc=viresh.kumar@linaro.org \
    --subject='Re: [PATCH RFC 01/12] Documentation: Introduce Linux Kernel Thermal Framework DocBook' \
    /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

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).