cpufreq: Don't clip PM QoS requests to old policy limits
authorAlex Frid <afrid@nvidia.com>
Tue, 15 May 2012 04:06:11 +0000 (21:06 -0700)
committerRohan Somvanshi <rsomvanshi@nvidia.com>
Thu, 17 May 2012 11:26:40 +0000 (04:26 -0700)
commit30ea6f3571852533737e412b5f7786fdac8b6c9f
tree20b77621aa50d2b866a66076e438a610c17bf9e5
parent1ed0961122af7753b557a46ede66e4e78c71138a
cpufreq: Don't clip PM QoS requests to old policy limits

Clipping PM QoS requests to combined old policy limits that include
both PM QoS and user policy requests creates a circular dependency.
As a result new PM QoS maximum limit is rejected if it is above
previous PM QoS minimum limit even though the new PM QoS minimum
limit has been already lowered below new PM QoS maximum limit.

Instead clip PM QoS request to the old user policy limits only.

Change-Id: Ice0a53a699e0798f07f0e32d6b8a28586fe5db0c
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/102386
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Antti Miettinen <amiettinen@nvidia.com>
Reviewed-by: Diwakar Tundlam <dtundlam@nvidia.com>
Tested-by: Vikas Ramesh Kedigehalli <vikasr@nvidia.com>
drivers/cpufreq/cpufreq.c