From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Daniel Stone <daniels@collabora.com>
Subject: [PATCH 0/5] drm/uapi: Intoduce DRM_MODE_DUMB_CURSOR
Date: Tue, 21 Oct 2025 22:44:50 +0300 [thread overview]
Message-ID: <20251021194455.24297-1-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Currently DRM_IOCTL_MODE_CREATE_DUMB isn't really suitable for
allocating buffers for cursor planes (at least on Intel GPUs).
Introduce a new DRM_MODE_DUMB_CURSOR flag for
DRM_IOCTL_MODE_CREATE_DUMB so that userspace can tell us that
it wants a dumb buffer for a cursor plane. And implement support
fot the new flag in i915.
This is more of an RFC at this point to see what people think.
I haven't done any userspace changes yet. Figured I'd gauge
the general interest first...
Cc: Daniel Stone <daniels@collabora.com>
Ville Syrjälä (5):
drm/uapi: Validate DRM_IOCTL_MODE_CREATE_DUMB flags
drm/uapi: Introduce the DRM_MODE_DUMB_CURSOR flag
drm/i915/dumb: Move the display dumb buffer stuff into the display
code
drm/i915/dumb: Reject dumb buffer that exceed max fb dimensions
drm/i915/dumb: Handle DRM_MODE_DUMB_CURSOR
drivers/gpu/drm/drm_dumb_buffers.c | 2 +
drivers/gpu/drm/i915/display/intel_cursor.c | 38 ++++++++++++++
drivers/gpu/drm/i915/display/intel_cursor.h | 3 ++
drivers/gpu/drm/i915/display/intel_display.c | 11 ++++
drivers/gpu/drm/i915/display/intel_display.h | 3 ++
drivers/gpu/drm/i915/display/intel_plane.c | 39 ++++++++++++++
drivers/gpu/drm/i915/display/intel_plane.h | 4 ++
drivers/gpu/drm/i915/gem/i915_gem_create.c | 55 ++++++++++----------
include/uapi/drm/drm_mode.h | 4 +-
9 files changed, 130 insertions(+), 29 deletions(-)
--
2.49.1
next reply other threads:[~2025-10-21 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 19:44 Ville Syrjala [this message]
2025-10-21 19:44 ` [PATCH 1/5] drm/uapi: Validate DRM_IOCTL_MODE_CREATE_DUMB flags Ville Syrjala
2025-10-21 19:44 ` [PATCH 2/5] drm/uapi: Introduce the DRM_MODE_DUMB_CURSOR flag Ville Syrjala
2025-10-21 19:44 ` [PATCH 3/5] drm/i915/dumb: Move the display dumb buffer stuff into the display code Ville Syrjala
2025-10-21 19:44 ` [PATCH 4/5] drm/i915/dumb: Reject dumb buffer that exceed max fb dimensions Ville Syrjala
2025-10-21 19:44 ` [PATCH 5/5] drm/i915/dumb: Handle DRM_MODE_DUMB_CURSOR Ville Syrjala
2025-10-21 19:51 ` ✗ CI.checkpatch: warning for drm/uapi: Intoduce DRM_MODE_DUMB_CURSOR Patchwork
2025-10-21 19:52 ` ✓ CI.KUnit: success " Patchwork
2025-10-21 20:07 ` ✗ CI.checksparse: warning " Patchwork
2025-10-21 20:31 ` ✓ Xe.CI.BAT: success " Patchwork
2025-10-21 23:07 ` ✓ Xe.CI.Full: " Patchwork
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=20251021194455.24297-1-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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