[lkml]   [2020]   [May]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC RESEND 0/3] Introduce cpufreq minimum load QoS
A first round [1] of discussions and suggestions have already be done on 
this series but without found a solution to the problem. I resend it to
progress on this topic.

When start streaming from the sensor the CPU load could remain very low
because almost all the capture pipeline is done in hardware (i.e. without
using the CPU) and let believe to cpufreq governor that it could use lower
frequencies. If the governor decides to use a too low frequency that
becomes a problem when we need to acknowledge the interrupt during the
blanking time.
The delay to ack the interrupt and perform all the other actions before
the next frame is very short and doesn't allow to the cpufreq governor to
provide the required burst of power. That led to drop the half of the frames.

To avoid this problem, DCMI driver informs the cpufreq governors by adding
a cpufreq minimum load QoS resquest.



Benjamin Gaignard (3):
PM: QoS: Introduce cpufreq minimum load QoS
cpufreq: governor: Use minimum load QoS
media: stm32-dcmi: Inform cpufreq governors about cpu load needs

drivers/cpufreq/cpufreq_governor.c | 5 +
drivers/media/platform/stm32/stm32-dcmi.c | 8 ++
include/linux/pm_qos.h | 12 ++
kernel/power/qos.c | 213 ++++++++++++++++++++++++++++++
4 files changed, 238 insertions(+)


 \ /
  Last update: 2020-05-26 17:17    [W:0.085 / U:4.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site