[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160428145054.GC19279@localhost.localdomain>
Date: Thu, 28 Apr 2016 07:50:55 -0700
From: Eduardo Valentin <edubezval@...il.com>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: Caesar Wang <wxt@...k-chips.com>, Heiko Stuebner <heiko@...ech.de>,
dianders@...omium.org, briannorris@...gle.com, smbarber@...gle.com,
linux-rockchip@...ts.infradead.org, dmitry.torokhov@...il.com,
huangtao@...k-chips.com, eddie.cai@...k-chips.com,
Zhang Rui <rui.zhang@...el.com>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] thermal: bang-bang governor: act on lower trip
boundary
On Thu, Apr 28, 2016 at 08:30:18AM +0200, Sascha Hauer wrote:
> On Wed, Apr 27, 2016 at 02:54:26PM -0700, Eduardo Valentin wrote:
> > On Mon, Apr 25, 2016 at 11:02:47AM +0800, Caesar Wang wrote:
> > > From: Sascha Hauer <s.hauer@...gutronix.de>
> > >
> > > With interrupt driven thermal zones we pass the lower and upper
> > > temperature on which shall be acted, so in the governor we have to act on
> > > the exact lower temperature to be consistent. Otherwise an interrupt maybe
> > > generated on the exact lower temperature, but the bang bang governor does
> > > not react.
> >
> > What is the expected impact on polling driven zones that use bang bang
> > after this change?
>
> Polling driven zones may have to be one step cooler before the governor
> reacts, otherwise the behaviour should be unaffected.
OK. Can we add this description of the expectation of what will happen
to polling driver zones in the next version? An explanation on how this
has bee tested on polling driven zones it is also welcome.
>
> Sascha
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Powered by blists - more mailing lists