Attachment 87006 Details for Bug 70053 – possible fix

[patch] possible fix

bug70053.diff (text/plain), 1.48 KB, created by Alex Deucher on 2013-10-02 21:47:57 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2013-10-02 21:47:57 UTC

Size: 1.48 KB

patch

obsolete

>diff --git a/drivers/gpu/drm/radeon/radeon_pm.c b/drivers/gpu/drm/radeon/radeon_pm.c
>index d1662c0..601acf0 100644
>--- a/drivers/gpu/drm/radeon/radeon_pm.c
>+++ b/drivers/gpu/drm/radeon/radeon_pm.c
>@@ -73,6 +73,8 @@ void radeon_pm_acpi_event_handler(struct radeon_device *rdev)
> 			rdev->pm.dpm.ac_power = true;
> 		else
> 			rdev->pm.dpm.ac_power = false;
>+		printk("radeon_pm_acpi_event_handler running on %s power\n",
>+		       rdev->pm.dpm.ac_power ? "AC" : "DC");
> 		if (rdev->asic->dpm.enable_bapm)
> 			radeon_dpm_enable_bapm(rdev, rdev->pm.dpm.ac_power);
> 		mutex_unlock(&rdev->pm.mutex);
>diff --git a/drivers/gpu/drm/radeon/trinity_dpm.c b/drivers/gpu/drm/radeon/trinity_dpm.c
>index 7f998bf..4535b83 100644
>--- a/drivers/gpu/drm/radeon/trinity_dpm.c
>+++ b/drivers/gpu/drm/radeon/trinity_dpm.c
>@@ -1225,6 +1225,8 @@ int trinity_dpm_set_power_state(struct radeon_device *rdev)
> 
> 	trinity_acquire_mutex(rdev);
> 	if (pi->enable_dpm) {
>+		printk("trinity_dpm_set_power_state running on %s power\n",
>+		       rdev->pm.dpm.ac_power ? "AC" : "DC");
> 		if (pi->enable_bapm)
> 			trinity_dpm_bapm_enable(rdev, rdev->pm.dpm.ac_power);
> 		trinity_set_uvd_clock_before_set_eng_clock(rdev, new_ps, old_ps);
>@@ -1868,7 +1870,7 @@ int trinity_dpm_init(struct radeon_device *rdev)
> 	for (i = 0; i < SUMO_MAX_HARDWARE_POWERLEVELS; i++)
> 		pi->at[i] = TRINITY_AT_DFLT;
> 
>-	pi->enable_bapm = true;
>+	pi->enable_bapm = false;
> 	pi->enable_nbps_policy = true;
> 	pi->enable_sclk_ds = true;
> 	pi->enable_gfx_power_gating = true;

Actions: View | Splinter Review

Attachments on bug 70053: 87002 | 87003 | 87006 | 87033 | 87044

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.