02 May, 2012
1 commit
-
Performance and powersave governor's get_target_freq
is not called if driver chooses one of these two governors.
Add init function in governor profile to call update_devfreq
which will call get_target_freq subsequently.Signed-off-by: Xiaoguang Chen
Acked-by: MyungJoo Ham
Signed-off-by: Rafael J. Wysocki
20 Jan, 2012
1 commit
-
The frequency requested to devfreq device driver from devfreq governors
is restricted by min_freq and max_freq input.Signed-off-by: MyungJoo Ham
Signed-off-by: Kyungmin Park
02 Oct, 2011
1 commit
-
Four cpufreq-like governors are provided as examples.
powersave: use the lowest frequency possible. The user (device) should
set the polling_ms as 0 because polling is useless for this governor.performance: use the highest freqeuncy possible. The user (device)
should set the polling_ms as 0 because polling is useless for this
governor.userspace: use the user specified frequency stored at
devfreq.user_set_freq. With sysfs support in the following patch, a user
may set the value with the sysfs interface.simple_ondemand: simplified version of cpufreq's ondemand governor.
When a user updates OPP entries (enable/disable/add), OPP framework
automatically notifies devfreq to update operating frequency
accordingly. Thus, devfreq users (device drivers) do not need to update
devfreq manually with OPP entry updates or set polling_ms for powersave
, performance, userspace, or any other "static" governors.Note that these are given only as basic examples for governors and any
devices with devfreq may implement their own governors with the drivers
and use them.Signed-off-by: MyungJoo Ham
Signed-off-by: Kyungmin Park
Reviewed-by: Mike Turquette
Acked-by: Kevin Hilman
Signed-off-by: Rafael J. Wysocki