ACPI / CPPC: use MRTT/MPAR to decide if/when a req can be sent
authorPrakash, Prashanth <pprakash@codeaurora.org>
Wed, 17 Feb 2016 20:21:03 +0000 (13:21 -0700)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 9 Mar 2016 22:35:29 +0000 (23:35 +0100)
commitf387e5b901adb8352fcdf031bb2c539e390b92e2
treed503c4224dbdbeeab08271ea78bc4ef07d80ed4e
parentbeee23aebc6650609ef1547f6d813fa5065f74aa
ACPI / CPPC: use MRTT/MPAR to decide if/when a req can be sent

The ACPI spec defines Minimum Request Turnaround Time(MRTT) and
Maximum Periodic Access Rate(MPAR) to prevent the OSPM from sending
too many requests than the platform can handle. For further details
on these parameters please refer to section 14.1.3 of ACPI 6.0 spec.

This patch includes MRTT/MPAR in deciding if or when a CPPC request
can be sent to the platform to make sure CPPC implementation is
compliant to the spec.

Signed-off-by: Prashanth Prakash <pprakash@codeaurora.org>
Acked-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/acpi/cppc_acpi.c