All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Valla <francesco@valla.it>
To: jfalempe@redhat.com, javierm@redhat.com, rrameshbabu@nvidia.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@gmail.com, Thomas Zimmermann <tzimmermann@suse.de>
Cc: dri-devel@lists.freedesktop.org, Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v2 0/7] drm/client: Simply client-buffer interface and implementation
Date: Tue, 28 Oct 2025 18:22:35 +0100	[thread overview]
Message-ID: <2663948.XAFRqVoOGU@fedora> (raw)
In-Reply-To: <20251027121042.143588-1-tzimmermann@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

Hi Thomas,

On Monday, 27 October 2025 at 13:09:11 Thomas Zimmermann <tzimmermann@suse.de> wrote:
> Streamline the client-buffer code and remove the drm_client_framebuffer_
> functions. Makes the code easier to work with.
> 
> Also prepares for importing non-dumb-buffer objects. Most of the in-
> kernel clients will use dumb-buffer allocation. In the case of the
> per-driver fbdev_probe code, the client buffer can also wrap an object
> that comes from a different memory region; for example gma500's stolen
> memory area. This functionality is required to move forward with the
> various per-driver implementations of fbdev_probe within the overall
> DRM-client framework.
> 
> Tested with efidrm and virtio-gpu on Virt I/O hardware.
> 
> v2:
> - fix possible NULL-pointer deref in delete
> - avoid dependency on KMS helpers
> 
> Thomas Zimmermann (7):
>   drm/client: Remove pitch from struct drm_client_buffer
>   drm/client: Move dumb-buffer handling to
>     drm_client_framebuffer_create()
>   drm/client: Inline drm_client_buffer_addfb() and _rmfb()
>   drm/client: Deprecate struct drm_client_buffer.gem
>   drm/client: Remove drm_client_framebuffer_delete()
>   drm/client: Create client buffers with drm_client_buffer_create_dumb()
>   drm/client: Flush client buffers with drm_client_buffer_sync()
> 
>  drivers/gpu/drm/clients/drm_log.c |  10 +-
>  drivers/gpu/drm/drm_client.c      | 193 ++++++++++++++----------------
>  drivers/gpu/drm/drm_fbdev_dma.c   |   8 +-
>  drivers/gpu/drm/drm_fbdev_shmem.c |   6 +-
>  drivers/gpu/drm/drm_fbdev_ttm.c   |  10 +-
>  include/drm/drm_client.h          |  20 +---
>  6 files changed, 114 insertions(+), 133 deletions(-)
> 
> 
> base-commit: c03916cb446b6eefe91538599775bb54bf98238c
> 

Tested-by: Francesco Valla <francesco@valla.it>

Tested on a NXP i.MX93 FRDM.


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2025-10-28 17:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 12:09 [PATCH v2 0/7] drm/client: Simply client-buffer interface and implementation Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 1/7] drm/client: Remove pitch from struct drm_client_buffer Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 2/7] drm/client: Move dumb-buffer handling to drm_client_framebuffer_create() Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 3/7] drm/client: Inline drm_client_buffer_addfb() and _rmfb() Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 4/7] drm/client: Deprecate struct drm_client_buffer.gem Thomas Zimmermann
2025-10-31 15:49   ` [REGRESSION][ASAN] " Ian Forbes
2025-11-03 12:15     ` Thomas Zimmermann
2025-11-04 10:52     ` Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 5/7] drm/client: Remove drm_client_framebuffer_delete() Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 6/7] drm/client: Create client buffers with drm_client_buffer_create_dumb() Thomas Zimmermann
2025-10-27 12:09 ` [PATCH v2 7/7] drm/client: Flush client buffers with drm_client_buffer_sync() Thomas Zimmermann
2025-10-27 14:24   ` Jocelyn Falempe
2025-10-28 17:22 ` Francesco Valla [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=2663948.XAFRqVoOGU@fedora \
    --to=francesco@valla.it \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=jfalempe@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rrameshbabu@nvidia.com \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.