From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: "Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Louis Chauvet" <louis.chauvet@bootlin.com>,
"Haneen Mohammed" <hamohammed.sa@gmail.com>,
"Melissa Wen" <melissa.srw@gmail.com>
Cc: Robert Mader <robert.mader@collabora.com>,
kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v3 4/4] drm/rockchip: vop2: Support setting custom background color
Date: Fri, 28 Nov 2025 16:46:46 +0800 [thread overview]
Message-ID: <0ed71b8d-5a2e-4213-bd2f-7ba317d1e4cb@rock-chips.com> (raw)
In-Reply-To: <20251118-rk3588-bgcolor-v3-4-a2cc909428ea@collabora.com>
Hello Cristian,
On 11/18/2025 7:52 AM, Cristian Ciocaltea wrote:
> The Rockchip VOP2 display controller allows configuring the background
> color of each video output port.
>
> Since a previous patch introduced the BACKGROUND_COLOR CRTC property,
> which defaults to solid black, make use of it when programming the
> hardware.
>
> Note the maximum precision allowed by the display controller is 10bpc,
> while the alpha component is not supported, hence ignored.
>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
> ---
> drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 13 ++++++++++++-
> drivers/gpu/drm/rockchip/rockchip_drm_vop2.h | 4 ++++
> 2 files changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
> index 498df0ce4680..87110beba366 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.c
> @@ -1554,6 +1554,7 @@ static void vop2_post_config(struct drm_crtc *crtc)
> struct vop2_video_port *vp = to_vop2_video_port(crtc);
> struct vop2 *vop2 = vp->vop2;
> struct drm_display_mode *mode = &crtc->state->adjusted_mode;
> + u64 bgcolor = crtc->state->background_color;
> u16 vtotal = mode->crtc_vtotal;
> u16 hdisplay = mode->crtc_hdisplay;
> u16 hact_st = mode->crtc_htotal - mode->crtc_hsync_start;
> @@ -1599,7 +1600,11 @@ static void vop2_post_config(struct drm_crtc *crtc)
> vop2_vp_write(vp, RK3568_VP_POST_DSP_VACT_INFO_F1, val);
> }
>
> - vop2_vp_write(vp, RK3568_VP_DSP_BG, 0);
> + /* Background color is programmed with 10 bits of precision */
> + val = FIELD_PREP(RK3568_VP_DSP_BG__DSP_BG_RED, DRM_ARGB64_GETR_BPC(bgcolor, 10));
> + val |= FIELD_PREP(RK3568_VP_DSP_BG__DSP_BG_GREEN, DRM_ARGB64_GETG_BPC(bgcolor, 10));
> + val |= FIELD_PREP(RK3568_VP_DSP_BG__DSP_BG_BLUE, DRM_ARGB64_GETB_BPC(bgcolor, 10));
Division is expensive. If we convert a 16 bpc value to 10 bpc using
direct bit-shifts, that is "DRM_ARGB64_GETX(bgcolor) >> 6" will
keep the relative error within 1 compared to DIV_ROUND_CLOSEST().
Should we be concerned about the precision problem here?
> + vop2_vp_write(vp, RK3568_VP_DSP_BG, val);
> }
>
> static int us_to_vertical_line(struct drm_display_mode *mode, int us)
> @@ -1984,6 +1989,10 @@ static int vop2_crtc_state_dump(struct drm_crtc *crtc, struct seq_file *s)
> drm_get_bus_format_name(vcstate->bus_format));
> seq_printf(s, "\toutput_mode[%x]", vcstate->output_mode);
> seq_printf(s, " color_space[%d]\n", vcstate->color_space);
> + seq_printf(s, "\tbackground color (10bpc): r=0x%x g=0x%x b=0x%x\n",
> + DRM_ARGB64_GETR_BPC(cstate->background_color, 10),
> + DRM_ARGB64_GETG_BPC(cstate->background_color, 10),
> + DRM_ARGB64_GETB_BPC(cstate->background_color, 10));
> seq_printf(s, " Display mode: %dx%d%s%d\n",
> mode->hdisplay, mode->vdisplay, interlaced ? "i" : "p",
> drm_mode_vrefresh(mode));
> @@ -2473,6 +2482,8 @@ static int vop2_create_crtcs(struct vop2 *vop2)
> return dev_err_probe(drm->dev, ret,
> "crtc init for video_port%d failed\n", i);
>
> + drm_crtc_attach_background_color_property(&vp->crtc);
> +
> drm_crtc_helper_add(&vp->crtc, &vop2_crtc_helper_funcs);
> if (vop2->lut_regs) {
> const struct vop2_video_port_data *vp_data = &vop2_data->vp[vp->id];
> diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.h b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.h
> index 9124191899ba..37722652844a 100644
> --- a/drivers/gpu/drm/rockchip/rockchip_drm_vop2.h
> +++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop2.h
> @@ -658,6 +658,10 @@ enum dst_factor_mode {
> #define RK3588_VP_CLK_CTRL__DCLK_OUT_DIV GENMASK(3, 2)
> #define RK3588_VP_CLK_CTRL__DCLK_CORE_DIV GENMASK(1, 0)
>
> +#define RK3568_VP_DSP_BG__DSP_BG_RED GENMASK(29, 20)
> +#define RK3568_VP_DSP_BG__DSP_BG_GREEN GENMASK(19, 10)
> +#define RK3568_VP_DSP_BG__DSP_BG_BLUE GENMASK(9, 0)
> +
> #define RK3568_VP_POST_SCL_CTRL__VSCALEDOWN BIT(1)
> #define RK3568_VP_POST_SCL_CTRL__HSCALEDOWN BIT(0)
>
--
Best,
Chaoyi
next prev parent reply other threads:[~2025-11-28 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 23:51 [PATCH v3 0/4] Introduce BACKGROUND_COLOR DRM CRTC property Cristian Ciocaltea
2025-11-17 23:51 ` [PATCH v3 1/4] uapi: Provide DIV_ROUND_CLOSEST() Cristian Ciocaltea
2025-11-17 23:52 ` [PATCH v3 2/4] drm: Add CRTC background color property Cristian Ciocaltea
2025-11-17 23:52 ` [PATCH v3 3/4] drm/vkms: Support setting custom background color Cristian Ciocaltea
2025-11-17 23:52 ` [PATCH v3 4/4] drm/rockchip: vop2: " Cristian Ciocaltea
2025-11-28 8:46 ` Chaoyi Chen [this message]
2025-11-28 9:44 ` Cristian Ciocaltea
2025-11-29 3:49 ` Chaoyi Chen
2025-11-29 9:50 ` Cristian Ciocaltea
2025-11-30 3:01 ` Chaoyi Chen
2025-12-19 22:42 ` Cristian Ciocaltea
2025-12-19 22:33 ` Cristian Ciocaltea
2026-01-07 12:18 ` [PATCH v3 0/4] Introduce BACKGROUND_COLOR DRM CRTC property Diederik de Haas
2026-01-07 17:54 ` Cristian Ciocaltea
2026-01-07 19:37 ` Diederik de Haas
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=0ed71b8d-5a2e-4213-bd2f-7ba317d1e4cb@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=robert.mader@collabora.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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