From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: [PATCH 01/11] tools headers: Sync UAPI drm/drm.h with kernel sources
Date: Mon, 22 Dec 2025 14:57:06 -0800 [thread overview]
Message-ID: <20251222225716.3565649-1-namhyung@kernel.org> (raw)
To pick up changes from:
179ab8e7d7b378f1 ("drm/colorop: Introduce DRM_CLIENT_CAP_PLANE_COLOR_PIPELINE")
This should be used to beautify DRM syscall arguments and it addresses
these tools/perf build warnings:
Warning: Kernel ABI header differences:
diff -u tools/include/uapi/drm/drm.h include/uapi/drm/drm.h
Please see tools/include/README.kernel-copies.
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
tools/include/uapi/drm/drm.h | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/tools/include/uapi/drm/drm.h b/tools/include/uapi/drm/drm.h
index 3cd5cf15e3c9ce22..27cc159c1d275c7a 100644
--- a/tools/include/uapi/drm/drm.h
+++ b/tools/include/uapi/drm/drm.h
@@ -906,6 +906,21 @@ struct drm_get_cap {
*/
#define DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT 6
+/**
+ * DRM_CLIENT_CAP_PLANE_COLOR_PIPELINE
+ *
+ * If set to 1 the DRM core will allow setting the COLOR_PIPELINE
+ * property on a &drm_plane, as well as drm_colorop properties.
+ *
+ * Setting of these plane properties will be rejected when this client
+ * cap is set:
+ * - COLOR_ENCODING
+ * - COLOR_RANGE
+ *
+ * The client must enable &DRM_CLIENT_CAP_ATOMIC first.
+ */
+#define DRM_CLIENT_CAP_PLANE_COLOR_PIPELINE 7
+
/* DRM_IOCTL_SET_CLIENT_CAP ioctl argument type */
struct drm_set_client_cap {
__u64 capability;
--
2.52.0.351.gbe84eed79e-goog
next reply other threads:[~2025-12-22 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 22:57 Namhyung Kim [this message]
2025-12-22 22:57 ` [PATCH 02/11] tools headers: Sync UAPI KVM headers " Namhyung Kim
2025-12-22 22:57 ` [PATCH 03/11] tools headers: Sync UAPI linux/fcntl.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 04/11] tools headers: Sync UAPI linux/fs.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 05/11] tools headers: Sync UAPI linux/mount.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 06/11] tools headers: Sync UAPI sound/asound.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 07/11] tools headers: Sync x86 headers " Namhyung Kim
2025-12-22 22:57 ` [PATCH 08/11] tools headers: Sync arm64 " Namhyung Kim
2025-12-23 15:36 ` Leo Yan
2025-12-23 18:11 ` Namhyung Kim
2025-12-22 22:57 ` [PATCH 09/11] tools headers: Sync linux/gfp_types.h " Namhyung Kim
2025-12-23 1:00 ` SeongJae Park
2025-12-23 18:06 ` Namhyung Kim
2025-12-22 22:57 ` [PATCH 10/11] tools headers: Sync linux/socket.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 11/11] tools headers: Sync syscall table " Namhyung Kim
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=20251222225716.3565649-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®