From: Geert Uytterhoeven <geert@linux-m68k.org> To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Javier Martinez Canillas <javierm@redhat.com>, Sam Ravnborg <sam@ravnborg.org>, Helge Deller <deller@gmx.de> Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org> Subject: [PATCH v2 RFC 08/10] drm/fourcc: Document that single-channel "red" can be any color Date: Mon, 7 Mar 2022 21:52:43 +0100 [thread overview] Message-ID: <585dc03acb4016bba910e7d15fec3ef4f0aec5b0.1646683502.git.geert@linux-m68k.org> (raw) In-Reply-To: <cover.1646683502.git.geert@linux-m68k.org> Traditionally, the first channel has been called the "red" channel, but the fourcc values for single-channel "red" formats can also be used for other light-on-dark displays, like grayscale. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> --- RFC, as I have no immediate need for these formats. v2: - New. --- include/uapi/drm/drm_fourcc.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h index 457ed39cc48f08e1..f0187cf20e4619d2 100644 --- a/include/uapi/drm/drm_fourcc.h +++ b/include/uapi/drm/drm_fourcc.h @@ -104,16 +104,16 @@ extern "C" { #define DRM_FORMAT_C4 fourcc_code('C', '4', ' ', ' ') /* [7:0] C0:C1 4:4 two pixels/byte */ #define DRM_FORMAT_C8 fourcc_code('C', '8', ' ', ' ') /* [7:0] C 8 one pixel/byte */ -/* 8 bpp Red */ +/* 8 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R8 fourcc_code('R', '8', ' ', ' ') /* [7:0] R */ -/* 10 bpp Red */ +/* 10 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R10 fourcc_code('R', '1', '0', ' ') /* [15:0] x:R 6:10 little endian */ -/* 12 bpp Red */ +/* 12 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R12 fourcc_code('R', '1', '2', ' ') /* [15:0] x:R 4:12 little endian */ -/* 16 bpp Red */ +/* 16 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R16 fourcc_code('R', '1', '6', ' ') /* [15:0] R little endian */ /* 16 bpp RG */ -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Javier Martinez Canillas <javierm@redhat.com>, Sam Ravnborg <sam@ravnborg.org>, Helge Deller <deller@gmx.de> Cc: linux-fbdev@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>, linux-m68k@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 RFC 08/10] drm/fourcc: Document that single-channel "red" can be any color Date: Mon, 7 Mar 2022 21:52:43 +0100 [thread overview] Message-ID: <585dc03acb4016bba910e7d15fec3ef4f0aec5b0.1646683502.git.geert@linux-m68k.org> (raw) In-Reply-To: <cover.1646683502.git.geert@linux-m68k.org> Traditionally, the first channel has been called the "red" channel, but the fourcc values for single-channel "red" formats can also be used for other light-on-dark displays, like grayscale. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> --- RFC, as I have no immediate need for these formats. v2: - New. --- include/uapi/drm/drm_fourcc.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/uapi/drm/drm_fourcc.h b/include/uapi/drm/drm_fourcc.h index 457ed39cc48f08e1..f0187cf20e4619d2 100644 --- a/include/uapi/drm/drm_fourcc.h +++ b/include/uapi/drm/drm_fourcc.h @@ -104,16 +104,16 @@ extern "C" { #define DRM_FORMAT_C4 fourcc_code('C', '4', ' ', ' ') /* [7:0] C0:C1 4:4 two pixels/byte */ #define DRM_FORMAT_C8 fourcc_code('C', '8', ' ', ' ') /* [7:0] C 8 one pixel/byte */ -/* 8 bpp Red */ +/* 8 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R8 fourcc_code('R', '8', ' ', ' ') /* [7:0] R */ -/* 10 bpp Red */ +/* 10 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R10 fourcc_code('R', '1', '0', ' ') /* [15:0] x:R 6:10 little endian */ -/* 12 bpp Red */ +/* 12 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R12 fourcc_code('R', '1', '2', ' ') /* [15:0] x:R 4:12 little endian */ -/* 16 bpp Red */ +/* 16 bpp Red (or generic light-on-dark) */ #define DRM_FORMAT_R16 fourcc_code('R', '1', '6', ' ') /* [15:0] R little endian */ /* 16 bpp RG */ -- 2.25.1
next prev parent reply other threads:[~2022-03-07 20:54 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-07 20:52 [PATCH v2 00/10] drm: Add support for low-color frame buffer formats Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-07 20:52 ` [PATCH v2 01/10] drm/fourcc: Add drm_format_info_bpp() helper Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:46 ` Javier Martinez Canillas 2022-03-09 12:46 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 02/10] drm/fourcc: Add drm_format_info.is_color_indexed flag Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:50 ` Javier Martinez Canillas 2022-03-09 12:50 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 03/10] drm/client: Use actual bpp when allocating frame buffers Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:51 ` Javier Martinez Canillas 2022-03-09 12:51 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 04/10] drm/framebuffer: Use actual bpp for DRM_IOCTL_MODE_GETFB Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 12:53 ` Javier Martinez Canillas 2022-03-09 12:53 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 05/10] drm/fourcc: Add DRM_FORMAT_C[124] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-08 9:04 ` Pekka Paalanen 2022-03-08 9:04 ` Pekka Paalanen 2022-03-09 12:57 ` Javier Martinez Canillas 2022-03-09 12:57 ` Javier Martinez Canillas 2022-03-14 13:30 ` Geert Uytterhoeven 2022-03-14 13:30 ` Geert Uytterhoeven 2022-03-14 15:05 ` Pekka Paalanen 2022-03-14 15:05 ` Pekka Paalanen 2022-03-14 19:01 ` Geert Uytterhoeven 2022-03-14 19:01 ` Geert Uytterhoeven 2022-03-14 22:15 ` Finn Thain 2022-03-14 22:15 ` Finn Thain 2022-03-15 7:32 ` Pekka Paalanen 2022-03-15 7:32 ` Pekka Paalanen 2022-03-15 7:51 ` Geert Uytterhoeven 2022-03-15 7:51 ` Geert Uytterhoeven 2022-03-15 7:52 ` Geert Uytterhoeven 2022-03-15 7:52 ` Geert Uytterhoeven 2022-03-15 8:45 ` Pekka Paalanen 2022-03-15 8:45 ` Pekka Paalanen 2022-03-15 8:57 ` Geert Uytterhoeven 2022-03-15 8:57 ` Geert Uytterhoeven 2022-03-15 10:48 ` Pekka Paalanen 2022-03-15 10:48 ` Pekka Paalanen 2022-03-07 20:52 ` [PATCH v2 06/10] drm/fb-helper: Add support for DRM_FORMAT_C[124] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:10 ` Javier Martinez Canillas 2022-03-09 13:10 ` Javier Martinez Canillas 2022-03-09 13:14 ` Geert Uytterhoeven 2022-03-09 13:14 ` Geert Uytterhoeven 2022-03-07 20:52 ` [PATCH v2 RFC 07/10] drm/gem-fb-helper: Use actual bpp for size calculations Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:16 ` Javier Martinez Canillas 2022-03-09 13:16 ` Javier Martinez Canillas 2022-03-07 20:52 ` Geert Uytterhoeven [this message] 2022-03-07 20:52 ` [PATCH v2 RFC 08/10] drm/fourcc: Document that single-channel "red" can be any color Geert Uytterhoeven 2022-03-08 9:06 ` Pekka Paalanen 2022-03-08 9:06 ` Pekka Paalanen 2022-03-09 13:33 ` Javier Martinez Canillas 2022-03-09 13:33 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 RFC 09/10] drm/fourcc: Add DRM_FORMAT_R[124] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:39 ` Javier Martinez Canillas 2022-03-09 13:39 ` Javier Martinez Canillas 2022-03-07 20:52 ` [PATCH v2 RFC 10/10] drm/fourcc: Add DRM_FORMAT_D[1248] Geert Uytterhoeven 2022-03-07 20:52 ` Geert Uytterhoeven 2022-03-09 13:41 ` Javier Martinez Canillas 2022-03-09 13:41 ` Javier Martinez Canillas
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=585dc03acb4016bba910e7d15fec3ef4f0aec5b0.1646683502.git.geert@linux-m68k.org \ --to=geert@linux-m68k.org \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=deller@gmx.de \ --cc=dri-devel@lists.freedesktop.org \ --cc=javierm@redhat.com \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-m68k@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=mripard@kernel.org \ --cc=sam@ravnborg.org \ --cc=tzimmermann@suse.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.