From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: daniel@ffwll.ch, airlied@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
javierm@redhat.com, linux-samsung-soc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-tegra@vger.kernel.org, freedreno@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/11] drm/fbdev: Remove DRM's helpers for fbdev I/O
Date: Fri, 12 May 2023 12:29:54 +0200 [thread overview]
Message-ID: <20230512102954.GA1373384@ravnborg.org> (raw)
In-Reply-To: <20230512084152.31233-1-tzimmermann@suse.de>
Hi Thomas,
On Fri, May 12, 2023 at 10:41:41AM +0200, Thomas Zimmermann wrote:
> DRM provides a number of wrappers around fbdev cfb_() sys_(), fb_io_()
> and fb_sys_() helpers. The DRM functions don't provide any additional
> functionality for most DRM drivers. So remove them and call the fbdev
> I/O helpers directly.
>
> The DRM fbdev I/O wrappers were originally added because <linux/fb.h>
> does not protect its content with CONFIG_FB. DRM fbdev emulation did
> not build if the the config option had been disabled. This has been
> fixed. For fbdev-generic and i915, the wrappers added support for damage
> handling. But this is better handled within the two callers, as each
> is special in its damage handling.
>
> Patches 1 to 8 replace the DRM wrappers in a number of fbdev emulations.
> Patch 9 exports two helpers for damage handling. Patches 10 and 11
> update fbdev-generic and i915 with the help of the exported functions.
> The patches also remove DRM's fbdev I/O helpers, which are now unused.
>
> DRM's fbdev helpers had to select fbdev I/O helpers for I/O and for
> system memory. Each fbdev emulation now selects the correct helpers
> for itself. Depending on the selected DRM drivers, kernel builds will
> now only contain the necessary fbdev I/O helpers and might be slightly
> smaller in size.
Nice cleanup.
From one of the patches:
> +config DRM_ARMADA_FBDEV_EMULATION
> + bool
> + depends on DRM_ARMADA
> + select FB_CFB_COPYAREA
> + select FB_CFB_FILLRECT
> + select FB_CFB_IMAGEBLIT
This seems like a hard to maintain way to select a few helper functions.
Today we have LD_DEAD_CODE_DATA_ELIMINATION for the configs that care
about size - and that should work here as well.
I understand where this comes from and I am not against the
solution, but wanted to point at a more modern approach to deal with the
bloat.
Maybe some of the embbedded folks can tell if LD_DEAD_CODE_DATA_ELIMINATION
can be trusted yet or that is something for the future.
In barebox -ffunction-section (what LD_DEAD_CODE_DATA_ELIMINATION
enables) is used with success - there it really helps when generating
different barebox images where size matters a lot.
Sam
next prev parent reply other threads:[~2023-05-12 10:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 8:41 [PATCH 00/11] drm/fbdev: Remove DRM's helpers for fbdev I/O Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 01/11] drm/armada: Use regular fbdev I/O helpers Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 02/11] drm/exynos: " Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 03/11] drm/gma500: " Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 04/11] drm/radeon: " Thomas Zimmermann
2023-05-12 13:55 ` Deucher, Alexander
2023-05-12 8:41 ` [PATCH 05/11] drm/fbdev-dma: " Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 06/11] drm/msm: " Thomas Zimmermann
2023-05-12 9:45 ` Dmitry Baryshkov
2023-05-12 8:41 ` [PATCH 07/11] drm/omapdrm: " Thomas Zimmermann
2023-05-12 16:20 ` [Intel-gfx] " kernel test robot
2023-05-12 8:41 ` [PATCH 08/11] drm/tegra: " Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 09/11] drm/fb-helper: Export helpers for marking damage areas Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 10/11] drm/fbdev-generic: Implement dedicated fbdev I/O helpers Thomas Zimmermann
2023-05-12 8:41 ` [PATCH 11/11] drm/i915: " Thomas Zimmermann
2023-05-12 10:29 ` Sam Ravnborg [this message]
2023-05-12 11:49 ` [PATCH 00/11] drm/fbdev: Remove DRM's helpers for fbdev I/O Thomas Zimmermann
2023-05-12 13:41 ` 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=20230512102954.GA1373384@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=maarten.lankhorst@linux.intel.com \
--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