Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wentland <harry.wentland@amd.com>
To: <igt-dev@lists.freedesktop.org>
Subject: [igt-dev] [RFC PATCH v3 03/12] include/drm-uapi: Add COLOROP object
Date: Wed, 8 Nov 2023 11:39:52 -0500	[thread overview]
Message-ID: <20231108164006.106967-4-harry.wentland@amd.com> (raw)
In-Reply-To: <20231108164006.106967-1-harry.wentland@amd.com>

DRM is introducing a new DRM core obejct, a drm_colorop. This
object will represent one color operation in a color pipeline.

Introduce the object type in the drm-uapi.

v3:
- move enum drm_colorop_type to drm_mode.h

Signed-off-by: Harry Wentland <harry.wentland@amd.com>
---
 include/drm-uapi/drm_mode.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/include/drm-uapi/drm_mode.h b/include/drm-uapi/drm_mode.h
index ea1b639bcb28..c49526bca034 100644
--- a/include/drm-uapi/drm_mode.h
+++ b/include/drm-uapi/drm_mode.h
@@ -629,6 +629,7 @@ struct drm_mode_connector_set_property {
 #define DRM_MODE_OBJECT_FB 0xfbfbfbfb
 #define DRM_MODE_OBJECT_BLOB 0xbbbbbbbb
 #define DRM_MODE_OBJECT_PLANE 0xeeeeeeee
+#define DRM_MODE_OBJECT_COLOROP 0xfafafafa
 #define DRM_MODE_OBJECT_ANY 0
 
 struct drm_mode_obj_get_properties {
@@ -857,6 +858,10 @@ struct drm_color_lut {
 	__u16 reserved;
 };
 
+enum drm_colorop_type {
+	DRM_COLOROP_1D_CURVE
+};
+
 /**
  * struct hdr_metadata_infoframe - HDR Metadata Infoframe Data.
  *
-- 
2.42.0

  parent reply	other threads:[~2023-11-08 16:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 16:39 [igt-dev] [RFC PATCH v3 00/12] IGT tests for the KMS Color Pipeline API Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 01/12] lib/drmtest: Add is_vkms_device() Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 02/12] lib/igt_kms: Introduce DRM_CLIENT_CAP_PLANE_COLOR_PIPELINE Harry Wentland
2023-11-08 16:39 ` Harry Wentland [this message]
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 04/12] lib/igt_kms: Introduce drm_colorop and COLOR_PIPELINE Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 05/12] tests/kms_properties: Add colorop properties test Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 06/12] igt/color: Add SW color transform functionality Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 07/12] lib/igt_fb: Add copy_fb function Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 08/12] tests/kms_colorop: Add kms_colorop tests Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 09/12] drm-uapi: Add 3x4 CTM Harry Wentland
2023-11-08 16:39 ` [igt-dev] [RFC PATCH v3 10/12] lib/igt_kms: Add support for DATA colorop property Harry Wentland
2023-11-08 16:40 ` [igt-dev] [RFC PATCH v3 11/12] lib/igt_color: Add support for 3x4 matrices Harry Wentland
2023-11-08 16:40 ` [igt-dev] [RFC PATCH v3 12/12] tests/kms_colorop: Add 3x4 CTM tests Harry Wentland
2023-11-08 17:56 ` [igt-dev] ✗ GitLab.Pipeline: warning for IGT tests for the KMS Color Pipeline API (rev3) Patchwork
2023-11-08 18:23 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-08 18:40 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2024-02-09 16:32 ` [igt-dev] [RFC PATCH v3 00/12] IGT tests for the KMS Color Pipeline API Modem, Bhanuprakash
2024-02-09 16:50   ` Harry Wentland

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=20231108164006.106967-4-harry.wentland@amd.com \
    --to=harry.wentland@amd.com \
    --cc=igt-dev@lists.freedesktop.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