public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@gmail.com, simona@ffwll.ch,
	dri-devel@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org,
	freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	imx@lists.linux.dev, linux-samsung-soc@vger.kernel.org,
	nouveau@lists.freedesktop.org, virtualization@lists.linux.dev,
	spice-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org,
	linux-rockchip@lists.infradead.org, linux-tegra@vger.kernel.org,
	intel-xe@lists.freedesktop.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 02/25] drm/dumb-buffers: Provide helper to set pitch and size
Date: Wed, 19 Feb 2025 09:08:53 +0100	[thread overview]
Message-ID: <c011ec88-3b68-486b-9fda-ef18a0906c8e@suse.de> (raw)
In-Reply-To: <CAMuHMdV939ibJTRSaO-oW2Jz4zbkXGRpUYrmA7e=yQfF7W-k_g@mail.gmail.com>

Hi

Am 18.02.25 um 20:32 schrieb Geert Uytterhoeven:
[...]
>> +                                args->bpp);
>> +                       fallthrough;
>> +               case 12:
>> +               case 15:
>> +               case 30: /* see drm_gem_afbc_get_bpp() */
>> +               case 10:
> Perhaps keep them sorted numerically?

The first block comes from the afbc helper; the second block from Mesa; 
hence the odd order. I'll reorder and comment each case individually.

>
>> +               case 64: /* used by Mesa */
>> +                       pitch = args->width * DIV_ROUND_UP(args->bpp, SZ_8);
>> +                       break;
>> +               }
>> +       }
>> +
>> +       if (!pitch || pitch > U32_MAX)
>> +               return -EINVAL;
>> +
>> +       args->pitch = pitch;
>> +
>> +       return drm_mode_align_dumb(args, pitch_align, size_align);
>> +}
>> +EXPORT_SYMBOL(drm_mode_size_dumb);
>> +
>>   int drm_mode_create_dumb(struct drm_device *dev,
>>                           struct drm_mode_create_dumb *args,
>>                           struct drm_file *file_priv)
>> diff --git a/include/drm/drm_dumb_buffers.h b/include/drm/drm_dumb_buffers.h
>> new file mode 100644
>> index 000000000000..6fe36004b19d
>> --- /dev/null
>> +++ b/include/drm/drm_dumb_buffers.h
>> @@ -0,0 +1,14 @@
>> +/* SPDX-License-Identifier: MIT */
>> +
>> +#ifndef __DRM_DUMB_BUFFERS_H__
>> +#define __DRM_DUMB_BUFFERS_H__
>> +
>> +struct drm_device;
>> +struct drm_mode_create_dumb;
>> +
>> +int drm_mode_size_dumb(struct drm_device *dev,
>> +                      struct drm_mode_create_dumb *args,
>> +                      unsigned long pitch_align,
>> +                      unsigned long size_align);
>> +
>> +#endif
>> diff --git a/include/uapi/drm/drm_mode.h b/include/uapi/drm/drm_mode.h
>> index c082810c08a8..eea09103b1a6 100644
>> --- a/include/uapi/drm/drm_mode.h
>> +++ b/include/uapi/drm/drm_mode.h
>> @@ -1058,7 +1058,7 @@ struct drm_mode_crtc_page_flip_target {
>>    * struct drm_mode_create_dumb - Create a KMS dumb buffer for scanout.
>>    * @height: buffer height in pixels
>>    * @width: buffer width in pixels
>> - * @bpp: bits per pixel
>> + * @bpp: color mode
>>    * @flags: must be zero
>>    * @handle: buffer object handle
>>    * @pitch: number of bytes between two consecutive lines
>> @@ -1066,6 +1066,50 @@ struct drm_mode_crtc_page_flip_target {
>>    *
>>    * User-space fills @height, @width, @bpp and @flags. If the IOCTL succeeds,
>>    * the kernel fills @handle, @pitch and @size.
>> + *
>> + * The value of @bpp is a color-mode number describing a specific format
>> + * or a variant thereof. The value often corresponds to the number of bits
>> + * per pixel for most modes, although there are exceptions. Each color mode
>> + * maps to a DRM format plus a number of modes with similar pixel layout.
>> + * Framebuffer layout is always linear.
>> + *
>> + * Support for all modes and formats is optional. Even if dumb-buffer
>> + * creation with a certain color mode succeeds, it is not guaranteed that
>> + * the DRM driver supports any of the related formats. Most drivers support
>> + * a color mode of 32 with a format of DRM_FORMAT_XRGB8888 on their primary
>> + * plane.
>> + *
>> + * +------------+------------------------+------------------------+
>> + * | Color mode | Framebuffer format     | Compatibles            |
>> + * +============+========================+========================+
>> + * |     32     |  * DRM_FORMAT_XRGB8888 |  * DRM_FORMAT_XBGR8888 |
>> + * |            |                        |  * DRM_FORMAT_RGBX8888 |
>> + * |            |                        |  * DRM_FORMAT_BGRX8888 |
>> + * +------------+------------------------+------------------------+
>> + * |     24     |  * DRM_FORMAT_RGB888   |  * DRM_FORMAT_BGR888   |
>> + * +------------+------------------------+------------------------+
>> + * |     16     |  * DRM_FORMAT_RGB565   |  * DRM_FORMAT_BGR565   |
>> + * +------------+------------------------+------------------------+
>> + * |     15     |  * DRM_FORMAT_XRGB1555 |  * DRM_FORMAT_XBGR1555 |
>> + * |            |                        |  * DRM_FORMAT_RGBX1555 |
>> + * |            |                        |  * DRM_FORMAT_BGRX1555 |
>> + * +------------+------------------------+------------------------+
>> + * |      8     |  * DRM_FORMAT_C8       |  * DRM_FORMAT_R8       |
> + DRM_FORMAT_D8? (and 4/2/1 below)

Right, missed that.

>
> And DRM_FORMAT_Y8, if/when Tomi's series introducing that is accepted...

Sure, if it is compatible, it can also go into the third column.

Best regards
Thomas

>
>> + * +------------+------------------------+------------------------+
>> + * |      4     |  * DRM_FORMAT_C4       |  * DRM_FORMAT_R4       |
>> + * +------------+------------------------+------------------------+
>> + * |      2     |  * DRM_FORMAT_C2       |  * DRM_FORMAT_R2       |
>> + * +------------+------------------------+------------------------+
>> + * |      1     |  * DRM_FORMAT_C1       |  * DRM_FORMAT_R1       |
>> + * +------------+------------------------+------------------------+
>> + *
>> + * Color modes of 10, 12, 15, 30 and 64 are only supported for use by
>> + * legacy user space. Please don't use them in new code. Other modes
>> + * are not support.
>> + *
>> + * Do not attempt to allocate anything but linear framebuffer memory
>> + * with single-plane RGB data. Allocation of other framebuffer
>> + * layouts requires dedicated ioctls in the respective DRM driver.
>>    */
>>   struct drm_mode_create_dumb {
>>          __u32 height;
> Gr{oetje,eeting}s,
>
>                          Geert
>

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  reply	other threads:[~2025-02-19  8:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 14:23 [PATCH v3 00/25] drm/dumb-buffers: Fix and improve buffer-size calculation Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 01/25] drm/dumb-buffers: Sanitize output on errors Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 02/25] drm/dumb-buffers: Provide helper to set pitch and size Thomas Zimmermann
2025-02-18 19:32   ` Geert Uytterhoeven
2025-02-19  8:08     ` Thomas Zimmermann [this message]
2025-02-20  9:18   ` Tomi Valkeinen
2025-02-20 10:05     ` Thomas Zimmermann
2025-02-20 10:53       ` Tomi Valkeinen
2025-02-21  9:19         ` Thomas Zimmermann
2025-02-21  9:57           ` Geert Uytterhoeven
2025-02-21 10:08             ` Thomas Zimmermann
2025-02-25 13:45           ` Tomi Valkeinen
2025-02-26 10:16             ` Thomas Zimmermann
2025-03-07  8:42   ` Simona Vetter
2025-03-07 13:19     ` Simona Vetter
2025-02-18 14:23 ` [PATCH v3 03/25] drm/gem-dma: Compute dumb-buffer sizes with drm_mode_size_dumb() Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 04/25] drm/gem-shmem: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 05/25] drm/gem-vram: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 06/25] drm/armada: " Thomas Zimmermann
2025-02-18 15:57   ` Russell King (Oracle)
2025-02-19  8:09     ` Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 07/25] drm/exynos: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 08/25] drm/gma500: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 09/25] drm/hibmc: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 10/25] drm/imx/ipuv3: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 11/25] drm/loongson: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 12/25] drm/mediatek: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 13/25] drm/msm: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 14/25] drm/nouveau: " Thomas Zimmermann
2025-02-20 22:17   ` Lyude Paul
2025-02-18 14:23 ` [PATCH v3 15/25] drm/omapdrm: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 16/25] drm/qxl: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 17/25] drm/renesas/rcar-du: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 18/25] drm/renesas/rz-du: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 19/25] drm/rockchip: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 20/25] drm/tegra: " Thomas Zimmermann
2025-03-06 19:26   ` Thierry Reding
2025-02-18 14:23 ` [PATCH v3 21/25] drm/virtio: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 22/25] drm/vmwgfx: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 23/25] drm/xe: " Thomas Zimmermann
2025-02-20 10:08   ` Matthew Auld
2025-02-18 14:23 ` [PATCH v3 24/25] drm/xen: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 25/25] drm/xlnx: " 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=c011ec88-3b68-486b-9fda-ef18a0906c8e@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=imx@lists.linux.dev \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=simona@ffwll.ch \
    --cc=spice-devel@lists.freedesktop.org \
    --cc=virtualization@lists.linux.dev \
    --cc=xen-devel@lists.xenproject.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