nuttx/drivers/devfreq
guanyi3 674e5ef4d8 drivers/devfreq: use hardware frequency instead of cached value in driver_target
The cached devfreq->cur may become stale when the hardware frequency is
changed externally (e.g. by another core or governor). This causes
driver_target to incorrectly skip frequency transitions when the target
matches the cached value but differs from the actual hardware frequency.

Use driver->get_frequency() to read the real hardware frequency for the
unchanged check, and sync devfreq->cur on match to keep the cache correct.

Signed-off-by: guanyi3 <guanyi3@xiaomi.com>
2026-08-08 15:23:54 -03:00
..
CMakeLists.txt
devfreq.c drivers/devfreq: use hardware frequency instead of cached value in driver_target 2026-08-08 15:23:54 -03:00
devfreq_ondemand.c drivers/devfreq: use hardware frequency instead of cached value in driver_target 2026-08-08 15:23:54 -03:00
devfreq_performance.c drivers/devfreq: remove default governor 2026-08-08 15:23:54 -03:00
devfreq_powersave.c drivers/devfreq: remove default governor 2026-08-08 15:23:54 -03:00
devfreq_procfs.c drivers/devfreq: use hardware frequency instead of cached value in driver_target 2026-08-08 15:23:54 -03:00
devfreq_qos.c
Kconfig drivers/devfreq: remove default governor 2026-08-08 15:23:54 -03:00
Make.defs