public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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, mripard@kernel.org,
	dri-devel@lists.freedesktop.org, daniel@ffwll.ch,
	linux-tegra@vger.kernel.org, airlied@gmail.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [Intel-gfx] [PATCH 00/11] drm/fbdev: Remove DRM's helpers for fbdev I/O
Date: Fri, 12 May 2023 15:41:20 +0200	[thread overview]
Message-ID: <20230512134120.GA1395037@ravnborg.org> (raw)
In-Reply-To: <4cc261d7-ddcd-e1a2-1067-7b8c44e7769d@suse.de>

Hi Thomas,
> > 
> > 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 wasn't too happy about this solution either as it is quite verbose. But I
> don't want to rely on the linker either. It certainly cannot remove exported
> symbols.
I forgot about exported symbols - that makes the idea futile.

> 
> But the pattern is very common among the fbdev drivers. We could introduce
> common Kconfig options in fbdev and selcet those instead. Like this:
> 
> const FB_IO_HELPERS
> 	bool
> 	depends on FB
> 	select FB_CFB_COPYAREA
> 	select FB_CFB_FILLRECT
> 	select FB_CFB_IMAGEBLIT
> 
> const FB_SYS_HELPERS
> 	bool
> 	depends on FB
> 	select FB_SYS_COPYAREA
> 	select FB_SYS_FILLRECT
> 	select FB_SYS_FOPS
> 	select FB_SYS_IMAGEBLIT
> 
> Apart from DRM, most of the fbdev drivers could use these as well.
That's a much nicer way to express it - and with this we do not introduce
the IMO confusing CFB (Color Frame Buffer) abbreviation in every driver.

	Sam

      reply	other threads:[~2023-05-12 13:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  8:41 [Intel-gfx] [PATCH 00/11] drm/fbdev: Remove DRM's helpers for fbdev I/O Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 01/11] drm/armada: Use regular fbdev I/O helpers Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 02/11] drm/exynos: " Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 03/11] drm/gma500: " Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 04/11] drm/radeon: " Thomas Zimmermann
2023-05-12 13:55   ` Deucher, Alexander
2023-05-12  8:41 ` [Intel-gfx] [PATCH 05/11] drm/fbdev-dma: " Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 06/11] drm/msm: " Thomas Zimmermann
2023-05-12  9:45   ` Dmitry Baryshkov
2023-05-12  8:41 ` [Intel-gfx] [PATCH 07/11] drm/omapdrm: " Thomas Zimmermann
2023-05-12 16:20   ` kernel test robot
2023-05-12  8:41 ` [Intel-gfx] [PATCH 08/11] drm/tegra: " Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 09/11] drm/fb-helper: Export helpers for marking damage areas Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 10/11] drm/fbdev-generic: Implement dedicated fbdev I/O helpers Thomas Zimmermann
2023-05-12  8:41 ` [Intel-gfx] [PATCH 11/11] drm/i915: " Thomas Zimmermann
2023-05-12  9:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/fbdev: Remove DRM's helpers for fbdev I/O Patchwork
2023-05-12  9:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-05-12 10:29 ` [Intel-gfx] [PATCH 00/11] " Sam Ravnborg
2023-05-12 11:49   ` Thomas Zimmermann
2023-05-12 13:41     ` Sam Ravnborg [this message]

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=20230512134120.GA1395037@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