drm/armada: fbdev: Use client buffers
Subsystems (2)
cover drm/armada: fbdev: Use client buffers
A client buffer holds the DRM framebuffer for an in-kernel DRM client. Until now, armada created an internal ad-hoc framebuffer for its fbdev emulation, while by-passing the regular interfaces used by user-space compositors.
Convert armada's fbdev emulation to use client buffers. Replacing the existing code with a client buffer allows for stream-lining armada code and later also the fbdev helpers. The new framebuffer will be registered against the client's file and will support handles for GEM objects. It is then just another framebuffer within the DRM ecosystem.
If all driver's fbdev-emulation helpers can be converted to use client buffers, the emulation's framebuffer handling as a whole can possibly be moved into shared helpers.
Patches 1 and 2 convert armada's fbdev emulation to client buffers. It still allocates a GEM object buffer tailored towards fbdev emulation, but size calculations now use common DRM helpers.
Patch 3 cleans up symbol visibility in armada's fb code.
Thomas Zimmermann (3):
drm/armada: fbdev: Calculate buffer geometry with format helpers drm/armada: fbdev: Use a DRM client buffer
drm/armada: Make armada_framebuffer_create() an internal interface
drivers/gpu/drm/armada/armada_fb.c | 9 ++-- drivers/gpu/drm/armada/armada_fb.h | 3 -- drivers/gpu/drm/armada/armada_fbdev.c | 76 +++++++++++++++------------ 3 files changed, 48 insertions(+), 40 deletions(-)
Signature · 1 line
2.53.0
PATCH 1/3 drm/armada: fbdev: Calculate buffer geometry with format helpers
Replace the geometry and size calculation in armada's fbdev emulation with DRM format helpers. This consists of a 4CC lookup from the fbdev parameters, format lookup, pitch calculation and size calculation.
Then allocate the GEM buffer object for the framebuffer memory from the calculated size. Mmap provides the allocated buffer to user space, so align the buffer size to PAGE_SIZE.
Slightly rearrange cleaning up the GEM object and rolling back on errors. This will simplify error handling when the code uses client buffers.
--- drivers/gpu/drm/armada/armada_fbdev.c | 55 ++++++++++++++------------- 1 file changed, 29 insertions(+), 26 deletions(-)
drivers/gpu/drm/armada/armada_fbdev.c +29 -26
@@ -45,20 +45,20 @@ int armada_fbdev_driver_fbdev_probe(struct drm_fb_helper *fbh, {struct drm_device *dev = fbh->dev;struct fb_info *info = fbh->info; +u32 fourcc, pitch; +u64 size; +const struct drm_format_info *format;struct drm_mode_fb_cmd2 mode;struct armada_framebuffer *dfb;struct armada_gem_object *obj; -int size, ret; +int ret;void *ptr; -memset (&mode,0 ,sizeof (mode)); - mode.width = sizes->surface_width; - mode.height = sizes->surface_height; - mode.pitches[0 ] =armada_pitch (mode.width, sizes->surface_bpp); - mode.pixel_format =drm_mode_legacy_fb_format (sizes->surface_bpp, - sizes->surface_depth); + fourcc =drm_mode_legacy_fb_format (sizes->surface_bpp, sizes->surface_depth); + format =drm_get_format_info (dev, fourcc,DRM_FORMAT_MOD_LINEAR ); + pitch =armada_pitch (sizes->surface_width,drm_format_info_bpp (format,0 )); + size =ALIGN (pitch * sizes->surface_height,PAGE_SIZE ); - size = mode.pitches[0 ] * mode.height; obj =armada_gem_alloc_private_object (dev, size);if (!obj) {DRM_ERROR ("failed to allocate fb memory\n" );
@@ -66,30 +66,26 @@ int armada_fbdev_driver_fbdev_probe(struct drm_fb_helper *fbh, } ret =armada_gem_linear_back (dev, obj); -if (ret) { -drm_gem_object_put (&obj->obj); -return ret; - } +if (ret) + goto err_drm_gem_object_put; ptr =armada_gem_map_object (dev, obj);if (!ptr) { -drm_gem_object_put (&obj->obj); -return -ENOMEM ; + ret = -ENOMEM ; + goto err_drm_gem_object_put; } - dfb =armada_framebuffer_create (dev, -drm_get_format_info (dev, mode.pixel_format, - mode.modifier[0 ]), - &mode, obj); - -/* -* A reference is now held by the framebuffer object if -* successful, otherwise this drops the ref for the error path. -*/ -drm_gem_object_put (&obj->obj); +memset (&mode,0 ,sizeof (mode)); + mode.width = sizes->surface_width; + mode.height = sizes->surface_height; + mode.pitches[0 ] = pitch; + mode.pixel_format = fourcc; -if (IS_ERR (dfb)) -return PTR_ERR (dfb); + dfb =armada_framebuffer_create (dev, format, &mode, obj); +if (IS_ERR (dfb)) { + ret =PTR_ERR (dfb); + goto err_drm_gem_object_put; + } info->fbops = &armada_fb_ops; info->fix.smem_start = obj->phys_addr;
@@ -105,5 +101,12 @@ int armada_fbdev_driver_fbdev_probe(struct drm_fb_helper *fbh, dfb->fb.width, dfb->fb.height, dfb->fb.format->cpp[0 ] *8 , (unsigned long long)obj->phys_addr); +/* The framebuffer still holds a reference on the GEM object. */ +drm_gem_object_put (&obj->obj); +return 0 ; + +err_drm_gem_object_put: +drm_gem_object_put (&obj->obj); +return ret; }
Signature · 1 line
2.53.0
PATCH 2/3 drm/armada: fbdev: Use a DRM client buffer
In reply to Thomas ZimmermannReplace the internal DRM framebuffer with a DRM client buffer. The client buffer allocates the DRM framebuffer on a file and also uses GEM object handles via the regular ADDFB2 interfaces.
Using client-buffer interfaces unifies framebuffer allocation for DRM clients in user space and armada's internal fbdev emulation. It also simplifies the clean-up side of the fbdev emulation.
--- drivers/gpu/drm/armada/armada_fbdev.c | 41 ++++++++++++++++----------- 1 file changed, 24 insertions(+), 17 deletions(-)
drivers/gpu/drm/armada/armada_fbdev.c +24 -17
@@ -26,8 +26,7 @@ static void armada_fbdev_fb_destroy(struct fb_info *info)drm_fb_helper_fini (fbh); - fbh->fb->funcs->destroy (fbh->fb); - +drm_client_buffer_delete (fbh->buffer);drm_client_release (&fbh->client); }
@@ -43,14 +42,16 @@ static const struct drm_fb_helper_funcs armada_fbdev_helper_funcs;int armada_fbdev_driver_fbdev_probe (struct drm_fb_helper *fbh,struct drm_fb_helper_surface_size *sizes) { -struct drm_device *dev = fbh->dev; +struct drm_client_dev *client = &fbh->client; +struct drm_device *dev = client->dev; +struct drm_file *file = client->file;struct fb_info *info = fbh->info;u32 fourcc, pitch;u64 size;const struct drm_format_info *format; -struct drm_mode_fb_cmd2 mode; -struct armada_framebuffer *dfb;struct armada_gem_object *obj; +struct drm_client_buffer *buffer; +u32 handle;int ret;void *ptr;
@@ -75,37 +76,43 @@ int armada_fbdev_driver_fbdev_probe(struct drm_fb_helper *fbh, goto err_drm_gem_object_put; } -memset (&mode,0 ,sizeof (mode)); - mode.width = sizes->surface_width; - mode.height = sizes->surface_height; - mode.pitches[0 ] = pitch; - mode.pixel_format = fourcc; - - dfb =armada_framebuffer_create (dev, format, &mode, obj); -if (IS_ERR (dfb)) { - ret =PTR_ERR (dfb); + ret =drm_gem_handle_create (file, &obj->obj, &handle); +if (ret) goto err_drm_gem_object_put; + + buffer =drm_client_buffer_create (client, sizes->surface_width, sizes->surface_height, + fourcc, handle, pitch); +if (IS_ERR (buffer)) { + ret =PTR_ERR (buffer); + goto err_drm_gem_handle_delete; } + fbh->funcs = &armada_fbdev_helper_funcs; + fbh->buffer = buffer; + fbh->fb = buffer->fb; + info->fbops = &armada_fb_ops; info->fix.smem_start = obj->phys_addr; info->fix.smem_len = obj->obj.size; info->screen_size = obj->obj.size; info->screen_base = ptr; - fbh->funcs = &armada_fbdev_helper_funcs; - fbh->fb = &dfb->fb;drm_fb_helper_fill_info (info, fbh, sizes);DRM_DEBUG_KMS ("allocated %dx%d %dbpp fb: 0x%08llx\n" , - dfb->fb.width, dfb->fb.height, dfb->fb.format->cpp[0 ] *8 , + buffer->fb->width, buffer->fb->height, buffer->fb->format->cpp[0 ] *8 , (unsigned long long )obj->phys_addr); +/* The handle is only needed for creating the framebuffer. */ +drm_gem_handle_delete (file, handle); +/* The framebuffer still holds a reference on the GEM object. */ drm_gem_object_put (&obj->obj);return 0 ; +err_drm_gem_handle_delete: +drm_gem_handle_delete (file, handle); err_drm_gem_object_put:drm_gem_object_put (&obj->obj);return ret;
Signature · 1 line
2.53.0
PATCH 3/3 drm/armada: Make armada_framebuffer_create() an internal interface
In reply to Thomas ZimmermannThe only caller of armada_framebuffer_create() is armada_fb_create() from the same source file. Declare the former as static.
--- drivers/gpu/drm/armada/armada_fb.c | 9 +++++---- drivers/gpu/drm/armada/armada_fb.h | 3 --- 2 files changed, 5 insertions(+), 7 deletions(-)
drivers/gpu/drm/armada/armada_fb.c +5 -4
@@ -18,10 +18,11 @@ static const struct drm_framebuffer_funcs armada_fb_funcs = { .create_handle = drm_gem_fb_create_handle, }; -struct armada_framebuffer *armada_framebuffer_create (struct drm_device *dev, -const struct drm_format_info *info, -const struct drm_mode_fb_cmd2 *mode, -struct armada_gem_object *obj) +static struct armada_framebuffer * +armada_framebuffer_create (struct drm_device *dev, +const struct drm_format_info *info, +const struct drm_mode_fb_cmd2 *mode, +struct armada_gem_object *obj) {struct armada_framebuffer *dfb;uint8_t format, config;
drivers/gpu/drm/armada/armada_fb.h +0 -3
@@ -16,9 +16,6 @@ struct armada_framebuffer { container_of(dfb, struct armada_framebuffer, fb)#define drm_fb_obj (fb) drm_to_armada_gem((fb)->obj[0]) -struct armada_framebuffer *armada_framebuffer_create (struct drm_device *, -const struct drm_format_info *info, -const struct drm_mode_fb_cmd2 *,struct armada_gem_object *);struct drm_framebuffer *armada_fb_create (struct drm_device *dev,struct drm_file *dfile,const struct drm_format_info *info,const struct drm_mode_fb_cmd2 *mode);
Signature · 1 line
2.53.0