LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Archit Taneja <architt@codeaurora.org>
Cc: daniel.vetter@ffwll.ch, robdclark@gmail.com, airlied@linux.ie,
treding@nvidia.com, benjamin.gaignard@linaro.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC 5/6] drm/imx: Remove local fbdev emulation Kconfig option
Date: Tue, 10 Mar 2015 11:54:18 +0100 [thread overview]
Message-ID: <1425984858.3141.37.camel@pengutronix.de> (raw)
In-Reply-To: <1425980493-27533-6-git-send-email-architt@codeaurora.org>
Hi Archit,
thanks for the cleanup!
Am Dienstag, den 10.03.2015, 15:11 +0530 schrieb Archit Taneja:
> DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation for
> the imx kms driver.
>
> Remove this local config option and use the top level DRM_FBDEV_EMULATION config
> option where applicable. Using this config lets us also prevent wrapping around
> drm_fb_helper_* calls with #ifdefs in certain places.
>
> We replace the #ifdef in imx_drm_driver_load with CONFIG_DRM_FBDEV_EMULATION.
> It's probably okay to get remove the #ifdef itself, but just left it here for
> now to be safe. It can be removed after some testing.
>
> Signed-off-by: Archit Taneja <architt@codeaurora.org>
Tested-by: Philipp Zabel <p.zabel@pengutronix.de>
(Both with and without the #ifdef CONFIG_DRM_FBDEV_EMULATION removed.)
Although this is for another patch, I think the legacyfb_depth
module_param should be removed altogether if CONFIG_DRM_FBDEV_EMULATION
is disabled, so maybe that #ifdef should stay.
regards
Philipp
next prev parent reply other threads:[~2015-03-10 10:54 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
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 [this message]
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=1425984858.3141.37.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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=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).