From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: freedreno@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org, amd-gfx@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
javierm@redhat.com, dri-devel@lists.freedesktop.org,
mripard@kernel.org, daniel@ffwll.ch, linux-tegra@vger.kernel.org,
airlied@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [Intel-gfx] [PATCH v4 11/13] drm/fb-helper: Export helpers for marking damage areas
Date: Mon, 29 May 2023 21:38:51 +0200 [thread overview]
Message-ID: <20230529193851.GF1370714@ravnborg.org> (raw)
In-Reply-To: <20230524092150.11776-12-tzimmermann@suse.de>
On Wed, May 24, 2023 at 11:21:48AM +0200, Thomas Zimmermann wrote:
> Export drm_fb_helper_damage() and drm_fb_helper_damage_range(), which
> handle damage areas for fbdev emulation. This is a temporary export
> that allows to move the DRM I/O helpers for fbdev into drivers. Only
> fbdev-generic and i915 need them. Both will be updated to implement
> damage handling by themselves and the exported functions will be removed.
>
> v4:
> * update interfaces
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Assuming there is a good answer why there is no dirty check:
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
> ---
> drivers/gpu/drm/drm_fb_helper.c | 22 ++++++++++++++++++++++
> include/drm/drm_fb_helper.h | 3 +++
> 2 files changed, 25 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> index f0e9549b6bd7..cb03099fd2e3 100644
> --- a/drivers/gpu/drm/drm_fb_helper.c
> +++ b/drivers/gpu/drm/drm_fb_helper.c
> @@ -670,6 +670,28 @@ static void drm_fb_helper_memory_range_to_clip(struct fb_info *info, off_t off,
> drm_rect_init(clip, x1, y1, x2 - x1, y2 - y1);
> }
>
> +/* Don't use in new code. */
> +void drm_fb_helper_damage_range(struct fb_info *info, off_t off, size_t len)
> +{
> + struct drm_fb_helper *fb_helper = info->par;
> + struct drm_rect damage_area;
> +
> + drm_fb_helper_memory_range_to_clip(info, off, len, &damage_area);
> + drm_fb_helper_damage(fb_helper, damage_area.x1, damage_area.y1,
> + drm_rect_width(&damage_area),
> + drm_rect_height(&damage_area));
> +}
> +EXPORT_SYMBOL(drm_fb_helper_damage_range);
> +
> +/* Don't use in new code. */
> +void drm_fb_helper_damage_area(struct fb_info *info, u32 x, u32 y, u32 width, u32 height)
> +{
> + struct drm_fb_helper *fb_helper = info->par;
> +
> + drm_fb_helper_damage(fb_helper, x, y, width, height);
> +}
> +EXPORT_SYMBOL(drm_fb_helper_damage_area);
> +
> /**
> * drm_fb_helper_deferred_io() - fbdev deferred_io callback function
> * @info: fb_info struct pointer
> diff --git a/include/drm/drm_fb_helper.h b/include/drm/drm_fb_helper.h
> index 72032c354a30..7d5804882be7 100644
> --- a/include/drm/drm_fb_helper.h
> +++ b/include/drm/drm_fb_helper.h
> @@ -253,6 +253,9 @@ void drm_fb_helper_fill_info(struct fb_info *info,
> struct drm_fb_helper *fb_helper,
> struct drm_fb_helper_surface_size *sizes);
>
> +void drm_fb_helper_damage_range(struct fb_info *info, off_t off, size_t len);
> +void drm_fb_helper_damage_area(struct fb_info *info, u32 x, u32 y, u32 width, u32 height);
> +
> void drm_fb_helper_deferred_io(struct fb_info *info, struct list_head *pagereflist);
>
> ssize_t drm_fb_helper_sys_read(struct fb_info *info, char __user *buf,
> --
> 2.40.1
next prev parent reply other threads:[~2023-05-29 19:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 9:21 [Intel-gfx] [PATCH v4 00/13] drm/fbdev: Remove DRM's helpers for fbdev I/O Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 01/13] fbdev: Add Kconfig options to select different fb_ops helpers Thomas Zimmermann
2023-05-24 20:46 ` [Intel-gfx] [v4, " Sui Jingfeng
2023-05-29 19:17 ` [Intel-gfx] [PATCH v4 " Sam Ravnborg
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 02/13] fbdev: Add initializer macros for struct fb_ops Thomas Zimmermann
2023-05-24 20:57 ` [Intel-gfx] [v4, " Sui Jingfeng
2023-05-26 12:38 ` Thomas Zimmermann
2023-05-29 19:23 ` [Intel-gfx] [PATCH v4 " Sam Ravnborg
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 03/13] drm/armada: Use regular fbdev I/O helpers Thomas Zimmermann
2023-05-29 19:24 ` Sam Ravnborg
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 04/13] drm/exynos: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 05/13] drm/gma500: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 06/13] drm/radeon: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 07/13] drm/fbdev-dma: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 08/13] drm/msm: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 09/13] drm/omapdrm: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 10/13] drm/tegra: " Thomas Zimmermann
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 11/13] drm/fb-helper: Export helpers for marking damage areas Thomas Zimmermann
2023-05-29 19:38 ` Sam Ravnborg [this message]
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 12/13] drm/fbdev-generic: Implement dedicated fbdev I/O helpers Thomas Zimmermann
2023-05-24 20:23 ` [Intel-gfx] [v4, " Sui Jingfeng
2023-05-26 12:44 ` Thomas Zimmermann
2023-05-25 2:46 ` Sui Jingfeng
2023-05-24 9:21 ` [Intel-gfx] [PATCH v4 13/13] drm/i915: " Thomas Zimmermann
2023-05-24 21:25 ` [Intel-gfx] [v4, " Sui Jingfeng
2023-05-29 19:36 ` [Intel-gfx] [PATCH v4 " Sam Ravnborg
2023-05-30 4:02 ` Sui Jingfeng
2023-05-30 7:12 ` Thomas Zimmermann
2023-05-30 15:37 ` Sam Ravnborg
2023-05-29 19:41 ` Sam Ravnborg
2023-05-24 19:25 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/fbdev: Remove DRM's helpers for fbdev I/O (rev4) Patchwork
2023-05-24 19:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-05-24 19:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-25 12:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-29 19:37 ` [Intel-gfx] [PATCH v4 00/13] drm/fbdev: Remove DRM's helpers for fbdev I/O Sam Ravnborg
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=20230529193851.GF1370714@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mripard@kernel.org \
--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