Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 512bb03f authored by Hanjun Guo's avatar Hanjun Guo Committed by Rafael J. Wysocki
Browse files

ACPI: processor: use dev_dbg() instead of dev_warn() when CPPC probe failed 



_CPC is a optinal object for processor device so it's
fine for processor devices in DSDT without CPPC data,
but when booting the system with CPPC enabled in the
kernel but without its support in the firmware, I got
lots of warnings on a 64 core system:

[    6.346016] acpi ACPI0007:00: CPPC data invalid or not present
[    6.346028] acpi ACPI0007:01: CPPC data invalid or not present
[    6.346039] acpi ACPI0007:02: CPPC data invalid or not present
[    6.346050] acpi ACPI0007:03: CPPC data invalid or not present
[    6.346063] acpi ACPI0007:04: CPPC data invalid or not present
...
[    6.346737] acpi ACPI0007:3f: CPPC data invalid or not present

This isn't much useful and a little bit noise, so
switch the dev_warn() to dev_dbg().

Signed-off-by: default avatarHanjun Guo <hanjun.guo@linaro.org>
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent 520eccdf

drivers/acpi/processor_driver.c

+1 −1
Original line number Diff line number Diff line
@@ -237,7 +237,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))

		dev_warn(&device->dev, "CPPC data invalid or not present\n");

		dev_dbg(&device->dev, "CPPC data invalid or not present\n");



	if (!cpuidle_get_driver() || cpuidle_get_driver() == &acpi_idle_driver)

		acpi_processor_power_init(pr);