Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: simona@ffwll.ch, airlied@gmail.com, javierm@redhat.com,
	jfalempe@redhat.com
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 0/5] drm: Introduce DRM client library
Date: Fri, 27 Sep 2024 16:37:25 +0200	[thread overview]
Message-ID: <20240927144252.31813-1-tzimmermann@suse.de> (raw)

With the next DRM client coming soon (drm_log) and most of DRM's
fbdev emulation consolidated in a few places, it's time to provide
a single place for the clients.

The new module drm_client_lib.ko stores most of the common client
code. It's designed such that drivers can opt into client support,
but the presence of the client module depends on the user's kernel
configuration. Without selected clients, no client module will be
build.

Thomas Zimmermann (5):
  drm/i915: Select DRM_CLIENT_SELECTION
  drm/xe: Select DRM_CLIENT_SELECTION
  drm: Move client-device functions in to drm_client_dev.c
  drm: Select fbdev helpers for modules that require them
  drm: Add client-lib module

 Documentation/gpu/drm-client.rst   |   3 +
 drivers/gpu/drm/Kconfig            |  34 +++++--
 drivers/gpu/drm/Makefile           |  20 +++--
 drivers/gpu/drm/amd/amdgpu/Kconfig |   1 +
 drivers/gpu/drm/drm_client.c       | 122 +------------------------
 drivers/gpu/drm/drm_client_dev.c   | 138 +++++++++++++++++++++++++++++
 drivers/gpu/drm/drm_dumb_buffers.c |   2 +
 drivers/gpu/drm/drm_file.c         |   2 +
 drivers/gpu/drm/drm_framebuffer.c  |   2 +
 drivers/gpu/drm/drm_gem.c          |   2 +
 drivers/gpu/drm/i915/Kconfig       |   1 +
 drivers/gpu/drm/xe/Kconfig         |   1 +
 12 files changed, 196 insertions(+), 132 deletions(-)
 create mode 100644 drivers/gpu/drm/drm_client_dev.c

-- 
2.46.0


             reply	other threads:[~2024-09-27 14:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 14:37 Thomas Zimmermann [this message]
2024-09-27 14:37 ` [PATCH 1/5] drm/i915: Select DRM_CLIENT_SELECTION Thomas Zimmermann
2024-09-27 14:37 ` [PATCH 2/5] drm/xe: " Thomas Zimmermann
2024-09-27 14:37 ` [PATCH 3/5] drm: Move client-device functions in to drm_client_dev.c Thomas Zimmermann
2024-09-30 11:49   ` Jocelyn Falempe
2024-09-27 14:37 ` [PATCH 4/5] drm: Select fbdev helpers for modules that require them Thomas Zimmermann
2024-09-30 11:49   ` Jocelyn Falempe
2024-09-27 14:37 ` [PATCH 5/5] drm: Add client-lib module Thomas Zimmermann
2024-09-30 11:55   ` Jocelyn Falempe
2024-09-30 11:56     ` Jocelyn Falempe
2024-09-27 16:19 ` ✓ CI.Patch_applied: success for drm: Introduce DRM client library Patchwork
2024-09-27 16:19 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-27 16:20 ` ✓ CI.KUnit: success " Patchwork
2024-09-27 16:26 ` ✗ CI.Build: failure " Patchwork
2024-09-27 19:27 ` [PATCH 0/5] " Felix Kuehling
2024-09-30  6:19   ` Thomas Zimmermann
2024-09-30 11:46 ` Jocelyn Falempe
2024-09-30 12:27   ` Thomas Zimmermann

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=20240927144252.31813-1-tzimmermann@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=jfalempe@redhat.com \
    --cc=simona@ffwll.ch \
    /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