summaryrefslogtreecommitdiff
path: root/drivers/acpi/processor_driver.c
diff options
context:
space:
mode:
authorSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>2016-09-01 23:37:09 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-09-09 00:02:14 +0300
commit5448f14698b916e5b04112b104433b90247e01c7 (patch)
tree32fb3d3c09368dd1329bb37b578c21864879bef5 /drivers/acpi/processor_driver.c
parent65e958910a0342c2d802dea05eaf0de16c1b872a (diff)
downloadlinux-5448f14698b916e5b04112b104433b90247e01c7.tar.xz
ACPI / CPPC: Don't return on CPPC probe failure
It is still possible to continue even CPPC data is invalid or missing. Suggested-by: Alexey Klimov <alexey.klimov@arm.com> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/acpi/processor_driver.c')
-rw-r--r--drivers/acpi/processor_driver.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
index f5c92be72987..8f8552a19e63 100644
--- a/drivers/acpi/processor_driver.c
+++ b/drivers/acpi/processor_driver.c
@@ -246,7 +246,7 @@ static int __acpi_processor_start(struct acpi_device *device)
result = acpi_cppc_processor_probe(pr);
if (result && !IS_ENABLED(CONFIG_ACPI_CPU_FREQ_PSS))
- return -ENODEV;
+ dev_warn(&device->dev, "CPPC data invalid or not present\n");
if (!cpuidle_get_driver() || cpuidle_get_driver() == &acpi_idle_driver)
acpi_processor_power_init(pr);