[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0dfb0aafeb37f0683182ef23293bb8373dd7caf2.camel@collabora.com>
Date: Mon, 26 Jan 2026 15:25:35 -0300
From: Nícolas "F. R. A. Prado" <nfraprado@...labora.com>
To: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>, Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>, Sandy Huang <hjc@...k-chips.com>, Heiko
Stübner <heiko@...ech.de>, Andy Yan
<andy.yan@...k-chips.com>, Louis Chauvet <louis.chauvet@...tlin.com>,
Haneen Mohammed <hamohammed.sa@...il.com>, Melissa Wen
<melissa.srw@...il.com>
Cc: Robert Mader <robert.mader@...labora.com>, kernel@...labora.com,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH v4 3/4] drm/vkms: Support setting custom background color
On Fri, 2025-12-19 at 23:47 +0200, Cristian Ciocaltea wrote:
> Make use of the BACKGROUND_COLOR CRTC property when filling the
> background during blending. It already defaults to solid black.
>
> Since the internal representation of the pixel color in VKMS relies
> on
> 16 bits of precision, use the newly introduced
> DRM_ARGB64_GET{R|G|B}()
> helpers to access the individual components of the background color
> property, which is compliant with DRM_FORMAT_ARGB16161616.
>
> It's worth noting the alpha component is ignored, hence non-opaque
> background colors are not supported.
>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Reviewed-by: Nícolas F. R. A. Prado <nfraprado@...labora.com>
--
Thanks,
Nícolas
Powered by blists - more mailing lists