From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Melissa Wen <mwen@igalia.com>,
Petri Latvala <adrinael@adrinael.net>,
Arkadiusz Hiler <arek@hiler.eu>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
Bhanuprakash Modem <bhanuprakash.modem@gmail.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Karthik B S <karthik.b.s@intel.com>
Cc: <igt-dev@lists.freedesktop.org>, <kernel-dev@igalia.com>,
Alex Hung <alex.hung@amd.com>,
Swati Sharma <swati2.sharma@intel.com>,
John Harrison <John.Harrison@Igalia.com>,
Rodrigo Siqueira <siqueira@igalia.com>,
Simon Ser <contact@emersion.fr>, Xaver Hugl <xaver.hugl@kde.org>,
Harry Wentland <harry.wentland@amd.com>,
Uma Shankar <uma.shankar@intel.com>
Subject: Re: [PATCH i-g-t v2 3/4] tests/kms_properties: check colorop properties on active color pipelines
Date: Fri, 31 Jul 2026 13:57:07 +0530 [thread overview]
Message-ID: <5829921c-ff2e-4bd7-be70-b1bc1ed07061@intel.com> (raw)
In-Reply-To: <20260602211259.898147-4-mwen@igalia.com>
Hello Melissa,
On 6/3/2026 2:36 AM, Melissa Wen wrote:
> Colorop properties can only be changed if its color pipeline is active,
> i.e. the colorop is in the chain of the color pipeline set in plane
> COLOR_PIPELINE property and its plane is active. For AMD, a CRTC must
> have a primary plane active, so overlay needs its own fb and cannot
> reuse primary fb. Also, color pipeline cannot be enabled on planes
> without COLOR_PIPELINE properties.
>
The patch is doing two things together. Can you please separate them out?
==
Chaitanya
> Signed-off-by: Melissa Wen <mwen@igalia.com>
> ---
> tests/kms_properties.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_properties.c b/tests/kms_properties.c
> index f735839da..79d691448 100644
> --- a/tests/kms_properties.c
> +++ b/tests/kms_properties.c
> @@ -237,7 +237,7 @@ static void run_colorop_property_tests(igt_display_t *display,
> igt_crtc_t *crtc, igt_output_t *output,
> bool atomic)
> {
> - struct igt_fb fb;
> + struct igt_fb fb, afb;
> igt_plane_t *plane;
> igt_colorop_t *colorop;
> int i;
> @@ -247,14 +247,31 @@ static void run_colorop_property_tests(igt_display_t *display,
> &fb);
>
> for_each_plane_on_crtc(crtc, plane) {
> + /* don't check colorop in planes without support to color pipeline */
> + if (!igt_plane_has_prop(plane, IGT_PLANE_COLOR_PIPELINE))
> + continue;
> +
> igt_info("Testing colorop properties on plane %s.#%d-%s (output: %s)\n",
> igt_crtc_name(crtc), plane->index,
> kmstest_plane_type_name(plane->type), output->name);
>
> + /* AMD requires primary plane enabled to keep CRTC enabled */
> + if (plane->type != DRM_PLANE_TYPE_PRIMARY) {
> + drmModeModeInfo *mode = igt_output_get_mode(output);
> +
> + igt_create_pattern_fb(display->drm_fd, mode->hdisplay, mode->vdisplay,
> + DRM_FORMAT_XRGB8888, DRM_FORMAT_MOD_LINEAR, &afb);
> +
> + igt_plane_set_fb(plane, &afb);
> + }
> +
> /* iterate over all color pipelines on plane */
> for (i = 0; i < plane->num_color_pipelines; ++i) {
> /* iterate over all colorops in pipeline*/
> colorop = plane->color_pipelines[i];
> + igt_plane_set_color_pipeline(plane, colorop);
> + igt_display_commit_atomic(display, DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> +
> while (colorop) {
> igt_info("Testing colorop properties on %s.#%d.#%d-%s (output: %s)\n",
> igt_crtc_name(crtc), plane->index,
> @@ -268,8 +285,13 @@ static void run_colorop_property_tests(igt_display_t *display,
> colorop = igt_find_colorop(display, colorop_id);
> }
> }
> - }
> + igt_plane_set_prop_enum(plane, IGT_PLANE_COLOR_PIPELINE, "Bypass");
>
> + if (plane->type != DRM_PLANE_TYPE_PRIMARY) {
> + igt_plane_set_fb(plane, NULL);
> + igt_remove_fb(display->drm_fd, &afb);
> + }
> + }
> cleanup_crtc(display, crtc, output,
> &fb);
> }
next prev parent reply other threads:[~2026-07-31 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 21:06 [PATCH i-g-t v2 0/4] test/kms_colorop_helper: don't request colorop updates indefinitely Melissa Wen
2026-06-02 21:06 ` [PATCH i-g-t v2 1/4] lib/igt_kms: clear colorop-changed flag after commit Melissa Wen
2026-07-31 8:25 ` Borah, Chaitanya Kumar
2026-06-02 21:06 ` [PATCH i-g-t v2 2/4] test/kms_colorop_helper: only check if a given enum value exist Melissa Wen
2026-07-31 8:26 ` Borah, Chaitanya Kumar
2026-06-02 21:06 ` [PATCH i-g-t v2 3/4] tests/kms_properties: check colorop properties on active color pipelines Melissa Wen
2026-07-31 8:27 ` Borah, Chaitanya Kumar [this message]
2026-06-02 21:06 ` [PATCH i-g-t v2 4/4] tests/kms_color_pipeline: skip if not an intel device Melissa Wen
2026-07-31 8:27 ` Borah, Chaitanya Kumar
2026-06-03 6:51 ` ✓ Xe.CI.BAT: success for test/kms_colorop_helper: don't request colorop updates indefinitely Patchwork
2026-06-03 6:57 ` ✓ i915.CI.BAT: " Patchwork
2026-06-03 18:25 ` ✓ Xe.CI.FULL: " Patchwork
2026-06-04 3:33 ` ✗ i915.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=5829921c-ff2e-4bd7-be70-b1bc1ed07061@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=John.Harrison@Igalia.com \
--cc=adrinael@adrinael.net \
--cc=alex.hung@amd.com \
--cc=arek@hiler.eu \
--cc=ashutosh.dixit@intel.com \
--cc=bhanuprakash.modem@gmail.com \
--cc=contact@emersion.fr \
--cc=harry.wentland@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=karthik.b.s@intel.com \
--cc=kernel-dev@igalia.com \
--cc=mwen@igalia.com \
--cc=siqueira@igalia.com \
--cc=swati2.sharma@intel.com \
--cc=uma.shankar@intel.com \
--cc=xaver.hugl@kde.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