From: Thomas Zimmermann <tzimmermann@suse.de>
To: sashiko-reviews@lists.linux.dev
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm/fbdev: Move fbdev helpers into client library
Date: Thu, 24 Sep 2026 12:46:27 +0200 [thread overview]
Message-ID: <80a93244-dc29-49c2-b4bc-1133d0443443@suse.de> (raw)
In-Reply-To: <20260924094332.14F311F000FF@smtp.kernel.org>
Am 24.09.26 um 11:43 schrieb sashiko-bot@kernel.org:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] drm: missing DRM_CLIENT_LIB selection in memory helpers causes linker error
> --
>
> commit b0f3c606cfc59f0c56cd9be7e3349abc72f97a64
> Author: Thomas Zimmermann <tzimmermann@suse.de>
>
> drm/fbdev: Move fbdev helpers into client library
>
> DRM's fbdev helpers are for the fbdev-emulation clients. Move them
> into the client-library module. Fix include statements throughout
> DRM drivers.
>
>> diff --git a/drivers/gpu/drm/clients/Makefile b/drivers/gpu/drm/clients/Makefile
>> index c16addbc327f0..1304ff358509d 100644
>> --- a/drivers/gpu/drm/clients/Makefile
>> +++ b/drivers/gpu/drm/clients/Makefile
>> @@ -4,5 +4,6 @@ subdir-ccflags-y += -I$(src)/..
>>
>> drm_client_lib-y := drm_client_setup.o
>> drm_client_lib-$(CONFIG_DRM_CLIENT_LOG) += drm_log.o
>> -drm_client_lib-$(CONFIG_DRM_FBDEV_EMULATION) += drm_fbdev_client.o
>> +drm_client_lib-$(CONFIG_DRM_FBDEV_EMULATION) += drm_fbdev_client.o \
>> + drm_fbdev_helper.o
> [Severity: Low]
> Since drm_fbdev_helper.o is now built into drm_client_lib, can this cause a
> linker error for built-in memory helpers?
>
> If CONFIG_DRM_FBDEV_EMULATION=y and a driver selects DRM_GEM_DMA_HELPER=y,
> but CONFIG_DRM_CLIENT_SELECTION=m (selected only by modular drivers),
> drm_client_lib.ko will be built as a module while drm_fbdev_dma.o becomes
> built-in.
>
> This would lead to undefined references to fbdev helper functions (e.g.,
> drm_fb_helper_fini) during vmlinux linkage.
>
> Do the memory helpers in drivers/gpu/drm/Kconfig (DRM_GEM_DMA_HELPER,
> DRM_GEM_SHMEM_HELPER, DRM_TTM_HELPER) need to explicitly select
> DRM_CLIENT_LIB when DRM_FBDEV_EMULATION is enabled to prevent this?
To answer that question: yes they do. And I forgot that they already do
the same for DRM_KMS_HELPER because of this dependency. [1] The
KMS-helper rule simply needs to be replaced with the client-lib. The
memory managers do not use the three module parameters that remain in
drm_kms_helper.ko . No need for a dependency there.
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Stefan Gaiser, Jochen Jaser, Abhinav Puri, (HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2026-09-24 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 9:29 [PATCH v2 0/2] drm/fbdev: Move helpers to clients/ subdirectory Thomas Zimmermann
2026-09-24 9:29 ` [PATCH v2 1/2] drm/fbdev: Move fbdev module parameters next to module init Thomas Zimmermann
2026-09-24 9:29 ` [PATCH v2 2/2] drm/fbdev: Move fbdev helpers into client library Thomas Zimmermann
2026-09-24 9:43 ` sashiko-bot
2026-09-24 10:46 ` Thomas Zimmermann [this message]
2026-09-24 9:38 ` ✗ CI.checkpatch: warning for drm/fbdev: Move helpers to clients/ subdirectory (rev2) Patchwork
2026-09-24 9:40 ` ✓ CI.KUnit: success " Patchwork
2026-09-24 11:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-25 0:22 ` ✗ Xe.CI.FULL: failure " Patchwork
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=80a93244-dc29-49c2-b4bc-1133d0443443@suse.de \
--to=tzimmermann@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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