LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Archit Taneja <architt@codeaurora.org>
Cc: robdclark@gmail.com, airlied@linux.ie, treding@nvidia.com,
	p.zabel@pengutronix.de, benjamin.gaignard@linaro.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, daniel@ffwll.ch,
	daniel.vetter@ffwll.ch
Subject: Re: [RFC 1/6] drm: Add top level Kconfig option for DRM fbdev emulation
Date: Tue, 10 Mar 2015 11:05:47 +0100	[thread overview]
Message-ID: <20150310100547.GG3800@phenom.ffwll.local> (raw)
In-Reply-To: <54FEBEF1.5000103@codeaurora.org>

On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
> 
> 
> On 03/10/2015 03:17 PM, Daniel Vetter wrote:
> >On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
> >>Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
> >>Most modesetting drivers enable provide fbdev emulation by default by selecting
> >>KMS FB helpers. A few provide a separate Kconfig option for the user to enable
> >>or disbale fbdev emulation.
> >>
> >>Enabling fbdev emulation is finally a distro-level decision. Having a top level
> >>Kconfig option for fbdev emulation helps by providing a uniform way to
> >>enable/disable fbdev emulation for any modesetting driver. It also lets us
> >>remove unnecessary driver specific Kconfig options that causes bloat.
> >>
> >>With a top level Kconfig in place, we can stub out the fb helper functions when
> >>not needed without breaking functionality. Having stub functions also prevents
> >>drivers to require wrapping fb helper function calls with #ifdefs.
> >>
> >>DRM_FBDEV_EMULATION defaults to y since many drivers enable fbdev emulation by
> >>default and majority of distributions expect the fbdev interface in the kernel.
> >>
> >>For now, this config selects both FB_SYS_* and FB_CFB_* configs as some
> >>modesetting drivers use the former and other the later. This needs to be taken
> >>care of in a better way.
> >>
> >>Signed-off-by: Archit Taneja <architt@codeaurora.org>
> >>---
> >>  drivers/gpu/drm/Kconfig     |  18 +++++++
> >>  drivers/gpu/drm/Makefile    |   4 ++
> >>  include/drm/drm_fb_helper.h | 120 ++++++++++++++++++++++++++++++++++++++++++++
> >>  3 files changed, 142 insertions(+)
> >>
> >>diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
> >>index 151a050..38f83a0 100644
> >>--- a/drivers/gpu/drm/Kconfig
> >>+++ b/drivers/gpu/drm/Kconfig
> >>@@ -40,6 +40,24 @@ config DRM_KMS_FB_HELPER
> >>  	help
> >>  	  FBDEV helpers for KMS drivers.
> >>
> >>+config DRM_FBDEV_EMULATION
> >>+	bool "Enable legacy fbdev support for your modesetting driver"
> >>+	depends on DRM
> >>+	select DRM_KMS_HELPER
> >>+	select DRM_KMS_FB_HELPER
> >>+	select FB_SYS_FILLRECT
> >>+	select FB_SYS_COPYAREA
> >>+	select FB_SYS_IMAGEBLIT
> >>+	select FB_SYS_FOPS
> >>+	select FB_CFB_FILLRECT
> >>+	select FB_CFB_COPYAREA
> >>+	select FB_CFB_IMAGEBLIT
> >>+	default y
> >>+	help
> >>+	  Choose this option if you have a need for the legacy fbdev
> >>+	  support. Note that this support also provide the linux console
> >>+	  support on top of your modesetting driver.
> >
> >Maybe clarify that for linux console support you also need
> >CONFIG_FRAMEBUFFER_CONSOLE? fbdev alone isn't enough.
> 
> DRM_KMS_FB_HELPER selects that for us, right?

Hm right I've missed that. Reminds me that you need one more patch at the
end to remove all the various select DRM_KMS_FB_HELPER from all drm
drivers. Otherwise this knob here won't work by default if you e.g. select
radeon. In general we can't mix explicit options with menu entries with a
select.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2015-03-10 10:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10  9:41 [RFC 0/6] drm: Add DRM_FBDEV_EMULATION Kconfig option Archit Taneja
2015-03-10  9:41 ` [RFC 1/6] drm: Add top level Kconfig option for DRM fbdev emulation Archit Taneja
2015-03-10  9:46   ` Daniel Vetter
2015-03-10  9:54     ` Archit Taneja
2015-03-10  9:47   ` Daniel Vetter
2015-03-10  9:52     ` Archit Taneja
2015-03-10 10:05       ` Daniel Vetter [this message]
2015-03-10 10:22         ` Archit Taneja
2015-03-10 12:17           ` Daniel Vetter
2015-03-11  8:21             ` Archit Taneja
2015-03-11 15:17               ` Daniel Vetter
2015-03-13  6:25                 ` Archit Taneja
2015-03-13  9:06                   ` Daniel Vetter
2015-03-13  9:46                     ` Jani Nikula
2015-03-13 11:00                     ` Archit Taneja
2015-03-25  8:17                     ` Archit Taneja
2015-03-25  9:21                       ` Daniel Vetter
2015-06-30  7:10                         ` Daniel Vetter
2015-06-30  7:56                           ` Archit Taneja
2015-06-30  8:31                             ` Benjamin Gaignard
2015-06-30  9:04                               ` Daniel Vetter
2015-07-03 12:32                                 ` Thierry Reding
2015-07-03 13:33                                   ` Rob Clark
2015-06-30  9:06                               ` Archit Taneja
2015-03-10 15:33           ` Jani Nikula
2015-03-11  4:57             ` Archit Taneja
2015-03-10  9:41 ` [RFC 2/6] drm/msm: Remove local fbdev emulation Kconfig option Archit Taneja
2015-03-10  9:41 ` [RFC 3/6] drm/i915: " Archit Taneja
2015-03-10 10:01   ` Daniel Vetter
2015-03-10 10:10     ` Archit Taneja
2015-03-10  9:41 ` [RFC 4/6] drm/tegra: " Archit Taneja
2015-03-10  9:41 ` [RFC 5/6] drm/imx: " Archit Taneja
2015-03-10 10:54   ` Philipp Zabel
2015-03-11  4:53     ` Archit Taneja
2015-03-10  9:41 ` [RFC 6/6] drm/sti: " Archit Taneja

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=20150310100547.GG3800@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=architt@codeaurora.org \
    --cc=benjamin.gaignard@linaro.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robdclark@gmail.com \
    --cc=treding@nvidia.com \
    /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;
as well as URLs for NNTP newsgroup(s).