[seems that posting via gmane is broken - resending (heehee - I do resent the gmane problem :) manually via mail - sorry if you get duplicates] mark gross <markgross@xxxxxxxxxxx> writes: > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c > index 987a165..4cbd58b 100644 > --- a/drivers/cpufreq/cpufreq.c > +++ b/drivers/cpufreq/cpufreq.c [..] > + > + if (policy->min < pm_qos_request(PM_QOS_CPU_THROUGHPUT)) > + policy->min = pm_qos_request(PM_QOS_CPU_THROUGHPUT); > Consider the following sequence - say original min is 100MHz - PM QoS requests 1GHz minimum - user requests 500MHz minimum via sysfs - PM QoS request is canceled After this the policy->min will be 1GHz. I'm not really happy with the min/max save/restore etc but something is needed to enable restoring the policy min/max when PM QoS constraints dissappear. --Antti _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/linux-pm
