Attachment 113304 Details for Bug 89052 – drm/i915/skl: handle all pixel formats in skylake_update_primary_plane

[patch] drm/i915/skl: handle all pixel formats in skylake_update_primary_plane

0001-drm-i915-skl-handle-all-pixel-formats-in-skylake_upd.patch (text/plain), 1.37 KB, created by Jani Nikula on 2015-02-10 08:50:28 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jani Nikula

Created: 2015-02-10 08:50:28 UTC

Size: 1.37 KB

patch

obsolete

>From 33114ac84d495a487b295c98973c1c6338f85c69 Mon Sep 17 00:00:00 2001
>From: Jani Nikula <jani.nikula@intel.com>
>Date: Tue, 10 Feb 2015 10:49:37 +0200
>Subject: [PATCH] drm/i915/skl: handle all pixel formats in
> skylake_update_primary_plane
>Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
>Cc: Jani Nikula <jani.nikula@intel.com>
>
>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>---
> drivers/gpu/drm/i915/intel_display.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
>diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>index 3fe95982be93..cede05256d56 100644
>--- a/drivers/gpu/drm/i915/intel_display.c
>+++ b/drivers/gpu/drm/i915/intel_display.c
>@@ -2751,10 +2751,19 @@ static void skylake_update_primary_plane(struct drm_crtc *crtc,
> 	case DRM_FORMAT_XRGB8888:
> 		plane_ctl |= PLANE_CTL_FORMAT_XRGB_8888;
> 		break;
>+	case DRM_FORMAT_ARGB8888:
>+		plane_ctl |= PLANE_CTL_FORMAT_XRGB_8888;
>+		plane_ctl |= PLANE_CTL_ALPHA_SW_PREMULTIPLY;
>+		break;
> 	case DRM_FORMAT_XBGR8888:
> 		plane_ctl |= PLANE_CTL_ORDER_RGBX;
> 		plane_ctl |= PLANE_CTL_FORMAT_XRGB_8888;
> 		break;
>+	case DRM_FORMAT_ABGR8888:
>+		plane_ctl |= PLANE_CTL_ORDER_RGBX;
>+		plane_ctl |= PLANE_CTL_FORMAT_XRGB_8888;
>+		plane_ctl |= PLANE_CTL_ALPHA_SW_PREMULTIPLY;
>+		break;
> 	case DRM_FORMAT_XRGB2101010:
> 		plane_ctl |= PLANE_CTL_FORMAT_XRGB_2101010;
> 		break;
>-- 
>2.1.4
>

Actions: View | Splinter Review

Attachments on bug 89052: 113294 | 113304

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.