From: Thomas Zimmermann <tzimmermann@suse.de>
To: Chen-Yu Tsai <wenst@chromium.org>, Liu Ying <victor.liu@nxp.com>,
Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>,
Lucas Stach <l.stach@pengutronix.de>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej@kernel.org>,
Samuel Holland <samuel@sholland.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
linux-sunxi@lists.linux.dev, imx@lists.linux.dev,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH RFT v2 1/5] drm: Split framebuffer pixel offset calculation from drm_fb_dma_get_gem_addr()
Date: Thu, 17 Sep 2026 17:20:44 +0200 [thread overview]
Message-ID: <f6ace486-70d8-4e81-89cb-e9d55ad9ac8b@suse.de> (raw)
In-Reply-To: <20260916033327.3054126-2-wenst@chromium.org>
Hi
Am 16.09.26 um 05:33 schrieb Chen-Yu Tsai:
> Currently drm_fb_dma_get_gem_addr() calculates the offset into the
> framebuffer memory for the framebuffer's unclipped source coordinates,
> adds that to the framebuffer's backing storage, and returns the result.
>
> We are about to add a variant that uses the clipped source coordinates,
> so there is already some reuse of code. However, calculating the data
> offset for a given pixel is not specific to the DMA FB helpers. The
> offset is only related to the framebuffer.
>
> Split out the offset calculation into a new framebuffer helper so that
> non-DMA users can also reuse the same code.
>
> Suggested-by: Thomas Zimmermann <tzimmermann@suse.de>
> Cc: <stable@vger.kernel.org> # dependency for next patch
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> ---
> Changes since v1:
> - New patch
> ---
> drivers/gpu/drm/drm_fb_dma_helper.c | 28 ++----------------
> drivers/gpu/drm/drm_framebuffer.c | 45 +++++++++++++++++++++++++++++
> include/drm/drm_framebuffer.h | 3 ++
> 3 files changed, 51 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_fb_dma_helper.c b/drivers/gpu/drm/drm_fb_dma_helper.c
> index fd71969d2fb1..ab0f37d8a5ff 100644
> --- a/drivers/gpu/drm/drm_fb_dma_helper.c
> +++ b/drivers/gpu/drm/drm_fb_dma_helper.c
> @@ -75,36 +75,14 @@ dma_addr_t drm_fb_dma_get_gem_addr(struct drm_framebuffer *fb,
> unsigned int plane)
> {
> struct drm_gem_dma_object *obj;
> - dma_addr_t dma_addr;
> - u8 h_div = 1, v_div = 1;
> - u32 block_w = drm_format_info_block_width(fb->format, plane);
> - u32 block_h = drm_format_info_block_height(fb->format, plane);
> - u32 block_size = fb->format->char_per_block[plane];
> - u32 sample_x;
> - u32 sample_y;
> - u32 block_start_y;
> - u32 num_hblocks;
>
> obj = drm_fb_dma_get_gem_obj(fb, plane);
> if (!obj)
> return 0;
>
> - dma_addr = obj->dma_addr + fb->offsets[plane];
> -
> - if (plane > 0) {
> - h_div = fb->format->hsub;
> - v_div = fb->format->vsub;
> - }
> -
> - sample_x = (state->src_x >> 16) / h_div;
> - sample_y = (state->src_y >> 16) / v_div;
> - block_start_y = (sample_y / block_h) * block_h;
> - num_hblocks = sample_x / block_w;
> -
> - dma_addr += fb->pitches[plane] * block_start_y;
> - dma_addr += block_size * num_hblocks;
> -
> - return dma_addr;
> + return obj->dma_addr + drm_framebuffer_get_block_offset(fb, plane,
> + state->src_x >> 16,
> + state->src_y >> 16);
> }
> EXPORT_SYMBOL_GPL(drm_fb_dma_get_gem_addr);
>
> diff --git a/drivers/gpu/drm/drm_framebuffer.c b/drivers/gpu/drm/drm_framebuffer.c
> index d32aceb6ca9b..9e1231162047 100644
> --- a/drivers/gpu/drm/drm_framebuffer.c
> +++ b/drivers/gpu/drm/drm_framebuffer.c
> @@ -1208,6 +1208,51 @@ void drm_framebuffer_print_info(struct drm_printer *p, unsigned int indent,
> }
> }
>
> +/**
> + * drm_framebuffer_get_block_offset() - Get offset to start of pixel block for
> + * the given framebuffer and coordinates.
> + * @fb: The framebuffer
> + * @plane: Which plane
> + * @x: x coordinate for pixel
> + * @y: y coordinate for pixel
> + *
> + * This function will usually be called from the PLANE callback functions,
> + * or from one of the helpers that calculates the framebuffer's DMA address.
> + *
> + * Return: offset from start of framebuffer to start of pixel block
> + */
> +u32 drm_framebuffer_get_block_offset(struct drm_framebuffer *fb, unsigned int plane,
> + unsigned int x, unsigned int y)
Better use u64 as return type.
> +{
> + u8 h_div = 1, v_div = 1;
> + u32 block_w = drm_format_info_block_width(fb->format, plane);
> + u32 block_h = drm_format_info_block_height(fb->format, plane);
> + u32 block_size = fb->format->char_per_block[plane];
> + u32 sample_x;
> + u32 sample_y;
> + u32 block_start_y;
> + u32 num_hblocks;
> + u32 offset;
> +
> + offset = fb->offsets[plane];
> +
> + if (plane > 0) {
> + h_div = fb->format->hsub;
> + v_div = fb->format->vsub;
> + }
> +
> + sample_x = x / h_div;
> + sample_y = y / v_div;
> + block_start_y = (sample_y / block_h) * block_h;
> + num_hblocks = sample_x / block_w;
> +
> + offset += fb->pitches[plane] * block_start_y;
> + offset += block_size * num_hblocks;
User space controls the values in fb->offsets and fb->pitches. I'm not
sure how well they have been validated already at this point. Did you
investigate this?
Best regards
Thomas
> +
> + return offset;
> +}
> +EXPORT_SYMBOL(drm_framebuffer_get_block_offset);
> +
> #ifdef CONFIG_DEBUG_FS
> static int drm_framebuffer_info(struct seq_file *m, void *data)
> {
> diff --git a/include/drm/drm_framebuffer.h b/include/drm/drm_framebuffer.h
> index 38b24fc8978d..c07aea1cc59f 100644
> --- a/include/drm/drm_framebuffer.h
> +++ b/include/drm/drm_framebuffer.h
> @@ -220,6 +220,9 @@ void drm_framebuffer_remove(struct drm_framebuffer *fb);
> void drm_framebuffer_cleanup(struct drm_framebuffer *fb);
> void drm_framebuffer_unregister_private(struct drm_framebuffer *fb);
>
> +u32 drm_framebuffer_get_block_offset(struct drm_framebuffer *fb, unsigned int plane,
> + unsigned int x, unsigned int y);
> +
> /**
> * drm_framebuffer_get - acquire a framebuffer reference
> * @fb: DRM framebuffer
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2026-09-17 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 3:33 [PATCH RFT v2 0/5] drm: Add and use drm_fb_dma_get_gem_clipped_addr() helper Chen-Yu Tsai
2026-09-16 3:33 ` [PATCH RFT v2 1/5] drm: Split framebuffer pixel offset calculation from drm_fb_dma_get_gem_addr() Chen-Yu Tsai
2026-09-17 15:20 ` Thomas Zimmermann [this message]
2026-09-18 4:16 ` Chen-Yu Tsai
2026-09-18 6:41 ` Thomas Zimmermann
2026-09-18 7:06 ` Chen-Yu Tsai
2026-09-18 7:17 ` Chen-Yu Tsai
2026-09-16 3:33 ` [PATCH RFT v2 2/5] drm/fb-dma-helper: Add drm_fb_dma_get_gem_clipped_addr() Chen-Yu Tsai
2026-09-16 3:33 ` [PATCH RFT v2 3/5] drm/sun4i: layers: Fix VI buffer address for clipped offsets Chen-Yu Tsai
2026-09-16 3:33 ` [PATCH RFT v2 4/5] drm/imx/dc: plane: Switch to drm_fb_dma_get_gem_clipped_addr() Chen-Yu Tsai
2026-09-16 3:33 ` [PATCH RFT v2 5/5] drm/imx/dcss: " Chen-Yu Tsai
2026-09-17 11:15 ` [PATCH RFT v2 0/5] drm: Add and use drm_fb_dma_get_gem_clipped_addr() helper Icenowy Zheng
2026-09-17 11:42 ` Chen-Yu Tsai
2026-09-17 11:51 ` Icenowy Zheng
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=f6ace486-70d8-4e81-89cb-e9d55ad9ac8b@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=jernej@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=samuel@sholland.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=victor.liu@nxp.com \
--cc=wens@kernel.org \
--cc=wenst@chromium.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®