From: mark gross <markgross@xxxxxxxxxxx>
> Maybe I'm missing something but cpufreq already has ABI for setting
> upper and lower bounds for frequencies.
>
> /sys/devices/system/cpu/cpu0/cpufreq/[scaling_min_freq,
> scaling_max_freq]
>
> --mark
Yes, and the patch just adds two read-only files,
/sys/devices/system/cpu/cpu?/cpufreq/policy_{min,max}_freq:
+show_one(policy_min_freq, user_policy.min);
+show_one(policy_max_freq, user_policy.max);
to show the user_policy.min/max in addition to the
policy->min/max. This is related to patch 4 which changes the
scaling_{min,max}_freq store function to store the received value to
user_policy instead of the enforced value. Related in turn to the
restoring of the policy values when PM QoS constraints get lifted. The
purpose of patch 3 is to allow inspecting the requested min/max in
addition to the enforced min/max.
--Antti
Adding cpufreq to cc, previous comments for context:
http://thread.gmane.org/gmane.linux.power-management.general/26532
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
