From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/8] drm/fb-helper: Use drm_file to get a dumb framebuffer
Date: Wed, 13 Sep 2017 08:09:56 +0300 [thread overview]
Message-ID: <53775807.sLI70s7jcq@avalon> (raw)
In-Reply-To: <1505140322-17416-1-git-send-email-noralf@tronnes.org>
Hi Noralf,
Thank you for the patches.
On Monday, 11 September 2017 17:31:54 EEST Noralf Trønnes wrote:
> Hi,
>
> I want to start out by saying that this patchset is low priority for me
> and if no one has interest or time to review this, that is just fine. I
> was in the flow and just typed it out.
>
> This patchset adds a way for fbdev emulation code to create a
> framebuffer that is backed by a dumb buffer. drm_fb_helper gets a
> drm_file to hang the objects on, drm_framebuffer_create_dumb() creates
> the framebuffer and drm_fb_helper_fini() destroys it.
> I have verified that all cma drivers supports dumb buffers, so
> converting the library should be fine for all.
Stupid question, what does this give us ? The series makes the call stack more
complex (up to a point where I'm getting trouble just following it), what's
the advantage that offsets that ?
With the exception of vmwgfx that does weird things I won't even try to
understand, all drivers seem to use the drm_file object passed to the
.dumb_create() operation just to register the GEM object handle. I wonder
whether a better solution to use .dumb_create() for framebuffer emulation
wouldn't be to move the GEM object handle registration from the .dumb_create()
implementation to its caller in the core.
> A patch by David Herrmann from a year ago made this easy. It was the
> last piece in his work to make it possible to create a drm_file for
> in-kernel use, but it never got merged.
>
> I've cc'ed intel-gfx since that will give CI runs of the core patches if
> I understood Daniel right.
>
> Noralf.
>
> David Herrmann (1):
> drm: provide management functions for drm_file
>
> Noralf Trønnes (7):
> drm/framebuffer: Add drm_framebuffer_create_dumb()
> drm/auth: Export drm_dropmaster_ioctl()
> drm/fb-helper: Allocate a drm_file
> drm/fb-cma-helper: Use drm_framebuffer_create_dumb()
> drm/fb-cma-helper: Drop unnecessary fbdev buffer offset
> drm/tinydrm: Use drm_fbdev_cma_init()
> drm/fb-cma-helper: Remove drm_fbdev_cma_init_with_funcs()
>
> drivers/gpu/drm/drm_auth.c | 1 +
> drivers/gpu/drm/drm_fb_cma_helper.c | 111 ++--------
> drivers/gpu/drm/drm_fb_helper.c | 22 +-
> drivers/gpu/drm/drm_file.c | 323 +++++++++++++++----------
> drivers/gpu/drm/drm_framebuffer.c | 61 ++++++
> drivers/gpu/drm/drm_internal.h | 2 -
> drivers/gpu/drm/tinydrm/core/tinydrm-core.c | 5 +-
> include/drm/drm_auth.h | 2 +
> include/drm/drm_fb_helper.h | 9 +
> include/drm/drm_file.h | 2 +
> include/drm/drm_framebuffer.h | 4 +
> 11 files changed, 305 insertions(+), 237 deletions(-)
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-13 5:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 14:31 [PATCH 0/8] drm/fb-helper: Use drm_file to get a dumb framebuffer Noralf Trønnes
2017-09-11 14:31 ` [PATCH 1/8] drm: provide management functions for drm_file Noralf Trønnes
2017-09-11 14:31 ` [PATCH 2/8] drm/framebuffer: Add drm_framebuffer_create_dumb() Noralf Trønnes
2017-09-11 14:31 ` [PATCH 3/8] drm/auth: Export drm_dropmaster_ioctl() Noralf Trønnes
2017-09-11 14:31 ` [PATCH 4/8] drm/fb-helper: Allocate a drm_file Noralf Trønnes
2017-09-17 1:40 ` [lkp-robot] [drm/fb] a583bc678d: WARNING:at_kernel/workqueue.c:#flush_workqueue kernel test robot
2017-09-11 14:31 ` [PATCH 5/8] drm/fb-cma-helper: Use drm_framebuffer_create_dumb() Noralf Trønnes
2017-09-11 14:32 ` [PATCH 6/8] drm/fb-cma-helper: Drop unnecessary fbdev buffer offset Noralf Trønnes
2017-09-11 14:32 ` [PATCH 7/8] drm/tinydrm: Use drm_fbdev_cma_init() Noralf Trønnes
2017-09-11 14:32 ` [PATCH 8/8] drm/fb-cma-helper: Remove drm_fbdev_cma_init_with_funcs() Noralf Trønnes
2017-09-11 14:51 ` ✓ Fi.CI.BAT: success for drm/fb-helper: Use drm_file to get a dumb framebuffer Patchwork
2017-09-11 18:39 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-13 5:09 ` Laurent Pinchart [this message]
2017-09-13 15:19 ` [PATCH 0/8] " Noralf Trønnes
2017-09-14 22:29 ` Laurent Pinchart
2017-09-15 16:37 ` Noralf Trønnes
2017-09-16 12:37 ` Noralf Trønnes
2017-09-16 14:45 ` Noralf Trønnes
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=53775807.sLI70s7jcq@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=noralf@tronnes.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