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.
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 | 192 ++++++++++++++----------------
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, 113 insertions(+), 133 deletions(-)
--
2.51.0
