Hi Sudeep,
On Wed, Dec 2, 2015 at 7:40 PM, Sudeep Holla <sudeep.holla@xxxxxxx> wrote:
diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
index 29f787b2493f..bfc59de0ce6b 100644
--- a/drivers/acpi/processor_driver.c
+++ b/drivers/acpi/processor_driver.c
@@ -90,7 +90,7 @@ static void acpi_processor_notify(acpi_handle handle, u32 event, void *data)
pr->performance_platform_limit);
break;
case ACPI_PROCESSOR_NOTIFY_POWER:
- acpi_processor_cst_has_changed(pr);
+ acpi_processor_power_state_has_changed(pr);
The function acpi_processor_power_state_has_changed() has a check as below,
if (nocst)
return -ENODEV;
So was wondering if the platform supports only _LPI and _CST is not
supported, the 'nocst' module param passed will be 1,
and function will return -ENODEV.
Hence, with the introduction of LPI, should we be handling "nocst"
appropriately.
Similar is the case in function int acpi_processor_hotplug(struct
acpi_processor *pr);
Let me know, if i am missing something here.