From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>,
Uma Shankar <uma.shankar@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>
Cc: <ville.syrjala@linux.intel.com>, <pekka.paalanen@collabora.com>,
<contact@emersion.fr>, <harry.wentland@amd.com>,
<mwen@igalia.com>, <jadahl@redhat.com>,
<sebastian.wick@redhat.com>, <swati2.sharma@intel.com>,
<alex.hung@amd.com>, <jani.nikula@intel.com>,
<suraj.kandpal@intel.com>
Subject: Re: [v7,04/15] drm/i915/color: Create a transfer function color pipeline
Date: Tue, 2 Dec 2025 13:50:08 +0530 [thread overview]
Message-ID: <b2864e72-6e2e-426b-8bab-855ec55a8a78@intel.com> (raw)
In-Reply-To: <a0e0f7ea-8fc0-44a0-9b32-0538bff42601@intel.com>
On 12/2/2025 1:26 PM, Murthy, Arun R wrote:
>
> On 01-12-2025 12:16, Uma Shankar wrote:
>> From: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>>
>> Add a color pipeline with three colorops in the sequence
>>
>> 1D LUT - 3x4 CTM - 1D LUT
>>
>> This pipeline can be used to do any color space conversion or HDR
>> tone mapping
>>
>> v2: Change namespace to drm_plane_colorop*
>> v3: Use simpler/pre-existing colorops for first iteration
>> v4:
>> - s/*_tf_*/*_color_* (Jani)
>> - Refactor to separate files (Jani)
>> - Add missing space in comment (Suraj)
>> - Consolidate patch that adds/attaches pipeline property
>> v5:
>> - Limit MAX_COLOR_PIPELINES to 2.(Suraj)
>> Increase it as and when we add more pipelines.
>> - Remove redundant initialization code (Suraj)
>>
>> Signed-off-by: Uma Shankar <uma.shankar@intel.com>
>> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> ---
>> drivers/gpu/drm/i915/Makefile | 1 +
>> .../drm/i915/display/intel_color_pipeline.c | 97 +++++++++++++++++++
>> .../drm/i915/display/intel_color_pipeline.h | 13 +++
>> drivers/gpu/drm/xe/Makefile | 1 +
>> 4 files changed, 112 insertions(+)
>> create mode 100644 drivers/gpu/drm/i915/display/intel_color_pipeline.c
>> create mode 100644 drivers/gpu/drm/i915/display/intel_color_pipeline.h
>>
>> diff --git a/drivers/gpu/drm/i915/Makefile b/drivers/gpu/drm/i915/
>> Makefile
>> index 7c19d5345d88..ca5c69d1cb08 100644
>> --- a/drivers/gpu/drm/i915/Makefile
>> +++ b/drivers/gpu/drm/i915/Makefile
>> @@ -241,6 +241,7 @@ i915-y += \
>> display/intel_cmtg.o \
>> display/intel_color.o \
>> display/intel_colorop.o \
>> + display/intel_color_pipeline.o \
>> display/intel_combo_phy.o \
>> display/intel_connector.o \
>> display/intel_crtc.o \
>> diff --git a/drivers/gpu/drm/i915/display/intel_color_pipeline.c b/
>> drivers/gpu/drm/i915/display/intel_color_pipeline.c
>> new file mode 100644
>> index 000000000000..1415f94dd3e3
>> --- /dev/null
>> +++ b/drivers/gpu/drm/i915/display/intel_color_pipeline.c
>> @@ -0,0 +1,97 @@
>> +// SPDX-License-Identifier: MIT
>> +/*
>> + * Copyright © 2025 Intel Corporation
>> + */
>> +#include "intel_colorop.h"
>> +#include "intel_color_pipeline.h"
>> +#include "intel_de.h"
>> +#include "intel_display_types.h"
>> +#include "skl_universal_plane.h"
>> +
>> +#define MAX_COLOR_PIPELINES 2
> Should this be same as INTEL_CB_MAX defined in intel_display_limits.h ?
>> +#define PLANE_DEGAMMA_SIZE 128
>> +#define PLANE_GAMMA_SIZE 32
>> +
>> +static
>> +int _intel_color_pipeline_plane_init(struct drm_plane *plane, struct
>> drm_prop_enum_list *list)
>> +{
>> + struct intel_colorop *colorop;
>> + struct drm_device *dev = plane->dev;
>> + int ret;
>> + struct drm_colorop *prev_op;
>> +
>> + colorop = intel_colorop_create(INTEL_PLANE_CB_PRE_CSC_LUT);
>> +
>> + ret = drm_plane_colorop_curve_1d_lut_init(dev, &colorop->base,
>> plane,
>> + PLANE_DEGAMMA_SIZE,
>> + DRM_COLOROP_LUT1D_INTERPOLATION_LINEAR,
>> + DRM_COLOROP_FLAG_ALLOW_BYPASS);
>> +
>> + if (ret)
>> + return ret;
>> +
>> + list->type = colorop->base.base.id;
>> + list->name = kasprintf(GFP_KERNEL, "Color Pipeline %d", colorop-
>> >base.base.id);
>> +
>> + /* TODO: handle failures and clean up */
>> + prev_op = &colorop->base;
>> +
>> + colorop = intel_colorop_create(INTEL_PLANE_CB_CSC);
>> + ret = drm_plane_colorop_ctm_3x4_init(dev, &colorop->base, plane,
>> + DRM_COLOROP_FLAG_ALLOW_BYPASS);
>> + if (ret)
>> + return ret;
>> +
>> + drm_colorop_set_next_property(prev_op, &colorop->base);
>> + prev_op = &colorop->base;
>> +
>> + colorop = intel_colorop_create(INTEL_PLANE_CB_POST_CSC_LUT);
>> + ret = drm_plane_colorop_curve_1d_lut_init(dev, &colorop->base,
>> plane,
>> + PLANE_GAMMA_SIZE,
>> + DRM_COLOROP_LUT1D_INTERPOLATION_LINEAR,
>> + DRM_COLOROP_FLAG_ALLOW_BYPASS);
>> + if (ret)
>> + return ret;
>> +
>> + drm_colorop_set_next_property(prev_op, &colorop->base);
>> +
>> + return 0;
>> +}
>> +
>> +int intel_color_pipeline_plane_init(struct drm_plane *plane)
>> +{
>> + struct drm_device *dev = plane->dev;
>> + struct intel_display *display = to_intel_display(dev);
>> + struct drm_property *prop;
>> + struct drm_prop_enum_list pipelines[MAX_COLOR_PIPELINES];
>> + int len = 0;
>> + int ret;
>> +
>> + /* Currently expose pipeline only for HDR planes */
>> + if (!icl_is_hdr_plane(display, to_intel_plane(plane)->id))
>> + return 0;
>> +
>> + /* Add "Bypass" (i.e. NULL) pipeline */
>> + pipelines[len].type = 0;
>> + pipelines[len].name = "Bypass";
>> + len++;
> Code for creating Bypass and COLOR_PIPELINE property is there in
> drm_core and is exported as drm_plane_create_color_pipeline_property()
>
> Can this function be used to avoid code duplication?
Makes sense. Would be added in the next version.
Regards
Chaitanya
>
> Thanks and Regards,
> Arun R Murthy
> -------------------
>
>> +
>> + /* Add pipeline consisting of transfer functions */
>> + ret = _intel_color_pipeline_plane_init(plane, &pipelines[len]);
>> + if (ret)
>> + return ret;
>> + len++;
>> +
>> + /* Create COLOR_PIPELINE property and attach */
>> + prop = drm_property_create_enum(dev, DRM_MODE_PROP_ATOMIC,
>> + "COLOR_PIPELINE",
>> + pipelines, len);
>> + if (!prop)
>> + return -ENOMEM;
>> +
>> + plane->color_pipeline_property = prop;
>> +
>> + drm_object_attach_property(&plane->base, prop, 0);
>> +
>> + return 0;
>> +}
>> diff --git a/drivers/gpu/drm/i915/display/intel_color_pipeline.h b/
>> drivers/gpu/drm/i915/display/intel_color_pipeline.h
>> new file mode 100644
>> index 000000000000..7f1d32bc9202
>> --- /dev/null
>> +++ b/drivers/gpu/drm/i915/display/intel_color_pipeline.h
>> @@ -0,0 +1,13 @@
>> +/* SPDX-License-Identifier: MIT */
>> +/*
>> + * Copyright © 2025 Intel Corporation
>> + */
>> +
>> +#ifndef __INTEL_COLOR_PIPELINE_H__
>> +#define __INTEL_COLOR_PIPELINE_H__
>> +
>> +struct drm_plane;
>> +
>> +int intel_color_pipeline_plane_init(struct drm_plane *plane);
>> +
>> +#endif /* __INTEL_COLOR_PIPELINE_H__ */
>> diff --git a/drivers/gpu/drm/xe/Makefile b/drivers/gpu/drm/xe/Makefile
>> index 3420725c4ba8..89f922d745ba 100644
>> --- a/drivers/gpu/drm/xe/Makefile
>> +++ b/drivers/gpu/drm/xe/Makefile
>> @@ -235,6 +235,7 @@ xe-$(CONFIG_DRM_XE_DISPLAY) += \
>> i915-display/intel_cmtg.o \
>> i915-display/intel_color.o \
>> i915-display/intel_colorop.o \
>> + i915-display/intel_color_pipeline.o \
>> i915-display/intel_combo_phy.o \
>> i915-display/intel_connector.o \
>> i915-display/intel_crtc.o \
next prev parent reply other threads:[~2025-12-02 8:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 6:46 [v7 00/15] Plane Color Pipeline support for Intel platforms Uma Shankar
2025-12-01 6:46 ` [v7 01/15] drm/i915/display: Add identifiers for driver specific blocks Uma Shankar
2025-12-02 7:42 ` [v7, " Murthy, Arun R
2025-12-02 8:04 ` Borah, Chaitanya Kumar
2025-12-01 6:46 ` [v7 02/15] drm/i915: Add intel_color_op Uma Shankar
2025-12-01 14:21 ` kernel test robot
2025-12-01 6:46 ` [v7 03/15] drm/i915/color: Add helper to create intel colorop Uma Shankar
2025-12-01 6:46 ` [v7 04/15] drm/i915/color: Create a transfer function color pipeline Uma Shankar
2025-12-01 9:02 ` Kandpal, Suraj
2025-12-01 15:55 ` kernel test robot
2025-12-02 7:56 ` [v7,04/15] " Murthy, Arun R
2025-12-02 8:20 ` Borah, Chaitanya Kumar [this message]
2025-12-01 6:46 ` [v7 05/15] drm/i915/color: Add framework to program CSC Uma Shankar
2025-12-01 9:05 ` Kandpal, Suraj
2025-12-01 15:45 ` kernel test robot
2025-12-01 6:46 ` [v7 06/15] drm/i915/color: Preserve sign bit when int_bits is Zero Uma Shankar
2025-12-01 6:46 ` [v7 07/15] drm/i915/color: Add plane CTM callback for D12 and beyond Uma Shankar
2025-12-01 9:16 ` Kandpal, Suraj
2025-12-01 18:13 ` kernel test robot
2025-12-01 6:46 ` [v7 08/15] drm/i915: Add register definitions for Plane Degamma Uma Shankar
2025-12-01 9:18 ` Kandpal, Suraj
2025-12-01 6:46 ` [v7 09/15] drm/i915: Add register definitions for Plane Post CSC Uma Shankar
2025-12-01 9:21 ` Kandpal, Suraj
2025-12-01 6:46 ` [v7 10/15] drm/i915/color: Add framework to program PRE/POST CSC LUT Uma Shankar
2025-12-01 9:23 ` Kandpal, Suraj
2025-12-01 6:46 ` [v7 11/15] drm/i915/color: Program Pre-CSC registers Uma Shankar
2025-12-01 9:24 ` Kandpal, Suraj
2025-12-02 8:24 ` Shankar, Uma
2025-12-02 16:00 ` Kandpal, Suraj
2025-12-01 19:28 ` kernel test robot
2025-12-01 6:46 ` [v7 12/15] drm/i915/xelpd: Program Plane Post CSC Registers Uma Shankar
2025-12-02 15:32 ` Kandpal, Suraj
2025-12-02 16:10 ` Kandpal, Suraj
2025-12-01 6:46 ` [v7 13/15] drm/i915/display: Add registers for 3D LUT Uma Shankar
2025-12-01 9:26 ` Kandpal, Suraj
2025-12-01 6:46 ` [v7 14/15] drm/i915/color: Add 3D LUT to color pipeline Uma Shankar
2025-12-02 15:42 ` Kandpal, Suraj
2025-12-01 6:46 ` [v7 15/15] drm/i915/color: Enable Plane Color Pipelines Uma Shankar
2025-12-01 21:14 ` kernel test robot
2025-12-01 6:47 ` ✗ CI.checkpatch: warning for Plane Color Pipeline support for Intel platforms (rev6) Patchwork
2025-12-01 6:48 ` ✓ CI.KUnit: success " Patchwork
2025-12-01 7:03 ` ✗ CI.checksparse: warning " Patchwork
2025-12-01 7:50 ` ✓ Xe.CI.BAT: success " Patchwork
2025-12-01 8:41 ` ✗ Xe.CI.Full: failure " Patchwork
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=b2864e72-6e2e-426b-8bab-855ec55a8a78@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=alex.hung@amd.com \
--cc=arun.r.murthy@intel.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jadahl@redhat.com \
--cc=jani.nikula@intel.com \
--cc=mwen@igalia.com \
--cc=pekka.paalanen@collabora.com \
--cc=sebastian.wick@redhat.com \
--cc=suraj.kandpal@intel.com \
--cc=swati2.sharma@intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@linux.intel.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