On 07/03/18 10:59, Amit Kucheria wrote:
> On Tue, Mar 6, 2018 at 6:02 PM, Sudeep Holla wrote:
>>
>>
>> On 05/03/18 18:36, Amit Kucheria wrote:
>>> From: Ram Chandrasekar
>>>
>>> There is currently no way for the governor to be selected for each thermal
>>> zone in devicetree.
>>
>> How is that
On 08-03-18, 11:05, Amit Kucheria wrote:
> Interestingly enough, there are some patches that make the thermal
> framework start earlier to deal with boot-time thermal issues. I
> expect to post them soon. :-) These are required, for example, if the
> device goes into a reboot loop - the device migh
On Thu, Mar 8, 2018 at 10:19 AM, Viresh Kumar wrote:
> On Wed, Mar 7, 2018 at 4:29 PM, Amit Kucheria
> wrote:
>> Cpufreq/cpuidle are designed to control a single parameter while
>> thermal framework is trying to mitigate heat from several disparate
>> sources that are throttled in different ways
On Wed, Mar 7, 2018 at 4:29 PM, Amit Kucheria wrote:
> Cpufreq/cpuidle are designed to control a single parameter while
> thermal framework is trying to mitigate heat from several disparate
> sources that are throttled in different ways. Besides, cpufreq/cpuidle
> have somewhat mature governors. C
On Tue, Mar 6, 2018 at 6:02 PM, Sudeep Holla wrote:
>
>
> On 05/03/18 18:36, Amit Kucheria wrote:
>> From: Ram Chandrasekar
>>
>> There is currently no way for the governor to be selected for each thermal
>> zone in devicetree.
>
> How is that any different from cpufreq, cpuidle or devfreq subsys
On 06/03/2018 06:48, Amit Kucheria wrote:
> On Tue, Mar 6, 2018 at 2:41 AM, Daniel Lezcano
> wrote:
>> On 05/03/2018 19:36, Amit Kucheria wrote:
>>> From: Ram Chandrasekar
>>>
>>> There is currently no way for the governor to be selected for each thermal
>>> zone in devicetree. This results in th
On 05/03/18 18:36, Amit Kucheria wrote:
> From: Ram Chandrasekar
>
> There is currently no way for the governor to be selected for each thermal
> zone in devicetree.
How is that any different from cpufreq, cpuidle or devfreq subsystems ?
> This results in the default governor being used for
On Tue, Mar 6, 2018 at 2:41 AM, Daniel Lezcano
wrote:
> On 05/03/2018 19:36, Amit Kucheria wrote:
>> From: Ram Chandrasekar
>>
>> There is currently no way for the governor to be selected for each thermal
>> zone in devicetree. This results in the default governor being used for all
>> thermal zo
On Tue, Mar 6, 2018 at 1:38 AM, Rob Herring wrote:
> On Mon, Mar 5, 2018 at 12:36 PM, Amit Kucheria
> wrote:
>> From: Ram Chandrasekar
>>
>> There is currently no way for the governor to be selected for each thermal
>> zone in devicetree. This results in the default governor being used for all
On 05/03/2018 19:36, Amit Kucheria wrote:
> From: Ram Chandrasekar
>
> There is currently no way for the governor to be selected for each thermal
> zone in devicetree. This results in the default governor being used for all
> thermal zones even though no such restriction exists in the core code.
On Mon, Mar 5, 2018 at 12:36 PM, Amit Kucheria wrote:
> From: Ram Chandrasekar
>
> There is currently no way for the governor to be selected for each thermal
> zone in devicetree. This results in the default governor being used for all
> thermal zones even though no such restriction exists in the
From: Ram Chandrasekar
There is currently no way for the governor to be selected for each thermal
zone in devicetree. This results in the default governor being used for all
thermal zones even though no such restriction exists in the core code.
Add support for specifying the thermal governor to
12 matches
Mail list logo
