From: "R, Durgadoss" <durgadoss.r@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"eduardo.valentin@ti.com" <eduardo.valentin@ti.com>,
"hongbo.zhang@linaro.org" <hongbo.zhang@linaro.org>,
"wni@nvidia.com" <wni@nvidia.com>
Subject: RE: [PATCH 7/9] Thermal: Make PER_ZONE values configurable
Date: Wed, 9 Jan 2013 09:12:29 +0000 [thread overview]
Message-ID: <4D68720C2E767A4AA6A8796D42C8EB59257F01@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <20130107192414.GC4465@kroah.com>
Hi Greg,
> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Tuesday, January 08, 2013 12:54 AM
> To: R, Durgadoss
> Cc: Zhang, Rui; linux-pm@vger.kernel.org; linux-kernel@vger.kernel.org;
> eduardo.valentin@ti.com; hongbo.zhang@linaro.org; wni@nvidia.com
> Subject: Re: [PATCH 7/9] Thermal: Make PER_ZONE values configurable
>
> On Mon, Jan 07, 2013 at 12:43:24PM +0530, Durgadoss R wrote:
> > This patch makes MAX_SENSORS_PER_ZONE and
> > MAX_CDEVS_PER_ZONE values configurable. The
> > default value is 1, and range is 1-12.
>
> Why would we ever want to change this? Why make this configurable at
> all, how is a distro supposed to set this value?
>
> Shouldn't it be specified from the driver itself?
These are platform level parameters, that can differ for various platforms.
(Mostly due to board design and thermistor layouts). Stand-alone thermal
sensor drivers are not (need not be) aware of these values.
That's why these values are made configurable.
Thanks,
Durga
next prev parent reply other threads:[~2013-01-09 9:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 7:13 [PATCHv2 0/9] Thermal Framework Enhancements Durgadoss R
2013-01-07 7:13 ` [PATCH 1/9] Thermal: Create sensor level APIs Durgadoss R
2013-01-07 7:13 ` [PATCH 2/9] Thermal: Create zone " Durgadoss R
2013-01-07 7:13 ` [PATCH 3/9] Thermal: Add APIs to bind cdev to new zone structure Durgadoss R
2013-01-07 19:26 ` Greg KH
2013-01-09 9:21 ` R, Durgadoss
2013-01-09 17:01 ` Greg KH
2013-01-07 7:13 ` [PATCH 4/9] Thermal: Add trip point sysfs nodes for sensor Durgadoss R
2013-01-07 7:13 ` [PATCH 5/9] Thermal: Create 'mapX' sysfs node for a zone Durgadoss R
2013-01-07 19:21 ` Greg KH
2013-01-10 12:50 ` R, Durgadoss
2013-01-10 14:28 ` Greg KH
2013-01-07 7:13 ` [PATCH 6/9] Thermal: Add Documentation to new APIs Durgadoss R
2013-01-07 8:40 ` Wei Ni
2013-01-07 8:53 ` R, Durgadoss
2013-01-07 9:28 ` Wei Ni
2013-01-16 8:04 ` Mattias NILSSON1
2013-01-07 7:13 ` [PATCH 7/9] Thermal: Make PER_ZONE values configurable Durgadoss R
2013-01-07 19:24 ` Greg KH
2013-01-09 9:12 ` R, Durgadoss [this message]
2013-01-09 17:00 ` Greg KH
2013-01-10 12:43 ` R, Durgadoss
2013-01-10 14:27 ` Greg KH
2013-01-07 7:13 ` [PATCH 8/9] Thermal: Add ABI Documentation for sysfs interfaces Durgadoss R
2013-02-19 9:10 ` Pavel Machek
2013-01-07 7:13 ` [PATCH 9/9] Thermal: Dummy driver used for testing Durgadoss R
2013-01-07 19:23 ` Greg KH
2013-01-21 10:10 ` [PATCHv2 0/9] Thermal Framework Enhancements Wei Ni
2013-02-04 5:39 ` Wei Ni
2013-02-04 6:37 ` R, Durgadoss
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=4D68720C2E767A4AA6A8796D42C8EB59257F01@BGSMSX101.gar.corp.intel.com \
--to=durgadoss.r@intel.com \
--cc=eduardo.valentin@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=hongbo.zhang@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--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 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).