[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D68720C2E767A4AA6A8796D42C8EB59257F01@BGSMSX101.gar.corp.intel.com>
Date: Wed, 9 Jan 2013 09:12:29 +0000
From: "R, Durgadoss" <durgadoss.r@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "Zhang, Rui" <rui.zhang@...el.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"eduardo.valentin@...com" <eduardo.valentin@...com>,
"hongbo.zhang@...aro.org" <hongbo.zhang@...aro.org>,
"wni@...dia.com" <wni@...dia.com>
Subject: RE: [PATCH 7/9] Thermal: Make PER_ZONE values configurable
Hi Greg,
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Tuesday, January 08, 2013 12:54 AM
> To: R, Durgadoss
> Cc: Zhang, Rui; linux-pm@...r.kernel.org; linux-kernel@...r.kernel.org;
> eduardo.valentin@...com; hongbo.zhang@...aro.org; wni@...dia.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists