From: Javier Martinez Canillas <javierm@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Javier Martinez Canillas <javierm@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org
Subject: [PATCH 2/2] drm: Make fbdev emulation depend on FB_CORE instead of FB
Date: Fri, 30 Jun 2023 00:51:04 +0200 [thread overview]
Message-ID: <20230629225113.297512-3-javierm@redhat.com> (raw)
In-Reply-To: <20230629225113.297512-1-javierm@redhat.com>
Now that the fbdev core has been split in FB_CORE and FB, make DRM fbdev
emulation layer to just depend on the former.
This allows to disable the CONFIG_FB option if is not needed, which will
avoid the need to explicitly disable each of the legacy fbdev drivers.
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
---
drivers/gpu/drm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index afb3b2f5f425..6ecb984d213a 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -132,7 +132,7 @@ config DRM_DEBUG_MODESET_LOCK
config DRM_FBDEV_EMULATION
bool "Enable legacy fbdev support for your modesetting driver"
depends on DRM_KMS_HELPER
- depends on FB=y || FB=DRM_KMS_HELPER
+ depends on FB_CORE=y || FB=DRM_KMS_HELPER
select FRAMEBUFFER_CONSOLE if !EXPERT
select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
default y
--
2.41.0
next prev parent reply other threads:[~2023-06-29 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:51 [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation Javier Martinez Canillas
2023-06-29 22:51 ` [PATCH 1/2] fbdev: Split frame buffer support in FB and FB_CORE symbols Javier Martinez Canillas
2023-06-30 9:01 ` Arnd Bergmann
2023-06-30 10:51 ` Javier Martinez Canillas
2023-06-30 11:34 ` Arnd Bergmann
2023-06-30 12:22 ` Javier Martinez Canillas
2023-06-29 22:51 ` Javier Martinez Canillas [this message]
2023-06-30 11:19 ` [PATCH 0/2] Allow disabling all native fbdev drivers and only keeping DRM emulation Thomas Zimmermann
2023-06-30 12:33 ` Javier Martinez Canillas
2023-06-30 12:41 ` Thomas Zimmermann
2023-07-01 19:49 ` Arnd Bergmann
2023-06-30 17:31 ` Andy Shevchenko
2023-06-30 17:38 ` Javier Martinez Canillas
2023-06-30 17:42 ` Andy Shevchenko
2023-06-30 17:43 ` Andy Shevchenko
2023-06-30 20:29 ` Javier Martinez Canillas
2023-07-03 8:21 ` Andy Shevchenko
2023-07-03 8:43 ` Javier Martinez Canillas
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=20230629225113.297512-3-javierm@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®