From: Daniel Vetter <daniel@ffwll.ch>
To: "Noralf Trønnes" <noralf@tronnes.org>
Cc: intel-gfx@lists.freedesktop.org,
laurent.pinchart@ideasonboard.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/9] drm: Add generic fbdev emulation
Date: Thu, 24 May 2018 12:17:56 +0200 [thread overview]
Message-ID: <20180524101756.GN3438@phenom.ffwll.local> (raw)
In-Reply-To: <20180523143411.64070-1-noralf@tronnes.org>
On Wed, May 23, 2018 at 04:34:02PM +0200, Noralf Trønnes wrote:
> This patchset adds generic fbdev emulation for drivers that supports GEM
> based dumb buffers which support .gem_prime_vmap and gem_prime_mmap. An
> API is begun to support in-kernel clients in general.
>
> The CMA helper drivers is moved as a whole over to this generic fbdev
> emulation. I've added patches 8 and 9 to show where it's heading.
> tinydrm will be the first driver to use the full emulation when it moves
> to vmalloc buffers. The CMA helper drivers will be converted one by one
> later.
Yeah I think 8&9 are looking like the right direction. I tried to review
them, but I bit harder to form an opinion without patch 10 to start making
use of the new things. But this is all looking really neat.
-Daniel
>
> This work is based on an idea[1] by Laurent Pinchart:
>
> Ideally I'd like to remove 100% of fbdev-related
> code from drivers. This includes
> - initialization and cleanup of fbdev helpers
> - fbdev restore in last_close()
> - forwarding of hotplug events to fbdev compatibility layer
>
> Noralf.
>
> [1] https://lists.freedesktop.org/archives/dri-devel/2017-September/152612.html
>
> David Herrmann (1):
> drm: provide management functions for drm_file
>
> Noralf Trønnes (8):
> drm/file: Don't set master on in-kernel clients
> drm: Make ioctls available for in-kernel clients
> drm: Begin an API for in-kernel clients
> drm/fb-helper: Add generic fbdev emulation .fb_probe function
> drm/pl111: Set .gem_prime_vmap and .gem_prime_mmap
> drm/cma-helper: Use the generic fbdev emulation
> drm/client: Add client callbacks
> drm/fb-helper: Finish the generic fbdev emulation
>
> Documentation/gpu/drm-client.rst | 12 +
> Documentation/gpu/index.rst | 1 +
> drivers/gpu/drm/Makefile | 2 +-
> drivers/gpu/drm/drm_client.c | 511 ++++++++++++++++++++++++++++++++++++
> drivers/gpu/drm/drm_crtc_internal.h | 19 +-
> drivers/gpu/drm/drm_debugfs.c | 7 +
> drivers/gpu/drm/drm_drv.c | 9 +
> drivers/gpu/drm/drm_dumb_buffers.c | 33 ++-
> drivers/gpu/drm/drm_fb_cma_helper.c | 365 ++++----------------------
> drivers/gpu/drm/drm_fb_helper.c | 287 ++++++++++++++++++++
> drivers/gpu/drm/drm_file.c | 304 ++++++++++++---------
> drivers/gpu/drm/drm_framebuffer.c | 42 +--
> drivers/gpu/drm/drm_internal.h | 2 +
> drivers/gpu/drm/drm_ioctl.c | 4 +-
> drivers/gpu/drm/drm_probe_helper.c | 3 +
> drivers/gpu/drm/pl111/pl111_drv.c | 2 +
> include/drm/drm_client.h | 146 +++++++++++
> include/drm/drm_device.h | 21 ++
> include/drm/drm_fb_cma_helper.h | 3 -
> include/drm/drm_fb_helper.h | 33 +++
> 20 files changed, 1322 insertions(+), 484 deletions(-)
> create mode 100644 Documentation/gpu/drm-client.rst
> create mode 100644 drivers/gpu/drm/drm_client.c
> create mode 100644 include/drm/drm_client.h
>
> --
> 2.15.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-05-24 10:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 14:34 [PATCH 0/9] drm: Add generic fbdev emulation Noralf Trønnes
2018-05-23 14:34 ` [PATCH 1/9] drm: provide management functions for drm_file Noralf Trønnes
2018-05-23 14:34 ` [PATCH 2/9] drm/file: Don't set master on in-kernel clients Noralf Trønnes
2018-05-23 14:34 ` [PATCH 3/9] drm: Make ioctls available for " Noralf Trønnes
2018-05-24 8:22 ` Daniel Vetter
2018-05-23 14:34 ` [PATCH 4/9] drm: Begin an API " Noralf Trønnes
2018-05-23 21:45 ` Thomas Hellstrom
2018-05-24 8:32 ` Daniel Vetter
2018-05-24 9:25 ` Thomas Hellstrom
2018-05-24 10:14 ` Daniel Vetter
2018-05-24 16:51 ` Thomas Hellstrom
2018-05-24 8:42 ` Daniel Vetter
2018-05-28 13:26 ` Noralf Trønnes
2018-05-29 7:53 ` Daniel Vetter
2018-05-23 14:34 ` [PATCH 5/9] drm/fb-helper: Add generic fbdev emulation .fb_probe function Noralf Trønnes
2018-05-24 9:16 ` Daniel Vetter
2018-05-24 10:16 ` Daniel Vetter
2018-05-25 12:42 ` Noralf Trønnes
2018-05-29 7:54 ` Daniel Vetter
2018-12-28 20:38 ` Daniel Vetter
2019-01-03 17:06 ` Noralf Trønnes
2019-01-07 10:14 ` Daniel Vetter
2018-05-23 14:34 ` [PATCH 6/9] drm/pl111: Set .gem_prime_vmap and .gem_prime_mmap Noralf Trønnes
2018-05-30 19:04 ` Eric Anholt
2018-05-23 14:34 ` [PATCH 7/9] drm/cma-helper: Use the generic fbdev emulation Noralf Trønnes
2018-05-24 10:16 ` Daniel Vetter
2018-05-23 14:34 ` [PATCH 8/9] drm/client: Add client callbacks Noralf Trønnes
2018-05-24 9:52 ` Daniel Vetter
2018-05-23 14:34 ` [PATCH 9/9] drm/fb-helper: Finish the generic fbdev emulation Noralf Trønnes
2018-05-24 9:57 ` Daniel Vetter
2018-05-24 10:17 ` Daniel Vetter [this message]
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=20180524101756.GN3438@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--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