From: Karthik B S <karthik.b.s@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Jeevan B <jeevan.b@intel.com>, <igt-dev@lists.freedesktop.org>,
<swati2.sharma@intel.com>, <juha-pekka.heikkila@intel.com>,
<ramanaidu.naladala@intel.com>
Subject: Re: [PATCH i-g-t] tests/kms_flip_scaled_crc: Move require checks at the beginning of the subtest
Date: Thu, 29 Jan 2026 20:38:04 +0530 [thread overview]
Message-ID: <2553cce8-fd48-488e-889d-302eccd69fde@intel.com> (raw)
In-Reply-To: <20260129143445.uxolu7ayg2ygl7h2@kamilkon-DESK.igk.intel.com>
Hi Kamil,
Thank you for the review. Will fix these during merge.
Thanks and Regards,
Karthik.B.S
On 1/29/2026 8:04 PM, Kamil Konieczny wrote:
> Hi Karthik,
> On 2026-01-21 at 10:51:58 +0530, Karthik B S wrote:
>
> add 'intel/' after 'test/' in subject:
>
> [PATCH i-g-t] tests/intel/kms_flip_scaled_crc: Move require checks at the beginning of the subtest
>
>> Previously, setup_fb() contained the igt_require() for format + modifier,
>> causing the dynamic test to be intialized only to skip eventually if the
> s/intialized/initialized/
>
>> combination is unsupported.
>> This patch moves format/modifier checks to the per-subtest level.
>>
>> Additionally, linear framebuffers combined with REFLECT_X rotation are
>> not supported on Intel platforms prior to gen35. To make this explicit and
>> reduce CI run time, the test now performs an early skip for this
>> combination, clearly stating the reason in the skip message.
> +cc Jeevan B <jeevan.b@intel.com>
>
>> Signed-off-by: Karthik B S <karthik.b.s@intel.com>
>> ---
>> tests/intel/kms_flip_scaled_crc.c | 15 ++++++++++++---
>> 1 file changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/tests/intel/kms_flip_scaled_crc.c b/tests/intel/kms_flip_scaled_crc.c
>> index 954b46b5f..91e5793f4 100644
>> --- a/tests/intel/kms_flip_scaled_crc.c
>> +++ b/tests/intel/kms_flip_scaled_crc.c
>> @@ -670,9 +670,6 @@ const struct {
>> static void setup_fb(data_t *data, struct igt_fb *newfb, uint32_t width,
>> uint32_t height, uint64_t format, uint64_t modifier)
>> {
>> - igt_require(igt_display_has_format_mod(&data->display, format,
>> - modifier));
>> -
>> igt_create_color_fb(data->drm_fd, width, height,
>> format, modifier, 0, 1, 0, newfb);
>> }
>> @@ -901,6 +898,18 @@ int igt_main()
>> for (int index = 0; index < ARRAY_SIZE(flip_scenario_test); index++) {
>> igt_describe(flip_scenario_test[index].describe);
>> igt_subtest_with_dynamic(flip_scenario_test[index].name) {
>> + igt_require(igt_display_has_format_mod(&data.display,
>> + flip_scenario_test[index].firstformat,
>> + flip_scenario_test[index].firstmodifier));
>> + igt_require(igt_display_has_format_mod(&data.display,
>> + flip_scenario_test[index].secondformat,
>> + flip_scenario_test[index].secondmodifier));
>> +
>> + if(flip_scenario_test[index].secondmodifier == DRM_FORMAT_MOD_LINEAR &&
> Add space after 'if':
> if (flip_scenario_test[index].secondmodifier == DRM_FORMAT_MOD_LINEAR &&
>
>> + flip_scenario_test[index].secondrotation & IGT_REFLECT_X)
>> + igt_require_f(data.gen >= 35,
>> + "Linear fb with REFLECT_X unsupported");
> Add newline at end of message:
> "Linear fb with REFLECT_X unsupported\n");
>
> Without it in report there is:
>
> Linear fb with REFLECT_X unsupportedSubtest flip-P016-linear-to-P016-linear-reflect-x: SKIP (0.000s)
>
> Regards,
> Kamil
>
>> +
>> free_fbs(&data);
>> for_each_pipe(&data.display, pipe) {
>> bool found = false;
>> --
>> 2.43.0
>>
prev parent reply other threads:[~2026-01-29 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 5:21 [PATCH i-g-t] tests/kms_flip_scaled_crc: Move require checks at the beginning of the subtest Karthik B S
2026-01-21 8:39 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-01-21 9:04 ` ✓ i915.CI.BAT: " Patchwork
2026-01-21 11:18 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-21 17:58 ` ✗ i915.CI.Full: " Patchwork
2026-01-29 15:18 ` Karthik B S
2026-01-23 8:32 ` [PATCH i-g-t] " B, Jeevan
2026-01-29 14:34 ` Kamil Konieczny
2026-01-29 15:08 ` Karthik B S [this message]
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=2553cce8-fd48-488e-889d-302eccd69fde@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=juha-pekka.heikkila@intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=ramanaidu.naladala@intel.com \
--cc=swati2.sharma@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 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.