From: Daniel Vetter <daniel@ffwll.ch>
To: Archit Taneja <architt@codeaurora.org>
Cc: Daniel Vetter <daniel@ffwll.ch>,
Alex Deucher <alexdeucher@gmail.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC 00/21] drm: fb emulation: Step 3: Remove FB_KMS_HELPER config from drivers
Date: Tue, 14 Jul 2015 09:32:14 +0200 [thread overview]
Message-ID: <20150714073214.GZ3736@phenom.ffwll.local> (raw)
In-Reply-To: <55A4ACD7.6020001@codeaurora.org>
On Tue, Jul 14, 2015 at 12:01:51PM +0530, Archit Taneja wrote:
> Hi,
>
> On 07/13/2015 09:07 PM, Daniel Vetter wrote:
> >On Mon, Jul 13, 2015 at 11:30:34AM -0400, Alex Deucher wrote:
> >>On Mon, Jul 13, 2015 at 2:43 AM, Archit Taneja <architt@codeaurora.org> wrote:
> >>>With the top level DRM_FBDEV_EMULATION option, drivers don't need to
> >>>select DRM_FB_KMS_HELPER or other FB related config options in the
> >>>driver.
> >>>
> >>>Even if FBDEV_EMULATION isn't select, the stubbed out versions of
> >>>the drm_fb_helper functions will be called.
> >>>
> >>>There are some drivers which still need some FB stuff even after
> >>>these changes. They are qxl, udl and nouveau. These are handled a bit
> >>>differently compared to the other patches.
> >>
> >>Series is:
> >>Acked-by: Alex Deucher <alexander.deucher@amd.com>
> >
> >Archit for merging I think I'll just keep the current set of patches I
> >have for testing (well until there's a real bug discovered). Can you
> >please collect all the acks/r-bs/t-d when resending so I don't have to
> >digg them out when we merge the final versions of these?
> >
>
> Sure. I'll keep a track of this.
>
> Speaking of bugs, there was one thing I noticed in the series which I
> am not sure about.
>
> One of the new helpers wraps around framebuffer_alloc(). Most drivers
> tend to pass the drm_device's dev pointer to this, and this is what I
> do in the helper too.
>
> But some drivers(nouveau, radeon, qxl and some more) pass their
> pci_dev's dev pointer.
Hm, didn't even notice that one.
> Looking at the framebuffer code, it looks like the 'dev' we pass to
> framebuffer_alloc is what is used as the parent device when
> creating a fb device.
>
> After this patch set, all drivers will use drm_device's dev when
> calling framebuffer_alloc. I was wondering if this could cause any
> fbcon issues?
I think it won't matter, this is just about discovering the fbdev instance
in sysfs. And all the legacy users that do care about fbdev device nodes
don't really use that anyway.
And I think conceptually it also makes more sense to have the emulated
fbdev device as a child of the kms device.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2015-07-14 7:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:43 [RFC 00/21] drm: fb emulation: Step 3: Remove FB_KMS_HELPER config from drivers Archit Taneja
2015-07-13 6:43 ` [RFC 01/21] drm/cirrus: Remove FB_KMS_HELPER and FB related config options Archit Taneja
2015-07-13 6:43 ` [RFC 02/21] drm/rockchip: " Archit Taneja
2015-07-13 6:43 ` [RFC 03/21] drm/armada: " Archit Taneja
2015-07-13 6:43 ` [RFC 04/21] drm/ast: " Archit Taneja
2015-07-13 6:43 ` [RFC 05/21] drm/omap: " Archit Taneja
2015-08-01 10:02 ` Laurent Pinchart
2015-08-05 7:04 ` Archit Taneja
2015-07-13 6:43 ` [RFC 06/21] drm/exynos: " Archit Taneja
2015-07-13 6:43 ` [RFC 07/21] drm/gma500: " Archit Taneja
2015-07-13 6:43 ` [RFC 08/21] drm/mgag200: " Archit Taneja
2015-07-13 6:43 ` [RFC 09/21] drm/radeon: " Archit Taneja
2015-07-13 6:43 ` [RFC 10/21] drm/qxl: " Archit Taneja
2015-07-13 7:38 ` Daniel Vetter
2015-07-13 6:43 ` [RFC 11/21] drm/nouveau: " Archit Taneja
2015-07-13 6:43 ` [RFC 12/21] drm/udl: " Archit Taneja
2015-07-13 6:44 ` [RFC 13/21] drm/bochs: " Archit Taneja
2015-07-13 6:44 ` [RFC 14/21] drm/amdgpu: " Archit Taneja
2015-07-13 6:44 ` [RFC 15/21] drm/virtio: " Archit Taneja
2015-07-13 6:44 ` [RFC 16/21] drm/fb_cma_helper: " Archit Taneja
2015-07-13 6:44 ` [RFC 17/21] drm/atmel-hlcdc: Remove FB_KMS_HELPER config option Archit Taneja
2015-07-13 6:44 ` [RFC 18/21] drm/imx: " Archit Taneja
2015-07-13 6:44 ` [RFC 19/21] drm/rcar-du: " Archit Taneja
2015-08-01 10:02 ` Laurent Pinchart
2015-07-13 6:44 ` [RFC 20/21] drm/shmobile: " Archit Taneja
2015-08-01 10:02 ` Laurent Pinchart
2015-07-13 6:44 ` [RFC 21/21] drm/tilcdc: " Archit Taneja
2015-07-13 15:30 ` [RFC 00/21] drm: fb emulation: Step 3: Remove FB_KMS_HELPER config from drivers Alex Deucher
2015-07-13 15:37 ` Daniel Vetter
2015-07-14 6:31 ` Archit Taneja
2015-07-14 7:32 ` Daniel Vetter [this message]
2015-07-14 8:02 ` Thierry Reding
2015-07-14 8:23 ` 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=20150714073214.GZ3736@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alexdeucher@gmail.com \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
/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