linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Paalanen <pekka.paalanen@haloniitty.fi>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Vishal Sagar <vishal.sagar@amd.com>,
	Anatoliy Klymenko <anatoliy.klymenko@amd.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Michal Simek <michal.simek@amd.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH v4 03/11] drm/fourcc: Add DRM_FORMAT_Y8
Date: Thu, 27 Mar 2025 11:20:46 +0200	[thread overview]
Message-ID: <20250327112009.6b4dc430@eldfell> (raw)
In-Reply-To: <b195971c-52e6-463e-a440-83dde4346e65@ideasonboard.com>

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

On Wed, 26 Mar 2025 15:55:18 +0200
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> wrote:

> Hi,
> 
> On 26/03/2025 15:52, Geert Uytterhoeven wrote:
> > Hi Tomi,
> > 
> > On Wed, 26 Mar 2025 at 14:23, Tomi Valkeinen
> > <tomi.valkeinen@ideasonboard.com> wrote:  
> >> Add greyscale Y8 format.
> >>
> >> Acked-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> >> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>  
> > 
> > Thanks for your patch!
> >   
> >> --- a/include/uapi/drm/drm_fourcc.h
> >> +++ b/include/uapi/drm/drm_fourcc.h
> >> @@ -405,6 +405,9 @@ extern "C" {
> >>   #define DRM_FORMAT_YUV444      fourcc_code('Y', 'U', '2', '4') /* non-subsampled Cb (1) and Cr (2) planes */
> >>   #define DRM_FORMAT_YVU444      fourcc_code('Y', 'V', '2', '4') /* non-subsampled Cr (1) and Cb (2) planes */
> >>
> >> +/* Greyscale formats */
> >> +
> >> +#define DRM_FORMAT_Y8          fourcc_code('G', 'R', 'E', 'Y')  /* 8-bit Y-only */  
> > 
> > This format differs from e.g. DRM_FORMAT_R8, which encodes
> > the number of bits in the FOURCC format. What do you envision
> > for e.g. DRM_FORMAT_Y16? fourcc_code('G', 'R', '1', '6')?  
> 
> I wanted to use the same fourcc as on V4L2 side. Strictly speaking it's 
> not required, but different fourccs for the same formats do confuse.
> 
> So, generally speaking, I'd pick an existing fourcc from v4l2 side if 
> possible, and if not, invent a new one.

Hi Tomi,

what's the actual difference between DRM_FORMAT_R8 and DRM_FORMAT_Y8?

Is the difference that when R8 gets expanded to RGB, it becomes (R, 0,
0), but Y8 gets expanded to (c1 * Y, c2 * Y, c3 * Y) where c1..c3 are
defined by MatrixCoefficients (H.273 terminology)?

That would be my intuitive assumption following how YCbCr is handled.
Is it obvious enough, or should there be a comment to that effect?


Thanks,
pq

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-03-27  9:22 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 13:22 [PATCH v4 00/11] drm: Add new pixel formats for Xilinx Zynqmp Tomi Valkeinen
2025-03-26 13:22 ` [PATCH v4 01/11] drm/fourcc: Add warning for bad bpp Tomi Valkeinen
2025-03-26 13:22 ` [PATCH v4 02/11] drm/fourcc: Add DRM_FORMAT_XV15/XV20 Tomi Valkeinen
2025-03-27 22:34   ` Laurent Pinchart
2025-03-28 10:05     ` Tomi Valkeinen
2025-03-28 10:27       ` Laurent Pinchart
2025-03-26 13:22 ` [PATCH v4 03/11] drm/fourcc: Add DRM_FORMAT_Y8 Tomi Valkeinen
2025-03-26 13:52   ` Geert Uytterhoeven
2025-03-26 13:55     ` Tomi Valkeinen
2025-03-27  9:20       ` Pekka Paalanen [this message]
2025-03-27 14:21         ` Tomi Valkeinen
2025-03-27 15:58           ` Pekka Paalanen
2025-03-27 16:35             ` Geert Uytterhoeven
2025-03-31  7:54               ` Pekka Paalanen
2025-03-31  8:21                 ` Laurent Pinchart
2025-03-31 10:53                   ` Pekka Paalanen
2025-03-31 14:54                     ` Laurent Pinchart
2025-04-01  6:49                       ` Pekka Paalanen
2025-04-01 13:27                     ` Pekka Paalanen
2025-04-16  8:59                       ` Tomi Valkeinen
2025-04-17  8:13                         ` Pekka Paalanen
2025-04-21 14:50                           ` Laurent Pinchart
2025-04-22  9:11                             ` Pekka Paalanen
2025-04-22  9:41                               ` Geert Uytterhoeven
2025-04-22 10:01                                 ` Pekka Paalanen
2025-04-22 10:12                                   ` Geert Uytterhoeven
2025-04-22 11:00                                     ` Pekka Paalanen
2025-04-25  8:38                           ` Tomi Valkeinen
2025-04-25 10:18                             ` Pekka Paalanen
2025-03-26 13:22 ` [PATCH v4 04/11] drm/fourcc: Add DRM_FORMAT_Y10_P32 Tomi Valkeinen
2025-03-27 22:53   ` Laurent Pinchart
2025-03-26 13:22 ` [PATCH v4 05/11] drm/fourcc: Add DRM_FORMAT_X403 Tomi Valkeinen
2025-03-27 22:55   ` Laurent Pinchart
2025-03-26 13:22 ` [PATCH v4 06/11] drm/fourcc: Add DRM_FORMAT_XVUY2101010 Tomi Valkeinen
2025-03-27 23:07   ` Laurent Pinchart
2025-03-26 13:22 ` [PATCH v4 07/11] drm: xlnx: zynqmp: Use drm helpers when calculating buffer sizes Tomi Valkeinen
2025-03-26 13:22 ` [PATCH v4 08/11] drm: xlnx: zynqmp: Add support for XV15 & XV20 Tomi Valkeinen
2025-03-27 22:35   ` Laurent Pinchart
2025-03-26 13:22 ` [PATCH v4 09/11] drm: xlnx: zynqmp: Add support for Y8 and Y10_P32 Tomi Valkeinen
2025-03-27 22:52   ` Laurent Pinchart
2025-03-31 11:37     ` Tomi Valkeinen
2025-03-26 13:22 ` [PATCH v4 10/11] drm: xlnx: zynqmp: Add support for X403 Tomi Valkeinen
2025-03-27 22:59   ` Laurent Pinchart
2025-03-26 13:22 ` [PATCH v4 11/11] drm: xlnx: zynqmp: Add support for XVUY2101010 Tomi Valkeinen
2025-03-27 23:06   ` Laurent Pinchart

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=20250327112009.6b4dc430@eldfell \
    --to=pekka.paalanen@haloniitty.fi \
    --cc=airlied@gmail.com \
    --cc=anatoliy.klymenko@amd.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michal.simek@amd.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    --cc=vishal.sagar@amd.com \
    /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;
as well as URLs for NNTP newsgroup(s).