diff options
| author | Mario Limonciello <mario.limonciello@amd.com> | 2024-12-09 23:44:15 +0300 |
|---|---|---|
| committer | Mario Limonciello <mario.limonciello@amd.com> | 2025-03-06 22:01:25 +0300 |
| commit | 93039a60fb28f72196769869aa4b502f1849a373 (patch) | |
| tree | 206431eba24c82eabb7b1dfaab782e2df8f10f1d | |
| parent | 1905fac6f9e08e34135e089704a0733ce711eb83 (diff) | |
| download | linux-93039a60fb28f72196769869aa4b502f1849a373.tar.xz | |
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>
| -rw-r--r-- | drivers/cpufreq/amd-pstate.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c index df42a2d22225..c70ed41a2448 100644 --- 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); |