mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christopher Obbard <chris.obbard@collabora.com>
To: Jonas Karlman <jonas@kwiboo.se>, Heiko Stuebner <heiko@sntech.de>,
	Sandy Huang <hjc@rock-chips.com>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel <kernel@collabora.com>
Subject: Re: [PATCH] drm/rockchip: vop: Fix color for RGB888/BGR888 format on VOP full
Date: Tue, 24 Oct 2023 09:49:35 +0100	[thread overview]
Message-ID: <a505d18044ccef9f188df91bc2afe73e6a15635f.camel@collabora.com> (raw)
In-Reply-To: <20231023211158.424489-1-jonas@kwiboo.se>

Hi Jonas,

On Mon, 2023-10-23 at 21:11 +0000, Jonas Karlman wrote:
> Use of DRM_FORMAT_RGB888 and DRM_FORMAT_BGR888 on e.g. RK3288, RK3328
> and RK3399 result in wrong colors being displayed.
> 
> The issue can be observed using modetest:
> 
>   modetest -s <connector_id>@<crtc_id>:1920x1080-60@RG24
>   modetest -s <connector_id>@<crtc_id>:1920x1080-60@BG24
> 
> Vendor 4.4 kernel apply an inverted rb swap for these formats on VOP
> full (major = 3).
> 
> Fix colors by applying rb swap similar to vendor 4.4 kernel.
> 
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>

How about a fixes tag? Seems like this was introduced in commit 85a359f25388
("drm/rockchip: Add BGR formats to VOP")

> ---
>  drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> index b3d0b6ae9294..a1ce09a22f83 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
> @@ -247,14 +247,17 @@ static inline void vop_cfg_done(struct vop *vop)
>  	VOP_REG_SET(vop, common, cfg_done, 1);
>  }
>  
> -static bool has_rb_swapped(uint32_t format)
> +static bool has_rb_swapped(uint32_t version, uint32_t format)
>  {
>  	switch (format) {
>  	case DRM_FORMAT_XBGR8888:
>  	case DRM_FORMAT_ABGR8888:
> -	case DRM_FORMAT_BGR888:
>  	case DRM_FORMAT_BGR565:
>  		return true;
> +	case DRM_FORMAT_RGB888:
> +		return VOP_MAJOR(version) == 3;
> +	case DRM_FORMAT_BGR888:
> +		return VOP_MAJOR(version) != 3;

The hardcoded bits are quite scary as it applies to all hardware variants ;-).
Is it worth adding an inline comment to describe what is going on and how it
relates to VOPL and VOPH? Or would it be even better to add this as a quirk in
the various vop_data structs?


Cheers!

Chris

>  	default:
>  		return false;
>  	}
> @@ -1035,7 +1038,7 @@ static void vop_plane_atomic_update(struct drm_plane
> *plane,
>  	VOP_WIN_SET(vop, win, dsp_info, dsp_info);
>  	VOP_WIN_SET(vop, win, dsp_st, dsp_st);
>  
> -	rb_swap = has_rb_swapped(fb->format->format);
> +	rb_swap = has_rb_swapped(vop->data->version, fb->format->format);
>  	VOP_WIN_SET(vop, win, rb_swap, rb_swap);
>  
>  	/*

  reply	other threads:[~2023-10-24  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 21:11 Jonas Karlman
2023-10-24  8:49 ` Christopher Obbard [this message]
2023-10-24 12:41   ` Andy Yan
2023-10-24 16:35     ` Jonas Karlman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a505d18044ccef9f188df91bc2afe73e6a15635f.camel@collabora.com \
    --to=chris.obbard@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=hjc@rock-chips.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®