Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t 4/5] tests/kms_flip: Fix Bigjoiner checks
Date: Wed, 15 Nov 2023 14:50:11 +0530	[thread overview]
Message-ID: <41bca00b-bf67-d3d4-f4af-bc4255b71c4e@intel.com> (raw)
In-Reply-To: <ZVSCl4gsegbhcQnu@intel.com>

Hi Ville,

On Wed-15-11-2023 02:04 pm, Ville Syrjälä wrote:
> On Mon, Nov 13, 2023 at 01:49:29PM +0530, Bhanuprakash Modem wrote:
>> Bigjoiner will come in the picture when the resolution > 5K or
>> clock > max dot-clock. Add a support to check the selected mode
>> clock is greater than the max dot-clock.
>>
>> V2: - Limit the bigjoiner checks to intel hardware
>>
>> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>>   tests/kms_flip.c | 18 +++++++++++-------
>>   1 file changed, 11 insertions(+), 7 deletions(-)
>>
>> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
>> index fc7cee050..d34596599 100755
>> --- a/tests/kms_flip.c
>> +++ b/tests/kms_flip.c
> <snip>
>> @@ -2136,6 +2139,7 @@ igt_main_args("e", NULL, help_str, opt_handler, NULL)
>>   			for (i = 0; i < sizeof(tests) / sizeof(tests[0]); i++)
>>   				tests[i].flags &= ~(TEST_CHECK_TS | TEST_VBLANK_EXPIRED_SEQ);
>>   		}
>> +		max_dotclock = igt_get_max_dotclock(drm_fd);
> 
> That seems to have broken the test for !display platforms (bat-atsm-1).

Thanks for pointing it, I have floated fix here[1]. Please help to review.

[1]: https://patchwork.freedesktop.org/series/126449/

- Bhanu

> 
>>   	}
>>   
>>   	igt_describe("Tests that nonblocking reading fails correctly");
>> -- 
>> 2.40.0
> 

  parent reply	other threads:[~2023-11-15  9:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13  8:19 [igt-dev] [i-g-t 0/5] Fix Bigjoiner checks Bhanuprakash Modem
2023-11-13  8:19 ` [igt-dev] [i-g-t 1/5] tests: s/i915_pipe_output_combo_valid/intel_pipe_output_combo_valid/ Bhanuprakash Modem
2023-11-13  8:19 ` [igt-dev] [i-g-t 2/5] lib/igt_kms: s/is_i915_device/is_intel_device Bhanuprakash Modem
2023-11-13  8:45   ` [igt-dev] [i-g-t, " Joshi, Kunal1
2023-11-13  8:19 ` [igt-dev] [i-g-t 3/5] tests/i915/kms_big_joiner: Fix Bigjoiner checks Bhanuprakash Modem
2023-11-13  8:19 ` [igt-dev] [i-g-t 4/5] tests/kms_flip: " Bhanuprakash Modem
2023-11-15  8:34   ` Ville Syrjälä
2023-11-15  8:47     ` Saarinen, Jani
2023-11-15  8:55       ` Saarinen, Jani
2023-11-15  9:01         ` Saarinen, Jani
2023-11-15  9:20     ` Modem, Bhanuprakash [this message]
2023-11-13  8:19 ` [igt-dev] [i-g-t 5/5] tests/kms_setmode: " Bhanuprakash Modem
2023-11-13  8:50   ` [igt-dev] [i-g-t,5/5] " Joshi, Kunal1
2023-11-13 11:50 ` [igt-dev] ✗ CI.xeBAT: failure for Fix Bigjoiner checks (rev10) Patchwork
2023-11-13 11:51 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-11-13 15:49 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-05-17  5:24 [igt-dev] [i-g-t 0/5] Fix Bigjoiner checks Bhanuprakash Modem
2023-05-17  5:24 ` [igt-dev] [i-g-t 4/5] tests/kms_flip: " Bhanuprakash Modem

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=41bca00b-bf67-d3d4-f4af-bc4255b71c4e@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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