From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: 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
Subject: Re: [PATCH v2 04/10] drm/fourcc: Add DRM_FORMAT_Y10_LE32
Date: Wed, 15 Jan 2025 18:07:43 +0200 [thread overview]
Message-ID: <3bcc862d-f63c-41fc-89a5-74993b68d636@ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdUSqiwGynNTCs7eVcr5EL4Toud90AVRb=85egWfDAc6Ew@mail.gmail.com>
On 15/01/2025 16:49, Geert Uytterhoeven wrote:
> Hi Tomi,
>
> On Wed, Jan 15, 2025 at 3:34 PM Tomi Valkeinen
> <tomi.valkeinen@ideasonboard.com> wrote:
>> On 15/01/2025 16:08, Geert Uytterhoeven wrote:
>>> On Wed, Jan 15, 2025 at 2:46 PM Tomi Valkeinen
>>> <tomi.valkeinen@ideasonboard.com> wrote:
>>>> On 15/01/2025 14:52, Geert Uytterhoeven wrote:
>>>>> On Wed, Jan 15, 2025 at 1:42 PM Tomi Valkeinen
>>>>> <tomi.valkeinen@ideasonboard.com> wrote:
>>>>>> On 15/01/2025 14:33, Geert Uytterhoeven wrote:
>>>>>>> On Wed, Jan 15, 2025 at 12:11 PM Tomi Valkeinen
>>>>>>> <tomi.valkeinen@ideasonboard.com> wrote:
>>>>>>>> On 15/01/2025 12:33, Geert Uytterhoeven wrote:
>>>>>>>>> On Wed, Jan 15, 2025 at 10:04 AM Tomi Valkeinen
>>>>>>>>> <tomi.valkeinen@ideasonboard.com> wrote:
>>>>>>>>>> Add Y10_LE32, a 10 bit greyscale format, with 3 pixels packed into
>>>>>>>>>> 32-bit container.
>
>> Well, this is all somewhat beside the point. So is "_Y10_32" (or
>> "_R10_32" if we use R) fine?
>
> IAARDD[*], but "10_32" makes me think it stores one 10-bit pixel in a
> 32-bit word (i.e. a 32-bit variant of R10). So [YR]PA4 would be better.
That would be a very silly format. So I think some HW guy is already
designing chips that have it.
[YR]10_PACKED_32? We can have longer names, we don't need to do encoding
like [YR]PA4.
> [*] I am a rookie DRM developer...
I haven't heard that before...
Tomi
next prev parent reply other threads:[~2025-01-15 16:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 9:03 [PATCH v2 00/10] drm: Add new pixel formats for Xilinx Zynqmp Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 01/10] drm/fourcc: Add warning for bad bpp Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 02/10] drm/fourcc: Add DRM_FORMAT_XV15/XV20 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 03/10] drm/fourcc: Add DRM_FORMAT_Y8 Tomi Valkeinen
2025-01-15 10:30 ` Geert Uytterhoeven
2025-01-15 11:12 ` Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 04/10] drm/fourcc: Add DRM_FORMAT_Y10_LE32 Tomi Valkeinen
2025-01-15 10:33 ` Geert Uytterhoeven
2025-01-15 11:11 ` Tomi Valkeinen
2025-01-15 12:33 ` Geert Uytterhoeven
2025-01-15 12:42 ` Tomi Valkeinen
2025-01-15 12:52 ` Geert Uytterhoeven
2025-01-15 13:46 ` Tomi Valkeinen
2025-01-15 14:08 ` Geert Uytterhoeven
2025-01-15 14:34 ` Tomi Valkeinen
2025-01-15 14:49 ` Geert Uytterhoeven
2025-01-15 16:07 ` Tomi Valkeinen [this message]
2025-01-15 9:03 ` [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_X403 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 06/10] drm: xlnx: zynqmp: Use drm helpers when calculating buffer sizes Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 07/10] drm: xlnx: zynqmp: Add support for XV15 & XV20 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 08/10] drm: xlnx: zynqmp: Add support for Y8 and Y10_LE32 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 09/10] drm: xlnx: zynqmp: Add support for X403 Tomi Valkeinen
2025-01-15 9:03 ` [PATCH v2 10/10] drm: xlnx: zynqmp: Fix max dma segment size Tomi Valkeinen
2025-02-06 19:48 ` Sean Anderson
2025-02-11 13:00 ` Tomi Valkeinen
2025-01-15 11:13 ` [PATCH v2 00/10] drm: Add new pixel formats for Xilinx Zynqmp Dmitry Baryshkov
2025-01-15 12:11 ` Tomi Valkeinen
2025-02-12 16:37 ` Tomi Valkeinen
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=3bcc862d-f63c-41fc-89a5-74993b68d636@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=anatoliy.klymenko@amd.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=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
all inboxes | Powered by JetHome®