On 18-02-21, 10:03, Thara Gopinath wrote:
> Scheduling a notifier for max frequency change from the qos framework should
> do the work, right?
Not that, but we need to increase/decrease cooling states at run time,
create sysfs files/directories, etc. It isn't worth it.
--
viresh
On 2/18/21 3:48 AM, Viresh Kumar wrote:
On 17-02-21, 10:32, Thara Gopinath wrote:
First of all, I am still unable to find this setting in the sysfs space.
The driver needs to call cpufreq_enable_boost_support() for that.
Ok. that makes sense.
Irrespective the ideal behavior here will
On 17-02-21, 10:32, Thara Gopinath wrote:
> First of all, I am still unable to find this setting in the sysfs space.
The driver needs to call cpufreq_enable_boost_support() for that.
> Irrespective the ideal behavior here will be to change the cpufreq cooling
> dev max state when this happens.
On 2/17/21 12:50 AM, Viresh Kumar wrote:
Hi Thara,
On 16-02-21, 19:00, Thara Gopinath wrote:
This is a fix for a regression observed on db845 platforms with 5.7-rc11
kernel. On these platforms running stress tests with 5.11-rc7 kernel
causes big cpus to overheat and ultimately shutdown the
Hi Thara,
On 16-02-21, 19:00, Thara Gopinath wrote:
> This is a fix for a regression observed on db845 platforms with 5.7-rc11
> kernel. On these platforms running stress tests with 5.11-rc7 kernel
> causes big cpus to overheat and ultimately shutdown the system due to
> hitting critical
This is a fix for a regression observed on db845 platforms with 5.7-rc11
kernel. On these platforms running stress tests with 5.11-rc7 kernel
causes big cpus to overheat and ultimately shutdown the system due to
hitting critical temperature (thermal throttling does not happen and
cur_state of
6 matches
Mail list logo
