ACPI: CPPC: Adjust debug messages in amd_set_max_freq_ratio() to warn

If the boost ratio isn't calculated properly for the system for any
reason this can cause other problems that are non-obvious.

Raise all messages to warn instead.

Suggested-by: Perry Yuan <Perry.Yuan@amd.com>
Reviewed-by: Perry Yuan <perry.yuan@amd.com>
Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>

diff --git a/arch/x86/kernel/acpi/cppc.c b/arch/x86/kernel/acpi/cppc.c
index e65c77a..f0328ce 100644 (file)
--- a/arch/x86/kernel/acpi/cppc.c
+++ b/arch/x86/kernel/acpi/cppc.c
@@ -75,19 +75,19 @@ static void amd_set_max_freq_ratio(void)
 
        rc = cppc_get_perf_caps(0, &perf_caps);
        if (rc) {
-               pr_debug("Could not retrieve perf counters (%d)\n", rc);
+               pr_warn("Could not retrieve perf counters (%d)\n", rc);
                return;
        }
 
        rc = amd_get_boost_ratio_numerator(0, &numerator);
        if (rc) {
-               pr_debug("Could not retrieve highest performance (%d)\n", rc);
+               pr_warn("Could not retrieve highest performance (%d)\n", rc);
                return;
        }
        nominal_perf = perf_caps.nominal_perf;
 
        if (!nominal_perf) {
-               pr_debug("Could not retrieve nominal performance\n");
+               pr_warn("Could not retrieve nominal performance\n");
                return;
        }