cpufreq/amd-pstate: Drop debug statements for policy setting

There are trace events that exist now for all amd-pstate modes that
will output information right before programming to the hardware.

This makes the existing debug statements unnecessary remaining
overhead.  Drop them.

Reviewed-by: Dhananjay Ugwekar <dhananjay.ugwekar@amd.com>
Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>

diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
index df42a2d22225bb2a3443bba91fc74bfd2ba588a5..c70ed41a2448f794c763fe48633cd2b090cb75e2 100644 (file)
--- a/drivers/cpufreq/amd-pstate.c
+++ b/drivers/cpufreq/amd-pstate.c
@@ -667,7 +667,6 @@ static int amd_pstate_verify(struct cpufreq_policy_data *policy_data)
        }
 
        cpufreq_verify_within_cpu_limits(policy_data);
-       pr_debug("policy_max =%d, policy_min=%d\n", policy_data->max, policy_data->min);
 
        return 0;
 }
@@ -1630,9 +1629,6 @@ static int amd_pstate_epp_set_policy(struct cpufreq_policy *policy)
        if (!policy->cpuinfo.max_freq)
                return -ENODEV;
 
-       pr_debug("set_policy: cpuinfo.max %u policy->max %u\n",
-                               policy->cpuinfo.max_freq, policy->max);
-
        cpudata->policy = policy->policy;
 
        ret = amd_pstate_epp_update_limit(policy);