mirror of
https://github.com/torvalds/linux.git
synced 2024-12-01 08:31:37 +00:00
d2216ba3eb
We're taking into account both HW memory-accesses + CPU activity based on current CPU's frequency. For memory-accesses there is a kind of hysteresis in a form of "boosting" which is managed by the tegra30-devfreq driver. If current HW memory activity is higher than activity judged based of the CPU's frequency, then there is no need to schedule cpufreq_update_work because the result of the work will be a NO-OP. And thus, tegra_actmon_cpufreq_contribution() should return 0, meaning that at the moment CPU frequency doesn't contribute anything to the final decision about required memory clock rate. Signed-off-by: Dmitry Osipenko <digetx@gmail.com> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com> |
||
|---|---|---|
| .. | ||
| event | ||
| devfreq-event.c | ||
| devfreq.c | ||
| exynos-bus.c | ||
| governor_passive.c | ||
| governor_performance.c | ||
| governor_powersave.c | ||
| governor_simpleondemand.c | ||
| governor_userspace.c | ||
| governor.h | ||
| imx8m-ddrc.c | ||
| Kconfig | ||
| Makefile | ||
| rk3399_dmc.c | ||
| tegra20-devfreq.c | ||
| tegra30-devfreq.c | ||