Attachment 86598 Details for Bug 69675 – use hw generated cts and n values rather than the sw programmed values

[patch] use hw generated cts and n values rather than the sw programmed values

use_hw_generated_cts_n.diff (text/plain), 1.33 KB, created by Alex Deucher on 2013-09-25 20:12:19 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2013-09-25 20:12:19 UTC

Size: 1.33 KB

patch

obsolete

>diff --git a/drivers/gpu/drm/radeon/evergreen_hdmi.c b/drivers/gpu/drm/radeon/evergreen_hdmi.c
>index f71ce39..f815c20 100644
>--- a/drivers/gpu/drm/radeon/evergreen_hdmi.c
>+++ b/drivers/gpu/drm/radeon/evergreen_hdmi.c
>@@ -288,8 +288,7 @@ void evergreen_hdmi_setmode(struct drm_encoder *encoder, struct drm_display_mode
> 	/* fglrx clears sth in AFMT_AUDIO_PACKET_CONTROL2 here */
> 
> 	WREG32(HDMI_ACR_PACKET_CONTROL + offset,
>-	       HDMI_ACR_AUTO_SEND | /* allow hw to sent ACR packets when required */
>-	       HDMI_ACR_SOURCE); /* select SW CTS value */
>+	       HDMI_ACR_AUTO_SEND); /* allow hw to sent ACR packets when required */
> 
> 	evergreen_hdmi_update_ACR(encoder, mode->clock);
> 
>diff --git a/drivers/gpu/drm/radeon/r600_hdmi.c b/drivers/gpu/drm/radeon/r600_hdmi.c
>index b0fa600..16edcb8 100644
>--- a/drivers/gpu/drm/radeon/r600_hdmi.c
>+++ b/drivers/gpu/drm/radeon/r600_hdmi.c
>@@ -444,8 +444,7 @@ void r600_hdmi_setmode(struct drm_encoder *encoder, struct drm_display_mode *mod
> 	}
> 
> 	WREG32(HDMI0_ACR_PACKET_CONTROL + offset,
>-	       HDMI0_ACR_AUTO_SEND | /* allow hw to sent ACR packets when required */
>-	       HDMI0_ACR_SOURCE); /* select SW CTS value */
>+	       HDMI0_ACR_AUTO_SEND); /* allow hw to sent ACR packets when required */
> 
> 	WREG32(HDMI0_VBI_PACKET_CONTROL + offset,
> 	       HDMI0_NULL_SEND | /* send null packets when required */

Actions: View | Splinter Review

Attachments on bug 69675: 86598 | 86739 | 86740 | 86741 | 86856 | 88450 | 88476 | 88775 | 88776

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.