All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 3/6] tests/kms_invalid_mode: Move bigjoiner handling into the proper place
Date: Tue, 5 Oct 2021 15:45:32 +0530	[thread overview]
Message-ID: <d0e88bad-fd98-352a-a660-30971172beb8@intel.com> (raw)
In-Reply-To: <20210916153515.21369-3-ville.syrjala@linux.intel.com>

On 9/16/2021 9:05 PM, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Since we're adding other subtests we don't want to muck around
> with the dotclock unconditionally in the main test code. Move
> the handling into the subtest specific adjust function.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
> ---
>   tests/i915/kms_invalid_mode.c | 28 +++++++++++++++-------------
>   1 file changed, 15 insertions(+), 13 deletions(-)
>
> diff --git a/tests/i915/kms_invalid_mode.c b/tests/i915/kms_invalid_mode.c
> index 8b24993e40a3..a1899bd52214 100644
> --- a/tests/i915/kms_invalid_mode.c
> +++ b/tests/i915/kms_invalid_mode.c
> @@ -69,7 +69,9 @@ can_bigjoiner(data_t *data)
>   static bool
>   adjust_mode_clock_too_high(data_t *data, drmModeModeInfoPtr mode)
>   {
> -	igt_require(data->max_dotclock != 0);
> +	int max_dotclock = data->max_dotclock;
> +
> +	igt_require(max_dotclock != 0);
>   
>   	/*
>   	 * FIXME When we have a fixed mode, the kernel will ignore
> @@ -82,7 +84,18 @@ adjust_mode_clock_too_high(data_t *data, drmModeModeInfoPtr mode)
>   	if (has_scaling_mode_prop(data))
>   		return false;
>   
> -	mode->clock = data->max_dotclock + 1;
> +	/*
> +	 * Newer platforms can support modes higher than the maximum dot clock
> +	 * by using pipe joiner, so set the mode clock twice that of maximum
> +	 * dot clock;
> +	 */
> +	if (can_bigjoiner(data)) {
> +		igt_info("Platform supports bigjoiner with %s\n",
> +			 data->output->name);
> +		max_dotclock *= 2;
> +	}
> +
> +	mode->clock = max_dotclock + 1;
>   
>   	return true;
>   }
> @@ -103,17 +116,6 @@ test_output(data_t *data)
>   	if (!data->adjust_mode(data, &mode))
>   		return 0;
>   
> -	/*
> -	 * Newer platforms can support modes higher than the maximum dot clock
> -	 * by using pipe joiner, so set the mode clock twice that of maximum
> -	 * dot clock;
> -	 */
> -	if (can_bigjoiner(data)) {
> -		igt_info("Platform supports bigjoiner with %s\n",
> -			  output->name);
> -		mode.clock *= 2;
> -	}
> -
>   	igt_create_fb(data->drm_fd,
>   		      mode.hdisplay, mode.vdisplay,
>   		      DRM_FORMAT_XRGB8888,


  reply	other threads:[~2021-10-05 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 15:35 [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Ville Syrjala
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 2/6] tests/kms_invalid_mode: Convert the max dotclock test into a subtest Ville Syrjala
2021-10-05 10:13   ` Karthik B S
2021-10-05 10:33     ` Petri Latvala
2021-10-05 10:38       ` Ville Syrjälä
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 3/6] tests/kms_invalid_mode: Move bigjoiner handling into the proper place Ville Syrjala
2021-10-05 10:15   ` Karthik B S [this message]
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 4/6] tests/kms_invalid_mode: Test various bogus timings Ville Syrjala
2021-10-05 10:22   ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 5/6] tests/kms_invalid_mode: Test clock==(U)INT_MAX Ville Syrjala
2021-10-05 10:24   ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 6/6] tests/kms_invalid_mode: Allow the test on !i915 Ville Syrjala
2021-10-05 10:27   ` Karthik B S
2021-09-16 19:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Patchwork
2021-09-22 17:16 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode (rev2) Patchwork
2021-09-22 19:09 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-10-04 12:30 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode (rev3) Patchwork
2021-10-04 14:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-05 10:09 ` [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Karthik B S
2021-10-05 11:12   ` Ville Syrjälä

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=d0e88bad-fd98-352a-a660-30971172beb8@intel.com \
    --to=karthik.b.s@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 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.