From: Alex Hung <alex.hung@amd.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: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
igt-dev@lists.freedesktop.org, kernel-dev@igalia.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 v3 3/6] tests/kms_properties: don't check colorop if no plane color pipeline prop
Date: Thu, 13 Aug 2026 21:44:53 -0600 [thread overview]
Message-ID: <da1aee65-0f91-4dcb-bb75-08563d40e166@amd.com> (raw)
In-Reply-To: <20260811143558.141813-4-mwen@igalia.com>
See typos and mistakes in commit message below; otherwise
Reviewed-by: Alex Hung <alex.hung@amd.com>
On 8/11/26 08:23, Melissa Wen wrote:
> If plane COLOR_PIPELINE property is not avaliable, the plane doesn't
"available"
> support colorop pipeline and there is no meaning in check colorop
"checking"
> properties here too. Don't check colorop properties in planes that
> doesn't support it (for example, in cursor planes of AMD driver).
"don't"
>
> Signed-off-by: Melissa Wen <mwen@igalia.com>
>
> ---
>
> v2:
> - detach different changes from a single commit (Chaitanya)
> ---
> tests/kms_properties.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tests/kms_properties.c b/tests/kms_properties.c
> index 93bf1ea26..292a04a2a 100644
> --- a/tests/kms_properties.c
> +++ b/tests/kms_properties.c
> @@ -247,6 +247,10 @@ 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);
next prev parent reply other threads:[~2026-08-14 3:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:23 [PATCH i-g-t v3 0/6] test/kms_colorop_helper: don't request colorop updates indefinitely Melissa Wen
2026-08-11 14:23 ` [PATCH i-g-t v3 1/6] lib/igt_kms: clear colorop-changed flag after commit Melissa Wen
2026-08-11 16:37 ` Jani Nikula
2026-08-14 3:39 ` Alex Hung
2026-08-11 14:23 ` [PATCH i-g-t v3 2/6] test/kms_colorop_helper: only check if a given enum value exist Melissa Wen
2026-08-14 3:41 ` Alex Hung
2026-08-11 14:23 ` [PATCH i-g-t v3 3/6] tests/kms_properties: don't check colorop if no plane color pipeline prop Melissa Wen
2026-08-14 3:44 ` Alex Hung [this message]
2026-08-11 14:23 ` [PATCH i-g-t v3 4/6] tests/kms_properties: keep primary plane enabled for each CRTC Melissa Wen
2026-08-14 4:05 ` Alex Hung
2026-08-14 6:20 ` Borah, Chaitanya Kumar
2026-08-11 14:23 ` [PATCH i-g-t v3 6/6] tests/kms_color_pipeline: skip if not an intel device Melissa Wen
2026-08-14 3:55 ` Alex Hung
2026-08-11 16:43 ` ✓ Xe.CI.BAT: success for test/kms_colorop_helper: don't request colorop updates indefinitely (rev2) Patchwork
2026-08-11 16:59 ` ✓ i915.CI.BAT: " Patchwork
2026-08-11 18:43 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-11 19:21 ` ✗ 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=da1aee65-0f91-4dcb-bb75-08563d40e166@amd.com \
--to=alex.hung@amd.com \
--cc=John.Harrison@Igalia.com \
--cc=adrinael@adrinael.net \
--cc=arek@hiler.eu \
--cc=ashutosh.dixit@intel.com \
--cc=bhanuprakash.modem@gmail.com \
--cc=chaitanya.kumar.borah@intel.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 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.