All of lore.kernel.org
 help / color / mirror / Atom feed
* [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
@ 2021-12-09  0:27 Jessica Zhang
  2021-12-09 11:26 ` Petri Latvala
                   ` (2 more replies)
  0 siblings, 3 replies; 13+ messages in thread
From: Jessica Zhang @ 2021-12-09  0:27 UTC (permalink / raw)
  To: igt-dev; +Cc: petri.latvala, quic_khsieh, swboyd, nganji, seanpaul, aravindh

Catch edge cases where driver doesn't support larger scale factors or
pipe doesn't support scaling.

Currently, a 20x20 framebuffer is passed in to be upscaled. However,
this will cause issues with other drivers as they may not support larger
scale factors or may not support scaling at all for certain planes.

This avoids failures due to invalid scale factor by trying
the original 20x20 framebuffer commit, then trying to commit larger
framebuffers up to and including unity scale.

Changes since V1:
- try_commit_with_fb_size: Changed igt_try_commit2 to
  igt_display_try_commit_atomic instead to avoid redundant commits
- try_commit_with_fb_size: Moved calls to clear framebuffer to outside
  of success condition and moved cleanup_crtc back to outside of method

Tested-on: Qualcomm RB5 (sdm845)

Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
---
 tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
 1 file changed, 46 insertions(+), 9 deletions(-)

diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
index 85db11ee..971c1532 100644
--- a/tests/kms_plane_scaling.c
+++ b/tests/kms_plane_scaling.c
@@ -1,5 +1,6 @@
 /*
  * Copyright © 2013,2014 Intel Corporation
+ * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
  *
  * Permission is hereby granted, free of charge, to any person obtaining a
  * copy of this software and associated documentation files (the "Software"),
@@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
 	igt_display_commit2(display, COMMIT_ATOMIC);
 }
 
+static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
+		                            igt_display_t *display, data_t *d,
+                                   igt_plane_t *plane,
+		                            drmModeModeInfo *mode)
+{
+	int ret;
+
+	/* Check min to full resolution upscaling */
+	igt_fb_set_position(&d->fb[0], plane, 0, 0);
+	igt_fb_set_size(&d->fb[0], plane, width, height);
+	igt_plane_set_position(plane, 0, 0);
+	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
+	igt_plane_set_rotation(plane, rot);
+
+	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
+		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
+
+	if (!ret)
+		igt_display_commit2(display, COMMIT_ATOMIC);
+
+	igt_plane_set_fb(plane, NULL);
+	igt_plane_set_position(plane, 0, 0);
+
+	return ret;
+}
+
 static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
 					 uint32_t pixel_format,
 					 uint64_t modifier, enum pipe pipe,
@@ -126,6 +153,7 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
 {
 	igt_display_t *display = &d->display;
 	int width, height;
+	int commit_ret;
 	drmModeModeInfo *mode;
 
 	cleanup_crtc(d);
@@ -139,16 +167,25 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
 		       pixel_format, modifier, 0.0, 1.0, 0.0, &d->fb[0]);
 	igt_plane_set_fb(plane, &d->fb[0]);
 
-	/* Check min to full resolution upscaling */
-	igt_fb_set_position(&d->fb[0], plane, 0, 0);
-	igt_fb_set_size(&d->fb[0], plane, width, height);
-	igt_plane_set_position(plane, 0, 0);
-	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
-	igt_plane_set_rotation(plane, rot);
-	igt_display_commit2(display, COMMIT_ATOMIC);
+	commit_ret = try_commit_with_fb_size(width, height, rot, display,
+                                        d, plane, mode);
 
-	igt_plane_set_fb(plane, NULL);
-	igt_plane_set_position(plane, 0, 0);
+	if(commit_ret == -ERANGE) {
+		igt_debug("Scaling for %dx%d plane not supported, trying scale factor of 4x\n", width, height);
+		width = height = mode->vdisplay / 4;
+		commit_ret = try_commit_with_fb_size(width, height, rot, display,
+                                            d, plane, mode);
+	}
+
+	if (commit_ret == -ERANGE) {
+		igt_debug("Scale factor of 4x (or scaling in general) not supported, trying unity scale\n");
+		width = mode->hdisplay;
+		height = mode->vdisplay;
+		commit_ret = try_commit_with_fb_size(width, height, rot, display,
+                                            d, plane, mode);
+	}
+
+	igt_assert_eq(commit_ret, 0);
 }
 
 static const igt_rotation_t rotations[] = {
-- 
2.34.1

^ permalink raw reply related	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-09  0:27 [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors Jessica Zhang
@ 2021-12-09 11:26 ` Petri Latvala
  2021-12-09 20:54   ` Jessica Zhang
  2021-12-09 19:28 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2) Patchwork
  2021-12-10  4:02 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  2 siblings, 1 reply; 13+ messages in thread
From: Petri Latvala @ 2021-12-09 11:26 UTC (permalink / raw)
  To: Jessica Zhang; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh

On Wed, Dec 08, 2021 at 04:27:16PM -0800, Jessica Zhang wrote:
> Catch edge cases where driver doesn't support larger scale factors or
> pipe doesn't support scaling.
> 
> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
> this will cause issues with other drivers as they may not support larger
> scale factors or may not support scaling at all for certain planes.
> 
> This avoids failures due to invalid scale factor by trying
> the original 20x20 framebuffer commit, then trying to commit larger
> framebuffers up to and including unity scale.
> 
> Changes since V1:
> - try_commit_with_fb_size: Changed igt_try_commit2 to
>   igt_display_try_commit_atomic instead to avoid redundant commits
> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>   of success condition and moved cleanup_crtc back to outside of method
> 
> Tested-on: Qualcomm RB5 (sdm845)
> 
> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
> ---
>  tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
>  1 file changed, 46 insertions(+), 9 deletions(-)
> 
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 85db11ee..971c1532 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -1,5 +1,6 @@
>  /*
>   * Copyright © 2013,2014 Intel Corporation
> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
>   *
>   * Permission is hereby granted, free of charge, to any person obtaining a
>   * copy of this software and associated documentation files (the "Software"),
> @@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
>  	igt_display_commit2(display, COMMIT_ATOMIC);
>  }
>  
> +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
> +		                            igt_display_t *display, data_t *d,
> +                                   igt_plane_t *plane,
> +		                            drmModeModeInfo *mode)
> +{
> +	int ret;
> +
> +	/* Check min to full resolution upscaling */
> +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
> +	igt_fb_set_size(&d->fb[0], plane, width, height);
> +	igt_plane_set_position(plane, 0, 0);
> +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
> +	igt_plane_set_rotation(plane, rot);
> +
> +	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
> +		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> +
> +	if (!ret)
> +		igt_display_commit2(display, COMMIT_ATOMIC);

Now this looks more understandable but I still have one "why"
remaining: Why test_only the commit if you're anyway going to perform
the commit? You could just have this as one try_commit, without
test_only, and let it perform it, as there's nothing done differently
here based on success/failure.



-- 
Petri Latvala


> +
> +	igt_plane_set_fb(plane, NULL);
> +	igt_plane_set_position(plane, 0, 0);
> +
> +	return ret;
> +}
> +
>  static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>  					 uint32_t pixel_format,
>  					 uint64_t modifier, enum pipe pipe,
> @@ -126,6 +153,7 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>  {
>  	igt_display_t *display = &d->display;
>  	int width, height;
> +	int commit_ret;
>  	drmModeModeInfo *mode;
>  
>  	cleanup_crtc(d);
> @@ -139,16 +167,25 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>  		       pixel_format, modifier, 0.0, 1.0, 0.0, &d->fb[0]);
>  	igt_plane_set_fb(plane, &d->fb[0]);
>  
> -	/* Check min to full resolution upscaling */
> -	igt_fb_set_position(&d->fb[0], plane, 0, 0);
> -	igt_fb_set_size(&d->fb[0], plane, width, height);
> -	igt_plane_set_position(plane, 0, 0);
> -	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
> -	igt_plane_set_rotation(plane, rot);
> -	igt_display_commit2(display, COMMIT_ATOMIC);
> +	commit_ret = try_commit_with_fb_size(width, height, rot, display,
> +                                        d, plane, mode);
>  
> -	igt_plane_set_fb(plane, NULL);
> -	igt_plane_set_position(plane, 0, 0);
> +	if(commit_ret == -ERANGE) {
> +		igt_debug("Scaling for %dx%d plane not supported, trying scale factor of 4x\n", width, height);
> +		width = height = mode->vdisplay / 4;
> +		commit_ret = try_commit_with_fb_size(width, height, rot, display,
> +                                            d, plane, mode);
> +	}
> +
> +	if (commit_ret == -ERANGE) {
> +		igt_debug("Scale factor of 4x (or scaling in general) not supported, trying unity scale\n");
> +		width = mode->hdisplay;
> +		height = mode->vdisplay;
> +		commit_ret = try_commit_with_fb_size(width, height, rot, display,
> +                                            d, plane, mode);
> +	}
> +
> +	igt_assert_eq(commit_ret, 0);
>  }
>  
>  static const igt_rotation_t rotations[] = {
> -- 
> 2.34.1
> 

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2)
  2021-12-09  0:27 [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors Jessica Zhang
  2021-12-09 11:26 ` Petri Latvala
@ 2021-12-09 19:28 ` Patchwork
  2021-12-10  4:02 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  2 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2021-12-09 19:28 UTC (permalink / raw)
  To: Jessica Zhang; +Cc: igt-dev

[-- Attachment #1: Type: text/plain, Size: 8443 bytes --]

== Series Details ==

Series: tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2)
URL   : https://patchwork.freedesktop.org/series/97584/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_10982 -> IGTPW_6482
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/index.html

Participating hosts (44 -> 36)
------------------------------

  Additional (2): fi-kbl-soraka fi-icl-u2 
  Missing    (10): fi-ilk-m540 bat-dg1-6 fi-tgl-u2 fi-hsw-4200u fi-bsw-cyan bat-adlp-6 bat-adlp-4 fi-ctg-p8600 bat-jsl-2 fi-bdw-samus 

Known issues
------------

  Here are the changes found in IGTPW_6482 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@amdgpu/amd_cs_nop@fork-gfx0:
    - fi-icl-u2:          NOTRUN -> [SKIP][1] ([fdo#109315]) +17 similar issues
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@amdgpu/amd_cs_nop@fork-gfx0.html

  * igt@gem_exec_fence@basic-busy@bcs0:
    - fi-kbl-soraka:      NOTRUN -> [SKIP][2] ([fdo#109271]) +8 similar issues
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-kbl-soraka/igt@gem_exec_fence@basic-busy@bcs0.html

  * igt@gem_exec_suspend@basic-s3:
    - fi-tgl-1115g4:      [PASS][3] -> [FAIL][4] ([i915#1888])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s3.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-tgl-1115g4/igt@gem_exec_suspend@basic-s3.html

  * igt@gem_huc_copy@huc-copy:
    - fi-skl-6600u:       NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#2190])
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@gem_huc_copy@huc-copy.html
    - fi-kbl-soraka:      NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-kbl-soraka/igt@gem_huc_copy@huc-copy.html
    - fi-icl-u2:          NOTRUN -> [SKIP][7] ([i915#2190])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@gem_huc_copy@huc-copy.html

  * igt@gem_lmem_swapping@basic:
    - fi-kbl-soraka:      NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#4613]) +3 similar issues
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-kbl-soraka/igt@gem_lmem_swapping@basic.html

  * igt@gem_lmem_swapping@parallel-random-engines:
    - fi-icl-u2:          NOTRUN -> [SKIP][9] ([i915#4613]) +3 similar issues
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@gem_lmem_swapping@parallel-random-engines.html

  * igt@gem_lmem_swapping@verify-random:
    - fi-skl-6600u:       NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#4613]) +3 similar issues
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@gem_lmem_swapping@verify-random.html

  * igt@i915_selftest@live@gt_engines:
    - fi-rkl-guc:         [PASS][11] -> [INCOMPLETE][12] ([i915#4432])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/fi-rkl-guc/igt@i915_selftest@live@gt_engines.html
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-rkl-guc/igt@i915_selftest@live@gt_engines.html

  * igt@i915_selftest@live@gt_pm:
    - fi-kbl-soraka:      NOTRUN -> [DMESG-FAIL][13] ([i915#1886] / [i915#2291])
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html

  * igt@kms_chamelium@common-hpd-after-suspend:
    - fi-kbl-soraka:      NOTRUN -> [SKIP][14] ([fdo#109271] / [fdo#111827]) +8 similar issues
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-kbl-soraka/igt@kms_chamelium@common-hpd-after-suspend.html

  * igt@kms_chamelium@hdmi-hpd-fast:
    - fi-icl-u2:          NOTRUN -> [SKIP][15] ([fdo#111827]) +8 similar issues
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html

  * igt@kms_chamelium@vga-edid-read:
    - fi-skl-6600u:       NOTRUN -> [SKIP][16] ([fdo#109271] / [fdo#111827]) +8 similar issues
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@kms_chamelium@vga-edid-read.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
    - fi-icl-u2:          NOTRUN -> [SKIP][17] ([fdo#109278]) +2 similar issues
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
    - fi-skl-6600u:       NOTRUN -> [SKIP][18] ([fdo#109271]) +2 similar issues
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html

  * igt@kms_force_connector_basic@force-load-detect:
    - fi-icl-u2:          NOTRUN -> [SKIP][19] ([fdo#109285])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@kms_force_connector_basic@force-load-detect.html

  * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
    - fi-skl-6600u:       NOTRUN -> [SKIP][20] ([fdo#109271] / [i915#533])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
    - fi-kbl-soraka:      NOTRUN -> [SKIP][21] ([fdo#109271] / [i915#533])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-kbl-soraka/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html

  * igt@kms_psr@primary_page_flip:
    - fi-skl-6600u:       NOTRUN -> [INCOMPLETE][22] ([i915#198])
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@kms_psr@primary_page_flip.html

  * igt@prime_vgem@basic-userptr:
    - fi-icl-u2:          NOTRUN -> [SKIP][23] ([i915#3301])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-icl-u2/igt@prime_vgem@basic-userptr.html

  * igt@runner@aborted:
    - fi-rkl-guc:         NOTRUN -> [FAIL][24] ([i915#3928] / [i915#4312])
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-rkl-guc/igt@runner@aborted.html

  
#### Possible fixes ####

  * igt@gem_exec_suspend@basic-s3:
    - fi-skl-6600u:       [FAIL][25] ([i915#4547]) -> [PASS][26]
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/fi-skl-6600u/igt@gem_exec_suspend@basic-s3.html
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-skl-6600u/igt@gem_exec_suspend@basic-s3.html

  * igt@kms_frontbuffer_tracking@basic:
    - fi-cml-u2:          [DMESG-WARN][27] ([i915#4269]) -> [PASS][28]
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html

  
  [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
  [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
  [fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
  [fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
  [fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
  [i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
  [i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
  [i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
  [i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
  [i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
  [i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
  [i915#3928]: https://gitlab.freedesktop.org/drm/intel/issues/3928
  [i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
  [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
  [i915#4432]: https://gitlab.freedesktop.org/drm/intel/issues/4432
  [i915#4547]: https://gitlab.freedesktop.org/drm/intel/issues/4547
  [i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
  [i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533


Build changes
-------------

  * CI: CI-20190529 -> None
  * IGT: IGT_6304 -> IGTPW_6482

  CI-20190529: 20190529
  CI_DRM_10982: 12d989f50a9dd0fec7a7b4ec3df1e29a0e690fc5 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGTPW_6482: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/index.html
  IGT_6304: ef0df2fbe5847fe5c4426b8a86a0b101588d0586 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/index.html

[-- Attachment #2: Type: text/html, Size: 10672 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-09 11:26 ` Petri Latvala
@ 2021-12-09 20:54   ` Jessica Zhang
  2021-12-10  6:11     ` Petri Latvala
  0 siblings, 1 reply; 13+ messages in thread
From: Jessica Zhang @ 2021-12-09 20:54 UTC (permalink / raw)
  To: Petri Latvala; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh



On 12/9/2021 3:26 AM, Petri Latvala wrote:
> On Wed, Dec 08, 2021 at 04:27:16PM -0800, Jessica Zhang wrote:
>> Catch edge cases where driver doesn't support larger scale factors or
>> pipe doesn't support scaling.
>>
>> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
>> this will cause issues with other drivers as they may not support larger
>> scale factors or may not support scaling at all for certain planes.
>>
>> This avoids failures due to invalid scale factor by trying
>> the original 20x20 framebuffer commit, then trying to commit larger
>> framebuffers up to and including unity scale.
>>
>> Changes since V1:
>> - try_commit_with_fb_size: Changed igt_try_commit2 to
>>    igt_display_try_commit_atomic instead to avoid redundant commits
>> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>>    of success condition and moved cleanup_crtc back to outside of method
>>
>> Tested-on: Qualcomm RB5 (sdm845)
>>
>> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
>> ---
>>   tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
>>   1 file changed, 46 insertions(+), 9 deletions(-)
>>
>> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
>> index 85db11ee..971c1532 100644
>> --- a/tests/kms_plane_scaling.c
>> +++ b/tests/kms_plane_scaling.c
>> @@ -1,5 +1,6 @@
>>   /*
>>    * Copyright © 2013,2014 Intel Corporation
>> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
>>    *
>>    * Permission is hereby granted, free of charge, to any person obtaining a
>>    * copy of this software and associated documentation files (the "Software"),
>> @@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
>>   	igt_display_commit2(display, COMMIT_ATOMIC);
>>   }
>>   
>> +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
>> +		                            igt_display_t *display, data_t *d,
>> +                                   igt_plane_t *plane,
>> +		                            drmModeModeInfo *mode)
>> +{
>> +	int ret;
>> +
>> +	/* Check min to full resolution upscaling */
>> +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
>> +	igt_fb_set_size(&d->fb[0], plane, width, height);
>> +	igt_plane_set_position(plane, 0, 0);
>> +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>> +	igt_plane_set_rotation(plane, rot);
>> +
>> +	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
>> +		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
>> +
>> +	if (!ret)
>> +		igt_display_commit2(display, COMMIT_ATOMIC);
> 
> Now this looks more understandable but I still have one "why"
> remaining: Why test_only the commit if you're anyway going to perform
> the commit? You could just have this as one try_commit, without
> test_only, and let it perform it, as there's nothing done differently
> here based on success/failure.
> 
The original intention was to test that a commit will go through before 
actually doing the commit. This way, the test would be more optimized 
since we would only perform a commit when we know it will succeed. 
Otherwise, in a worst case scenario, we'd be performing 3 or 4 commits 
per pipe/format for a subtest like pipe-*-scaler-with-pixel-format.

Thanks,
Jessica Zhang
> 
> 

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [igt-dev] ✓ Fi.CI.IGT: success for tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2)
  2021-12-09  0:27 [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors Jessica Zhang
  2021-12-09 11:26 ` Petri Latvala
  2021-12-09 19:28 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2) Patchwork
@ 2021-12-10  4:02 ` Patchwork
  2 siblings, 0 replies; 13+ messages in thread
From: Patchwork @ 2021-12-10  4:02 UTC (permalink / raw)
  To: Jessica Zhang; +Cc: igt-dev

[-- Attachment #1: Type: text/plain, Size: 30317 bytes --]

== Series Details ==

Series: tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2)
URL   : https://patchwork.freedesktop.org/series/97584/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_10982_full -> IGTPW_6482_full
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/index.html

Participating hosts (10 -> 7)
------------------------------

  Missing    (3): pig-skl-6260u pig-glk-j5005 shard-rkl 

Known issues
------------

  Here are the changes found in IGTPW_6482_full that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@gem_ctx_persistence@hang:
    - shard-snb:          NOTRUN -> [SKIP][1] ([fdo#109271] / [i915#1099])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-snb2/igt@gem_ctx_persistence@hang.html

  * igt@gem_ctx_sseu@invalid-args:
    - shard-tglb:         NOTRUN -> [SKIP][2] ([i915#280])
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@gem_ctx_sseu@invalid-args.html

  * igt@gem_exec_balancer@parallel-bb-first:
    - shard-tglb:         NOTRUN -> [SKIP][3] ([i915#4525]) +1 similar issue
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb2/igt@gem_exec_balancer@parallel-bb-first.html

  * igt@gem_exec_balancer@parallel-ordering:
    - shard-iclb:         NOTRUN -> [SKIP][4] ([i915#4525]) +1 similar issue
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb3/igt@gem_exec_balancer@parallel-ordering.html

  * igt@gem_exec_fair@basic-none-solo@rcs0:
    - shard-kbl:          [PASS][5] -> [FAIL][6] ([i915#2842]) +1 similar issue
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-kbl7/igt@gem_exec_fair@basic-none-solo@rcs0.html
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl7/igt@gem_exec_fair@basic-none-solo@rcs0.html

  * igt@gem_exec_fair@basic-pace@vcs1:
    - shard-iclb:         NOTRUN -> [FAIL][7] ([i915#2842])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb1/igt@gem_exec_fair@basic-pace@vcs1.html

  * igt@gem_exec_fair@basic-pace@vecs0:
    - shard-glk:          [PASS][8] -> [FAIL][9] ([i915#2842]) +3 similar issues
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk1/igt@gem_exec_fair@basic-pace@vecs0.html
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk3/igt@gem_exec_fair@basic-pace@vecs0.html

  * igt@gem_mmap_gtt@coherency:
    - shard-tglb:         NOTRUN -> [SKIP][10] ([fdo#111656])
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb5/igt@gem_mmap_gtt@coherency.html
    - shard-iclb:         NOTRUN -> [SKIP][11] ([fdo#109292])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb3/igt@gem_mmap_gtt@coherency.html

  * igt@gem_ppgtt@flink-and-close-vma-leak:
    - shard-glk:          [PASS][12] -> [FAIL][13] ([i915#644])
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk4/igt@gem_ppgtt@flink-and-close-vma-leak.html
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk2/igt@gem_ppgtt@flink-and-close-vma-leak.html

  * igt@gem_pxp@fail-invalid-protected-context:
    - shard-tglb:         NOTRUN -> [SKIP][14] ([i915#4270])
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@gem_pxp@fail-invalid-protected-context.html
    - shard-iclb:         NOTRUN -> [SKIP][15] ([i915#4270])
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@gem_pxp@fail-invalid-protected-context.html

  * igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs:
    - shard-iclb:         NOTRUN -> [SKIP][16] ([i915#768])
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb2/igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs.html

  * igt@gem_softpin@evict-snoop:
    - shard-iclb:         NOTRUN -> [SKIP][17] ([fdo#109312])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb1/igt@gem_softpin@evict-snoop.html
    - shard-tglb:         NOTRUN -> [SKIP][18] ([fdo#109312])
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb5/igt@gem_softpin@evict-snoop.html

  * igt@gem_userptr_blits@readonly-unsync:
    - shard-tglb:         NOTRUN -> [SKIP][19] ([i915#3297])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@gem_userptr_blits@readonly-unsync.html
    - shard-iclb:         NOTRUN -> [SKIP][20] ([i915#3297])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb3/igt@gem_userptr_blits@readonly-unsync.html

  * igt@gem_userptr_blits@vma-merge:
    - shard-apl:          NOTRUN -> [FAIL][21] ([i915#3318])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl1/igt@gem_userptr_blits@vma-merge.html

  * igt@gen9_exec_parse@cmd-crossing-page:
    - shard-tglb:         NOTRUN -> [SKIP][22] ([i915#2856]) +1 similar issue
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb1/igt@gen9_exec_parse@cmd-crossing-page.html

  * igt@gen9_exec_parse@unaligned-access:
    - shard-iclb:         NOTRUN -> [SKIP][23] ([i915#2856]) +1 similar issue
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb6/igt@gen9_exec_parse@unaligned-access.html

  * igt@i915_pm_dc@dc6-dpms:
    - shard-iclb:         [PASS][24] -> [FAIL][25] ([i915#454])
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb7/igt@i915_pm_dc@dc6-dpms.html
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html

  * igt@i915_pm_rpm@gem-execbuf-stress-pc8:
    - shard-iclb:         NOTRUN -> [SKIP][26] ([fdo#109293] / [fdo#109506])
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb5/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html
    - shard-tglb:         NOTRUN -> [SKIP][27] ([fdo#109506] / [i915#2411])
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb7/igt@i915_pm_rpm@gem-execbuf-stress-pc8.html

  * igt@i915_suspend@fence-restore-untiled:
    - shard-apl:          [PASS][28] -> [DMESG-WARN][29] ([i915#180])
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-apl2/igt@i915_suspend@fence-restore-untiled.html
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl2/igt@i915_suspend@fence-restore-untiled.html

  * igt@kms_atomic_transition@plane-all-modeset-transition-fencing:
    - shard-iclb:         NOTRUN -> [SKIP][30] ([i915#1769])
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html
    - shard-tglb:         NOTRUN -> [SKIP][31] ([i915#1769])
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html

  * igt@kms_big_fb@linear-32bpp-rotate-270:
    - shard-iclb:         NOTRUN -> [SKIP][32] ([fdo#110725] / [fdo#111614])
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb3/igt@kms_big_fb@linear-32bpp-rotate-270.html
    - shard-tglb:         NOTRUN -> [SKIP][33] ([fdo#111614])
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb5/igt@kms_big_fb@linear-32bpp-rotate-270.html

  * igt@kms_big_fb@yf-tiled-16bpp-rotate-270:
    - shard-tglb:         NOTRUN -> [SKIP][34] ([fdo#111615])
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@kms_big_fb@yf-tiled-16bpp-rotate-270.html

  * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip:
    - shard-apl:          NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#3777]) +2 similar issues
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl1/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html

  * igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
    - shard-apl:          NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#3886]) +8 similar issues
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
    - shard-glk:          NOTRUN -> [SKIP][37] ([fdo#109271] / [i915#3886]) +3 similar issues
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk1/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html

  * igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
    - shard-kbl:          NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#3886]) +6 similar issues
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl3/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html

  * igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_ccs:
    - shard-tglb:         NOTRUN -> [SKIP][39] ([i915#3689]) +2 similar issues
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_ccs.html

  * igt@kms_ccs@pipe-b-crc-primary-basic-yf_tiled_ccs:
    - shard-tglb:         NOTRUN -> [SKIP][40] ([fdo#111615] / [i915#3689]) +4 similar issues
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb7/igt@kms_ccs@pipe-b-crc-primary-basic-yf_tiled_ccs.html

  * igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
    - shard-iclb:         NOTRUN -> [SKIP][41] ([fdo#109278] / [i915#3886]) +4 similar issues
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
    - shard-tglb:         NOTRUN -> [SKIP][42] ([i915#3689] / [i915#3886]) +2 similar issues
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb6/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html

  * igt@kms_chamelium@dp-crc-multiple:
    - shard-apl:          NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +18 similar issues
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl1/igt@kms_chamelium@dp-crc-multiple.html

  * igt@kms_chamelium@hdmi-hpd-storm:
    - shard-kbl:          NOTRUN -> [SKIP][44] ([fdo#109271] / [fdo#111827]) +8 similar issues
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl7/igt@kms_chamelium@hdmi-hpd-storm.html

  * igt@kms_color@pipe-d-ctm-max:
    - shard-iclb:         NOTRUN -> [SKIP][45] ([fdo#109278] / [i915#1149])
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb7/igt@kms_color@pipe-d-ctm-max.html

  * igt@kms_color_chamelium@pipe-a-ctm-0-75:
    - shard-tglb:         NOTRUN -> [SKIP][46] ([fdo#109284] / [fdo#111827]) +8 similar issues
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb1/igt@kms_color_chamelium@pipe-a-ctm-0-75.html
    - shard-snb:          NOTRUN -> [SKIP][47] ([fdo#109271] / [fdo#111827]) +3 similar issues
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-snb5/igt@kms_color_chamelium@pipe-a-ctm-0-75.html

  * igt@kms_color_chamelium@pipe-c-ctm-0-75:
    - shard-glk:          NOTRUN -> [SKIP][48] ([fdo#109271] / [fdo#111827]) +3 similar issues
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk5/igt@kms_color_chamelium@pipe-c-ctm-0-75.html

  * igt@kms_color_chamelium@pipe-c-ctm-max:
    - shard-iclb:         NOTRUN -> [SKIP][49] ([fdo#109284] / [fdo#111827]) +4 similar issues
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_color_chamelium@pipe-c-ctm-max.html

  * igt@kms_content_protection@legacy:
    - shard-apl:          NOTRUN -> [TIMEOUT][50] ([i915#1319])
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl4/igt@kms_content_protection@legacy.html

  * igt@kms_cursor_crc@pipe-a-cursor-suspend:
    - shard-kbl:          NOTRUN -> [DMESG-WARN][51] ([i915#180])
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl1/igt@kms_cursor_crc@pipe-a-cursor-suspend.html

  * igt@kms_cursor_crc@pipe-c-cursor-32x32-random:
    - shard-tglb:         NOTRUN -> [SKIP][52] ([i915#3319])
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb7/igt@kms_cursor_crc@pipe-c-cursor-32x32-random.html

  * igt@kms_cursor_crc@pipe-c-cursor-max-size-offscreen:
    - shard-tglb:         NOTRUN -> [SKIP][53] ([i915#3359]) +5 similar issues
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb7/igt@kms_cursor_crc@pipe-c-cursor-max-size-offscreen.html

  * igt@kms_cursor_crc@pipe-d-cursor-512x170-sliding:
    - shard-tglb:         NOTRUN -> [SKIP][54] ([fdo#109279] / [i915#3359])
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb6/igt@kms_cursor_crc@pipe-d-cursor-512x170-sliding.html

  * igt@kms_cursor_crc@pipe-d-cursor-suspend:
    - shard-kbl:          NOTRUN -> [SKIP][55] ([fdo#109271]) +114 similar issues
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl2/igt@kms_cursor_crc@pipe-d-cursor-suspend.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size:
    - shard-tglb:         NOTRUN -> [SKIP][56] ([i915#4103])
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb6/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size.html

  * igt@kms_cursor_legacy@cursora-vs-flipb-varying-size:
    - shard-iclb:         NOTRUN -> [SKIP][57] ([fdo#109274] / [fdo#109278])
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb7/igt@kms_cursor_legacy@cursora-vs-flipb-varying-size.html

  * igt@kms_cursor_legacy@flip-vs-cursor-toggle:
    - shard-iclb:         [PASS][58] -> [FAIL][59] ([i915#2346])
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb1/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb7/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html

  * igt@kms_dsc@basic-dsc-enable:
    - shard-iclb:         NOTRUN -> [SKIP][60] ([i915#3840])
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb6/igt@kms_dsc@basic-dsc-enable.html

  * igt@kms_fbcon_fbt@fbc-suspend:
    - shard-kbl:          [PASS][61] -> [INCOMPLETE][62] ([i915#180] / [i915#636])
   [61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html

  * igt@kms_flip@2x-nonexisting-fb-interruptible:
    - shard-iclb:         NOTRUN -> [SKIP][63] ([fdo#109274]) +4 similar issues
   [63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb6/igt@kms_flip@2x-nonexisting-fb-interruptible.html

  * igt@kms_flip@flip-vs-blocking-wf-vblank@a-hdmi-a1:
    - shard-glk:          [PASS][64] -> [FAIL][65] ([i915#2122])
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk3/igt@kms_flip@flip-vs-blocking-wf-vblank@a-hdmi-a1.html
   [65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk2/igt@kms_flip@flip-vs-blocking-wf-vblank@a-hdmi-a1.html

  * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt:
    - shard-iclb:         NOTRUN -> [SKIP][66] ([fdo#109280]) +7 similar issues
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt.html

  * igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite:
    - shard-tglb:         NOTRUN -> [SKIP][67] ([fdo#111825]) +15 similar issues
   [67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb5/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-spr-indfb-draw-pwrite.html

  * igt@kms_hdr@bpc-switch-suspend:
    - shard-kbl:          [PASS][68] -> [DMESG-WARN][69] ([i915#180])
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-kbl2/igt@kms_hdr@bpc-switch-suspend.html
   [69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl1/igt@kms_hdr@bpc-switch-suspend.html

  * igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
    - shard-apl:          NOTRUN -> [FAIL][70] ([fdo#108145] / [i915#265])
   [70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl2/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html

  * igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
    - shard-kbl:          NOTRUN -> [FAIL][71] ([fdo#108145] / [i915#265])
   [71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl6/igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb.html

  * igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb:
    - shard-apl:          NOTRUN -> [FAIL][72] ([i915#265])
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl4/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html
    - shard-kbl:          NOTRUN -> [FAIL][73] ([i915#265])
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl6/igt@kms_plane_alpha_blend@pipe-b-alpha-transparent-fb.html

  * igt@kms_plane_cursor@pipe-d-viewport-size-256:
    - shard-glk:          NOTRUN -> [SKIP][74] ([fdo#109271]) +39 similar issues
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk5/igt@kms_plane_cursor@pipe-d-viewport-size-256.html

  * igt@kms_plane_lowres@pipe-c-tiling-none:
    - shard-iclb:         NOTRUN -> [SKIP][75] ([i915#3536])
   [75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb6/igt@kms_plane_lowres@pipe-c-tiling-none.html
    - shard-tglb:         NOTRUN -> [SKIP][76] ([i915#3536])
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb1/igt@kms_plane_lowres@pipe-c-tiling-none.html

  * igt@kms_plane_multiple@atomic-pipe-b-tiling-yf:
    - shard-tglb:         NOTRUN -> [SKIP][77] ([fdo#111615] / [fdo#112054])
   [77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb1/igt@kms_plane_multiple@atomic-pipe-b-tiling-yf.html

  * igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
    - shard-tglb:         NOTRUN -> [SKIP][78] ([i915#2920])
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb6/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html

  * igt@kms_psr2_su@page_flip-xrgb8888:
    - shard-tglb:         NOTRUN -> [SKIP][79] ([i915#1911])
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb7/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-kbl:          NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#658]) +1 similar issue
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl7/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-apl:          NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#658]) +3 similar issues
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl6/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-glk:          NOTRUN -> [SKIP][82] ([fdo#109271] / [i915#658])
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk1/igt@kms_psr2_su@page_flip-xrgb8888.html
    - shard-iclb:         NOTRUN -> [FAIL][83] ([i915#4148])
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb2/igt@kms_psr2_su@page_flip-xrgb8888.html

  * igt@kms_psr@psr2_basic:
    - shard-tglb:         NOTRUN -> [FAIL][84] ([i915#132] / [i915#3467])
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@kms_psr@psr2_basic.html
    - shard-iclb:         NOTRUN -> [SKIP][85] ([fdo#109441])
   [85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb7/igt@kms_psr@psr2_basic.html

  * igt@kms_psr@psr2_sprite_blt:
    - shard-iclb:         [PASS][86] -> [SKIP][87] ([fdo#109441]) +2 similar issues
   [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb2/igt@kms_psr@psr2_sprite_blt.html
   [87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_psr@psr2_sprite_blt.html

  * igt@kms_setmode@basic:
    - shard-glk:          [PASS][88] -> [FAIL][89] ([i915#31])
   [88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk6/igt@kms_setmode@basic.html
   [89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk3/igt@kms_setmode@basic.html

  * igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend:
    - shard-iclb:         NOTRUN -> [SKIP][90] ([fdo#109278]) +14 similar issues
   [90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_vblank@pipe-d-ts-continuation-dpms-suspend.html

  * igt@kms_vblank@pipe-d-wait-idle:
    - shard-kbl:          NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#533]) +1 similar issue
   [91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl4/igt@kms_vblank@pipe-d-wait-idle.html
    - shard-apl:          NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#533]) +1 similar issue
   [92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl1/igt@kms_vblank@pipe-d-wait-idle.html
    - shard-glk:          NOTRUN -> [SKIP][93] ([fdo#109271] / [i915#533]) +1 similar issue
   [93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk4/igt@kms_vblank@pipe-d-wait-idle.html

  * igt@perf@gen12-oa-tlb-invalidate:
    - shard-iclb:         NOTRUN -> [SKIP][94] ([fdo#109289]) +1 similar issue
   [94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb5/igt@perf@gen12-oa-tlb-invalidate.html

  * igt@perf@polling-parameterized:
    - shard-apl:          [PASS][95] -> [FAIL][96] ([i915#1542])
   [95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-apl7/igt@perf@polling-parameterized.html
   [96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl2/igt@perf@polling-parameterized.html

  * igt@perf_pmu@module-unload:
    - shard-apl:          NOTRUN -> [INCOMPLETE][97] ([i915#1982] / [i915#262])
   [97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl8/igt@perf_pmu@module-unload.html

  * igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name:
    - shard-apl:          NOTRUN -> [SKIP][98] ([fdo#109271]) +193 similar issues
   [98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl6/igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name.html

  * igt@sysfs_clients@sema-50:
    - shard-iclb:         NOTRUN -> [SKIP][99] ([i915#2994])
   [99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb2/igt@sysfs_clients@sema-50.html
    - shard-kbl:          NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#2994]) +1 similar issue
   [100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl7/igt@sysfs_clients@sema-50.html
    - shard-apl:          NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#2994]) +2 similar issues
   [101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl4/igt@sysfs_clients@sema-50.html
    - shard-glk:          NOTRUN -> [SKIP][102] ([fdo#109271] / [i915#2994])
   [102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk9/igt@sysfs_clients@sema-50.html
    - shard-tglb:         NOTRUN -> [SKIP][103] ([i915#2994])
   [103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb2/igt@sysfs_clients@sema-50.html

  * igt@sysfs_heartbeat_interval@precise@rcs0:
    - shard-snb:          NOTRUN -> [SKIP][104] ([fdo#109271]) +83 similar issues
   [104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-snb6/igt@sysfs_heartbeat_interval@precise@rcs0.html

  * igt@sysfs_timeslice_duration@timeout@vecs0:
    - shard-apl:          [PASS][105] -> [FAIL][106] ([i915#1755])
   [105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-apl2/igt@sysfs_timeslice_duration@timeout@vecs0.html
   [106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl2/igt@sysfs_timeslice_duration@timeout@vecs0.html

  
#### Possible fixes ####

  * igt@gem_ctx_isolation@preservation-s3@vecs0:
    - shard-kbl:          [DMESG-WARN][107] ([i915#180]) -> [PASS][108] +1 similar issue
   [107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-kbl1/igt@gem_ctx_isolation@preservation-s3@vecs0.html
   [108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl1/igt@gem_ctx_isolation@preservation-s3@vecs0.html

  * igt@gem_eio@unwedge-stress:
    - shard-tglb:         [TIMEOUT][109] ([i915#3063] / [i915#3648]) -> [PASS][110]
   [109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-tglb6/igt@gem_eio@unwedge-stress.html
   [110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb3/igt@gem_eio@unwedge-stress.html

  * igt@gem_exec_fair@basic-none-rrul@rcs0:
    - shard-glk:          [FAIL][111] ([i915#2842]) -> [PASS][112] +1 similar issue
   [111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk8/igt@gem_exec_fair@basic-none-rrul@rcs0.html
   [112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk5/igt@gem_exec_fair@basic-none-rrul@rcs0.html

  * igt@gem_exec_fair@basic-pace@bcs0:
    - shard-tglb:         [FAIL][113] ([i915#2842]) -> [PASS][114]
   [113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-tglb2/igt@gem_exec_fair@basic-pace@bcs0.html
   [114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb2/igt@gem_exec_fair@basic-pace@bcs0.html

  * igt@gem_huc_copy@huc-copy:
    - shard-tglb:         [SKIP][115] ([i915#2190]) -> [PASS][116]
   [115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-tglb6/igt@gem_huc_copy@huc-copy.html
   [116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb5/igt@gem_huc_copy@huc-copy.html

  * igt@i915_suspend@sysfs-reader:
    - shard-apl:          [DMESG-WARN][117] ([i915#180]) -> [PASS][118] +4 similar issues
   [117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-apl2/igt@i915_suspend@sysfs-reader.html
   [118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-apl3/igt@i915_suspend@sysfs-reader.html

  * igt@kms_big_fb@x-tiled-32bpp-rotate-0:
    - shard-glk:          [DMESG-WARN][119] ([i915#118]) -> [PASS][120] +1 similar issue
   [119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk3/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html
   [120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk9/igt@kms_big_fb@x-tiled-32bpp-rotate-0.html

  * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
    - shard-iclb:         [FAIL][121] ([i915#2346]) -> [PASS][122]
   [121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html
   [122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb2/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions.html

  * igt@kms_flip@flip-vs-suspend-interruptible@b-edp1:
    - shard-tglb:         [DMESG-WARN][123] ([i915#2411] / [i915#2867]) -> [PASS][124]
   [123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-tglb3/igt@kms_flip@flip-vs-suspend-interruptible@b-edp1.html
   [124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb5/igt@kms_flip@flip-vs-suspend-interruptible@b-edp1.html

  * igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
    - shard-kbl:          [INCOMPLETE][125] ([i915#636]) -> [PASS][126]
   [125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-kbl2/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
   [126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html

  * igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
    - shard-iclb:         [SKIP][127] ([i915#3701]) -> [PASS][128] +1 similar issue
   [127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
   [128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb7/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html

  * igt@kms_hdmi_inject@inject-audio:
    - shard-tglb:         [SKIP][129] ([i915#433]) -> [PASS][130]
   [129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-tglb5/igt@kms_hdmi_inject@inject-audio.html
   [130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-tglb8/igt@kms_hdmi_inject@inject-audio.html

  * igt@kms_psr@psr2_cursor_plane_move:
    - shard-iclb:         [SKIP][131] ([fdo#109441]) -> [PASS][132] +1 similar issue
   [131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
   [132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html

  
#### Warnings ####

  * igt@i915_pm_rc6_residency@rc6-fence:
    - shard-iclb:         [WARN][133] ([i915#2684]) -> [WARN][134] ([i915#1804] / [i915#2684])
   [133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb1/igt@i915_pm_rc6_residency@rc6-fence.html
   [134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@i915_pm_rc6_residency@rc6-fence.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt:
    - shard-glk:          [SKIP][135] ([fdo#109271] / [i915#1888]) -> [SKIP][136] ([fdo#109271])
   [135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-glk4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html
   [136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-glk9/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html

  * igt@kms_psr2_sf@plane-move-sf-dmg-area-3:
    - shard-iclb:         [SKIP][137] ([i915#658]) -> [SKIP][138] ([i915#2920]) +1 similar issue
   [137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb1/igt@kms_psr2_sf@plane-move-sf-dmg-area-3.html
   [138]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb2/igt@kms_psr2_sf@plane-move-sf-dmg-area-3.html

  * igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5:
    - shard-iclb:         [SKIP][139] ([i915#2920]) -> [SKIP][140] ([i915#658]) +2 similar issues
   [139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10982/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html
   [140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/shard-iclb4/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html

  * igt@runner@aborted:
    - shard-kbl:          ([FAIL][141], [FAIL][142], [FAIL][143], [FAIL][144], [FAIL][145]) ([i915#1436] / [i915#180] / [i915#2426] / [i915#3002] / [i915#3363] / [i915#4312]) -> ([FAIL][146], [FAIL][147], [FAIL][148], [FAIL][149], [FAIL][150], [FAIL][151], [FAIL][152]) ([i915#1436] / [i915#180] / [i915#1

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6482/index.html

[-- Attachment #2: Type: text/html, Size: 33786 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-09 20:54   ` Jessica Zhang
@ 2021-12-10  6:11     ` Petri Latvala
  2021-12-14  0:50       ` Jessica Zhang
  0 siblings, 1 reply; 13+ messages in thread
From: Petri Latvala @ 2021-12-10  6:11 UTC (permalink / raw)
  To: Jessica Zhang; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh

On Thu, Dec 09, 2021 at 12:54:58PM -0800, Jessica Zhang wrote:
> 
> 
> On 12/9/2021 3:26 AM, Petri Latvala wrote:
> > On Wed, Dec 08, 2021 at 04:27:16PM -0800, Jessica Zhang wrote:
> > > Catch edge cases where driver doesn't support larger scale factors or
> > > pipe doesn't support scaling.
> > > 
> > > Currently, a 20x20 framebuffer is passed in to be upscaled. However,
> > > this will cause issues with other drivers as they may not support larger
> > > scale factors or may not support scaling at all for certain planes.
> > > 
> > > This avoids failures due to invalid scale factor by trying
> > > the original 20x20 framebuffer commit, then trying to commit larger
> > > framebuffers up to and including unity scale.
> > > 
> > > Changes since V1:
> > > - try_commit_with_fb_size: Changed igt_try_commit2 to
> > >    igt_display_try_commit_atomic instead to avoid redundant commits
> > > - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
> > >    of success condition and moved cleanup_crtc back to outside of method
> > > 
> > > Tested-on: Qualcomm RB5 (sdm845)
> > > 
> > > Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
> > > ---
> > >   tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
> > >   1 file changed, 46 insertions(+), 9 deletions(-)
> > > 
> > > diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> > > index 85db11ee..971c1532 100644
> > > --- a/tests/kms_plane_scaling.c
> > > +++ b/tests/kms_plane_scaling.c
> > > @@ -1,5 +1,6 @@
> > >   /*
> > >    * Copyright © 2013,2014 Intel Corporation
> > > + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
> > >    *
> > >    * Permission is hereby granted, free of charge, to any person obtaining a
> > >    * copy of this software and associated documentation files (the "Software"),
> > > @@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
> > >   	igt_display_commit2(display, COMMIT_ATOMIC);
> > >   }
> > > +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
> > > +		                            igt_display_t *display, data_t *d,
> > > +                                   igt_plane_t *plane,
> > > +		                            drmModeModeInfo *mode)
> > > +{
> > > +	int ret;
> > > +
> > > +	/* Check min to full resolution upscaling */
> > > +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
> > > +	igt_fb_set_size(&d->fb[0], plane, width, height);
> > > +	igt_plane_set_position(plane, 0, 0);
> > > +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
> > > +	igt_plane_set_rotation(plane, rot);
> > > +
> > > +	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
> > > +		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> > > +
> > > +	if (!ret)
> > > +		igt_display_commit2(display, COMMIT_ATOMIC);
> > 
> > Now this looks more understandable but I still have one "why"
> > remaining: Why test_only the commit if you're anyway going to perform
> > the commit? You could just have this as one try_commit, without
> > test_only, and let it perform it, as there's nothing done differently
> > here based on success/failure.
> > 
> The original intention was to test that a commit will go through before
> actually doing the commit. This way, the test would be more optimized since
> we would only perform a commit when we know it will succeed. Otherwise, in a
> worst case scenario, we'd be performing 3 or 4 commits per pipe/format for a
> subtest like pipe-*-scaler-with-pixel-format.

But the kernel does the same checks for TEST_ONLY as for actually
doing the commit. For this kind of optimization assertion I have to
ask for some numbers to prove it's saving time enough to be worth of
the more complicated code.

Doing a TEST_ONLY commit followed by doing the same commit without
TEST_ONLY surely is slower when the commit will succeed at least.


-- 
Petri Latvala

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-10  6:11     ` Petri Latvala
@ 2021-12-14  0:50       ` Jessica Zhang
  2021-12-14  9:43         ` Petri Latvala
  0 siblings, 1 reply; 13+ messages in thread
From: Jessica Zhang @ 2021-12-14  0:50 UTC (permalink / raw)
  To: Petri Latvala; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh



On 12/9/2021 10:11 PM, Petri Latvala wrote:
> On Thu, Dec 09, 2021 at 12:54:58PM -0800, Jessica Zhang wrote:
>>
>>
>> On 12/9/2021 3:26 AM, Petri Latvala wrote:
>>> On Wed, Dec 08, 2021 at 04:27:16PM -0800, Jessica Zhang wrote:
>>>> Catch edge cases where driver doesn't support larger scale factors or
>>>> pipe doesn't support scaling.
>>>>
>>>> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
>>>> this will cause issues with other drivers as they may not support larger
>>>> scale factors or may not support scaling at all for certain planes.
>>>>
>>>> This avoids failures due to invalid scale factor by trying
>>>> the original 20x20 framebuffer commit, then trying to commit larger
>>>> framebuffers up to and including unity scale.
>>>>
>>>> Changes since V1:
>>>> - try_commit_with_fb_size: Changed igt_try_commit2 to
>>>>     igt_display_try_commit_atomic instead to avoid redundant commits
>>>> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>>>>     of success condition and moved cleanup_crtc back to outside of method
>>>>
>>>> Tested-on: Qualcomm RB5 (sdm845)
>>>>
>>>> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
>>>> ---
>>>>    tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
>>>>    1 file changed, 46 insertions(+), 9 deletions(-)
>>>>
>>>> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
>>>> index 85db11ee..971c1532 100644
>>>> --- a/tests/kms_plane_scaling.c
>>>> +++ b/tests/kms_plane_scaling.c
>>>> @@ -1,5 +1,6 @@
>>>>    /*
>>>>     * Copyright © 2013,2014 Intel Corporation
>>>> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
>>>>     *
>>>>     * Permission is hereby granted, free of charge, to any person obtaining a
>>>>     * copy of this software and associated documentation files (the "Software"),
>>>> @@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
>>>>    	igt_display_commit2(display, COMMIT_ATOMIC);
>>>>    }
>>>> +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
>>>> +		                            igt_display_t *display, data_t *d,
>>>> +                                   igt_plane_t *plane,
>>>> +		                            drmModeModeInfo *mode)
>>>> +{
>>>> +	int ret;
>>>> +
>>>> +	/* Check min to full resolution upscaling */
>>>> +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
>>>> +	igt_fb_set_size(&d->fb[0], plane, width, height);
>>>> +	igt_plane_set_position(plane, 0, 0);
>>>> +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>>>> +	igt_plane_set_rotation(plane, rot);
>>>> +
>>>> +	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
>>>> +		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
>>>> +
>>>> +	if (!ret)
>>>> +		igt_display_commit2(display, COMMIT_ATOMIC);
>>>
>>> Now this looks more understandable but I still have one "why"
>>> remaining: Why test_only the commit if you're anyway going to perform
>>> the commit? You could just have this as one try_commit, without
>>> test_only, and let it perform it, as there's nothing done differently
>>> here based on success/failure.
>>>
>> The original intention was to test that a commit will go through before
>> actually doing the commit. This way, the test would be more optimized since
>> we would only perform a commit when we know it will succeed. Otherwise, in a
>> worst case scenario, we'd be performing 3 or 4 commits per pipe/format for a
>> subtest like pipe-*-scaler-with-pixel-format.
> 
> But the kernel does the same checks for TEST_ONLY as for actually
> doing the commit. For this kind of optimization assertion I have to
> ask for some numbers to prove it's saving time enough to be worth of
> the more complicated code.
> 
> Doing a TEST_ONLY commit followed by doing the same commit without
> TEST_ONLY surely is slower when the commit will succeed at least.
> 

Sorry if this wasn't clear in my previous reply -- I'm focusing on 
optimizing for cases where scaling a 20x20 buffer isn't supported and 
for failure cases. For example, if we just call try_commit, we would be 
doing 3 commits per format per pipe in cases where the driver only 
supports unity scale. Since TEST_ONLY will only perform a check without 
performing an actual commit [1], wouldn't it be more optimal to only 
perform a commit if the commit will succeed in cases like this?

This approach is based on instances of try_commit_atomic in other tests 
[2, 3] where we catch an error from the commit and adjust the test 
accordingly, which is what this patch wants to emulate.

Thanks,
Jessica Zhang

[1] 
https://gitlab.freedesktop.org/drm/msm/-/blob/msm-next/drivers/gpu/drm/drm_atomic_uapi.c#L1456
[2] 
https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/blob/master/tests/kms_plane_scaling.c#L660
[3] 
https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/blob/master/tests/kms_atomic_transition.c#L75

> 

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-14  0:50       ` Jessica Zhang
@ 2021-12-14  9:43         ` Petri Latvala
  2021-12-15 19:59           ` Jessica Zhang
  0 siblings, 1 reply; 13+ messages in thread
From: Petri Latvala @ 2021-12-14  9:43 UTC (permalink / raw)
  To: Jessica Zhang; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh

On Mon, Dec 13, 2021 at 04:50:26PM -0800, Jessica Zhang wrote:
> 
> 
> On 12/9/2021 10:11 PM, Petri Latvala wrote:
> > On Thu, Dec 09, 2021 at 12:54:58PM -0800, Jessica Zhang wrote:
> > > 
> > > 
> > > On 12/9/2021 3:26 AM, Petri Latvala wrote:
> > > > On Wed, Dec 08, 2021 at 04:27:16PM -0800, Jessica Zhang wrote:
> > > > > Catch edge cases where driver doesn't support larger scale factors or
> > > > > pipe doesn't support scaling.
> > > > > 
> > > > > Currently, a 20x20 framebuffer is passed in to be upscaled. However,
> > > > > this will cause issues with other drivers as they may not support larger
> > > > > scale factors or may not support scaling at all for certain planes.
> > > > > 
> > > > > This avoids failures due to invalid scale factor by trying
> > > > > the original 20x20 framebuffer commit, then trying to commit larger
> > > > > framebuffers up to and including unity scale.
> > > > > 
> > > > > Changes since V1:
> > > > > - try_commit_with_fb_size: Changed igt_try_commit2 to
> > > > >     igt_display_try_commit_atomic instead to avoid redundant commits
> > > > > - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
> > > > >     of success condition and moved cleanup_crtc back to outside of method
> > > > > 
> > > > > Tested-on: Qualcomm RB5 (sdm845)
> > > > > 
> > > > > Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
> > > > > ---
> > > > >    tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
> > > > >    1 file changed, 46 insertions(+), 9 deletions(-)
> > > > > 
> > > > > diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> > > > > index 85db11ee..971c1532 100644
> > > > > --- a/tests/kms_plane_scaling.c
> > > > > +++ b/tests/kms_plane_scaling.c
> > > > > @@ -1,5 +1,6 @@
> > > > >    /*
> > > > >     * Copyright © 2013,2014 Intel Corporation
> > > > > + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
> > > > >     *
> > > > >     * Permission is hereby granted, free of charge, to any person obtaining a
> > > > >     * copy of this software and associated documentation files (the "Software"),
> > > > > @@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
> > > > >    	igt_display_commit2(display, COMMIT_ATOMIC);
> > > > >    }
> > > > > +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
> > > > > +		                            igt_display_t *display, data_t *d,
> > > > > +                                   igt_plane_t *plane,
> > > > > +		                            drmModeModeInfo *mode)
> > > > > +{
> > > > > +	int ret;
> > > > > +
> > > > > +	/* Check min to full resolution upscaling */
> > > > > +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
> > > > > +	igt_fb_set_size(&d->fb[0], plane, width, height);
> > > > > +	igt_plane_set_position(plane, 0, 0);
> > > > > +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
> > > > > +	igt_plane_set_rotation(plane, rot);
> > > > > +
> > > > > +	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
> > > > > +		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> > > > > +
> > > > > +	if (!ret)
> > > > > +		igt_display_commit2(display, COMMIT_ATOMIC);
> > > > 
> > > > Now this looks more understandable but I still have one "why"
> > > > remaining: Why test_only the commit if you're anyway going to perform
> > > > the commit? You could just have this as one try_commit, without
> > > > test_only, and let it perform it, as there's nothing done differently
> > > > here based on success/failure.
> > > > 
> > > The original intention was to test that a commit will go through before
> > > actually doing the commit. This way, the test would be more optimized since
> > > we would only perform a commit when we know it will succeed. Otherwise, in a
> > > worst case scenario, we'd be performing 3 or 4 commits per pipe/format for a
> > > subtest like pipe-*-scaler-with-pixel-format.
> > 
> > But the kernel does the same checks for TEST_ONLY as for actually
> > doing the commit. For this kind of optimization assertion I have to
> > ask for some numbers to prove it's saving time enough to be worth of
> > the more complicated code.
> > 
> > Doing a TEST_ONLY commit followed by doing the same commit without
> > TEST_ONLY surely is slower when the commit will succeed at least.
> > 
> 
> Sorry if this wasn't clear in my previous reply -- I'm focusing on
> optimizing for cases where scaling a 20x20 buffer isn't supported and for
> failure cases. For example, if we just call try_commit, we would be doing 3
> commits per format per pipe in cases where the driver only supports unity
> scale. Since TEST_ONLY will only perform a check without performing an
> actual commit [1], wouldn't it be more optimal to only perform a commit if
> the commit will succeed in cases like this?

Check the other functions called from there,
drm_atomic_nonblocking_commit and drm_atomic_commit. They call
drm_atomic_check_only to check if the commit would succeed.

Which is my point: TEST_ONLY flag is for cases where you just want to
verify the validness of a commit without ever (!) executing it. If
you're going to execute it after checking, just try to execute it,
that's faster. It will flow through the same code to check for
failure.


-- 
Petri Latvala

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-14  9:43         ` Petri Latvala
@ 2021-12-15 19:59           ` Jessica Zhang
  0 siblings, 0 replies; 13+ messages in thread
From: Jessica Zhang @ 2021-12-15 19:59 UTC (permalink / raw)
  To: Petri Latvala; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh



On 12/14/2021 1:43 AM, Petri Latvala wrote:
> On Mon, Dec 13, 2021 at 04:50:26PM -0800, Jessica Zhang wrote:
>>
>>
>> On 12/9/2021 10:11 PM, Petri Latvala wrote:
>>> On Thu, Dec 09, 2021 at 12:54:58PM -0800, Jessica Zhang wrote:
>>>>
>>>>
>>>> On 12/9/2021 3:26 AM, Petri Latvala wrote:
>>>>> On Wed, Dec 08, 2021 at 04:27:16PM -0800, Jessica Zhang wrote:
>>>>>> Catch edge cases where driver doesn't support larger scale factors or
>>>>>> pipe doesn't support scaling.
>>>>>>
>>>>>> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
>>>>>> this will cause issues with other drivers as they may not support larger
>>>>>> scale factors or may not support scaling at all for certain planes.
>>>>>>
>>>>>> This avoids failures due to invalid scale factor by trying
>>>>>> the original 20x20 framebuffer commit, then trying to commit larger
>>>>>> framebuffers up to and including unity scale.
>>>>>>
>>>>>> Changes since V1:
>>>>>> - try_commit_with_fb_size: Changed igt_try_commit2 to
>>>>>>      igt_display_try_commit_atomic instead to avoid redundant commits
>>>>>> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>>>>>>      of success condition and moved cleanup_crtc back to outside of method
>>>>>>
>>>>>> Tested-on: Qualcomm RB5 (sdm845)
>>>>>>
>>>>>> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
>>>>>> ---
>>>>>>     tests/kms_plane_scaling.c | 55 ++++++++++++++++++++++++++++++++-------
>>>>>>     1 file changed, 46 insertions(+), 9 deletions(-)
>>>>>>
>>>>>> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
>>>>>> index 85db11ee..971c1532 100644
>>>>>> --- a/tests/kms_plane_scaling.c
>>>>>> +++ b/tests/kms_plane_scaling.c
>>>>>> @@ -1,5 +1,6 @@
>>>>>>     /*
>>>>>>      * Copyright © 2013,2014 Intel Corporation
>>>>>> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
>>>>>>      *
>>>>>>      * Permission is hereby granted, free of charge, to any person obtaining a
>>>>>>      * copy of this software and associated documentation files (the "Software"),
>>>>>> @@ -118,6 +119,32 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
>>>>>>     	igt_display_commit2(display, COMMIT_ATOMIC);
>>>>>>     }
>>>>>> +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
>>>>>> +		                            igt_display_t *display, data_t *d,
>>>>>> +                                   igt_plane_t *plane,
>>>>>> +		                            drmModeModeInfo *mode)
>>>>>> +{
>>>>>> +	int ret;
>>>>>> +
>>>>>> +	/* Check min to full resolution upscaling */
>>>>>> +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
>>>>>> +	igt_fb_set_size(&d->fb[0], plane, width, height);
>>>>>> +	igt_plane_set_position(plane, 0, 0);
>>>>>> +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>>>>>> +	igt_plane_set_rotation(plane, rot);
>>>>>> +
>>>>>> +	ret = igt_display_try_commit_atomic(display, DRM_MODE_ATOMIC_TEST_ONLY |
>>>>>> +		                                DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
>>>>>> +
>>>>>> +	if (!ret)
>>>>>> +		igt_display_commit2(display, COMMIT_ATOMIC);
>>>>>
>>>>> Now this looks more understandable but I still have one "why"
>>>>> remaining: Why test_only the commit if you're anyway going to perform
>>>>> the commit? You could just have this as one try_commit, without
>>>>> test_only, and let it perform it, as there's nothing done differently
>>>>> here based on success/failure.
>>>>>
>>>> The original intention was to test that a commit will go through before
>>>> actually doing the commit. This way, the test would be more optimized since
>>>> we would only perform a commit when we know it will succeed. Otherwise, in a
>>>> worst case scenario, we'd be performing 3 or 4 commits per pipe/format for a
>>>> subtest like pipe-*-scaler-with-pixel-format.
>>>
>>> But the kernel does the same checks for TEST_ONLY as for actually
>>> doing the commit. For this kind of optimization assertion I have to
>>> ask for some numbers to prove it's saving time enough to be worth of
>>> the more complicated code.
>>>
>>> Doing a TEST_ONLY commit followed by doing the same commit without
>>> TEST_ONLY surely is slower when the commit will succeed at least.
>>>
>>
>> Sorry if this wasn't clear in my previous reply -- I'm focusing on
>> optimizing for cases where scaling a 20x20 buffer isn't supported and for
>> failure cases. For example, if we just call try_commit, we would be doing 3
>> commits per format per pipe in cases where the driver only supports unity
>> scale. Since TEST_ONLY will only perform a check without performing an
>> actual commit [1], wouldn't it be more optimal to only perform a commit if
>> the commit will succeed in cases like this?
> 
> Check the other functions called from there,
> drm_atomic_nonblocking_commit and drm_atomic_commit. They call
> drm_atomic_check_only to check if the commit would succeed.
> 
> Which is my point: TEST_ONLY flag is for cases where you just want to
> verify the validness of a commit without ever (!) executing it. If
> you're going to execute it after checking, just try to execute it,
> that's faster. It will flow through the same code to check for
> failure.
> 

Got it -- I see where you're coming from now. Will change the method to 
call try_commit.

Thanks,
Jessica Zhang

> 

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-23 16:20   ` Jessica Zhang
@ 2021-12-23 19:00     ` Jessica Zhang
  0 siblings, 0 replies; 13+ messages in thread
From: Jessica Zhang @ 2021-12-23 19:00 UTC (permalink / raw)
  To: Petri Latvala; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh



On 12/23/2021 8:20 AM, Jessica Zhang wrote:
> 
> 
> On 12/17/2021 4:34 AM, Petri Latvala wrote:
>> On Wed, Dec 15, 2021 at 02:51:18PM -0800, Jessica Zhang wrote:
>>> Catch edge cases where driver doesn't support larger scale factors or
>>> pipe doesn't support scaling.
>>>
>>> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
>>> this will cause issues with other drivers as they may not support larger
>>> scale factors or may not support scaling at all for certain planes.
>>>
>>> This avoids failures due to invalid scale factor by trying
>>> the original 20x20 framebuffer commit, then trying to commit larger
>>> framebuffers up to and including unity scale.
>>>
>>> Changes since V1:
>>> - try_commit_with_fb_size: Changed igt_try_commit2 to
>>>    igt_display_try_commit_atomic instead to avoid redundant commits
>>> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>>>    of success condition and moved cleanup_crtc back to outside of method
>>>
>>> Changes since V2:
>>> - try_commit_with_fb_size: Replaced igt_display_try_commit_atomic with
>>>    igt_display_try_commit2 and removed igt_display_try_commit2 to avoid
>>>    redundant checks
>>>
>>> Tested-on: Qualcomm RB5 (sdm845)
>>>
>>> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
>>> ---
>>>   tests/kms_plane_scaling.c | 51 ++++++++++++++++++++++++++++++++-------
>>>   1 file changed, 42 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
>>> index 85db11ee..55042d40 100644
>>> --- a/tests/kms_plane_scaling.c
>>> +++ b/tests/kms_plane_scaling.c
>>> @@ -1,5 +1,6 @@
>>>   /*
>>>    * Copyright © 2013,2014 Intel Corporation
>>> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights 
>>> reserved.
>>>    *
>>>    * Permission is hereby granted, free of charge, to any person 
>>> obtaining a
>>>    * copy of this software and associated documentation files (the 
>>> "Software"),
>>> @@ -118,6 +119,28 @@ static void prepare_crtc(data_t *data, 
>>> igt_output_t *output, enum pipe pipe,
>>>       igt_display_commit2(display, COMMIT_ATOMIC);
>>>   }
>>> +static int try_commit_with_fb_size(int width, int height, 
>>> igt_rotation_t rot,
>>> +                            igt_display_t *display, data_t *d,
>>> +                                   igt_plane_t *plane,
>>> +                            drmModeModeInfo *mode)
>>> +{
>>> +    int ret;
>>> +
>>> +    /* Check min to full resolution upscaling */
>>> +    igt_fb_set_position(&d->fb[0], plane, 0, 0);
>>> +    igt_fb_set_size(&d->fb[0], plane, width, height);
>>> +    igt_plane_set_position(plane, 0, 0);
>>> +    igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>>> +    igt_plane_set_rotation(plane, rot);
>>> +
>>> +    ret = igt_display_try_commit2(display, COMMIT_ATOMIC);
>>> +
>>> +    igt_plane_set_fb(plane, NULL);
>>> +    igt_plane_set_position(plane, 0, 0);
>>
>> These set_fb and set_position calls should only be done if the commit
>> is successful, maybe?
>>

(Sorry, responded a little too quickly previously)

set_position can be moved out to after a successful commit, but we want 
to keep set_fb inside the method, since we want to clear the fb 
properties before trying a different size.

Thanks,
Jessica Zhang

>>> +
>>> +    return ret;
>>> +}
>>> +
>>>   static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t 
>>> *plane,
>>>                        uint32_t pixel_format,
>>>                        uint64_t modifier, enum pipe pipe,
>>> @@ -126,6 +149,7 @@ static void check_scaling_pipe_plane_rot(data_t 
>>> *d, igt_plane_t *plane,
>>>   {
>>>       igt_display_t *display = &d->display;
>>>       int width, height;
>>> +    int commit_ret;
>>>       drmModeModeInfo *mode;
>>>       cleanup_crtc(d);
>>> @@ -139,16 +163,25 @@ static void check_scaling_pipe_plane_rot(data_t 
>>> *d, igt_plane_t *plane,
>>>                  pixel_format, modifier, 0.0, 1.0, 0.0, &d->fb[0]);
>>>       igt_plane_set_fb(plane, &d->fb[0]);
>>> -    /* Check min to full resolution upscaling */
>>> -    igt_fb_set_position(&d->fb[0], plane, 0, 0);
>>> -    igt_fb_set_size(&d->fb[0], plane, width, height);
>>> -    igt_plane_set_position(plane, 0, 0);
>>> -    igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>>> -    igt_plane_set_rotation(plane, rot);
>>> -    igt_display_commit2(display, COMMIT_ATOMIC);
>>> +    commit_ret = try_commit_with_fb_size(width, height, rot, display,
>>> +                                            d, plane, mode);
>>> -    igt_plane_set_fb(plane, NULL);
>>> -    igt_plane_set_position(plane, 0, 0);
>>> +    if(commit_ret == -ERANGE) {
>>> +        igt_debug("Scaling for %dx%d plane not supported, trying 
>>> scale factor of 4x\n", width, height);
>>> +        width = height = mode->vdisplay / 4;
>>> +        commit_ret = try_commit_with_fb_size(width, height, rot, 
>>> display,
>>> +                                                    d, plane, mode);
>>> +    }
>>> +
>>> +    if (commit_ret == -ERANGE) {
>>> +        igt_debug("Scale factor of 4x (or scaling in general) not 
>>> supported, trying unity scale\n");
>>> +        width = mode->hdisplay;
>>> +        height = mode->vdisplay;
>>> +        commit_ret = try_commit_with_fb_size(width, height, rot, 
>>> display,
>>> +                                                    d, plane, mode);
>>> +    }
>>> +
>>
>> In here, after going through the fallbacks.
>> Yes, makes sense.
> 
> Thanks,
> Jessica Zhang
>>
>> -- 
>> Petri Latvala
>>
>>
>>
>>> +    igt_assert_eq(commit_ret, 0);
>>>   }
>>>   static const igt_rotation_t rotations[] = {
>>> -- 
>>> 2.34.1
>>>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-17 12:34 ` Petri Latvala
@ 2021-12-23 16:20   ` Jessica Zhang
  2021-12-23 19:00     ` Jessica Zhang
  0 siblings, 1 reply; 13+ messages in thread
From: Jessica Zhang @ 2021-12-23 16:20 UTC (permalink / raw)
  To: Petri Latvala; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh



On 12/17/2021 4:34 AM, Petri Latvala wrote:
> On Wed, Dec 15, 2021 at 02:51:18PM -0800, Jessica Zhang wrote:
>> Catch edge cases where driver doesn't support larger scale factors or
>> pipe doesn't support scaling.
>>
>> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
>> this will cause issues with other drivers as they may not support larger
>> scale factors or may not support scaling at all for certain planes.
>>
>> This avoids failures due to invalid scale factor by trying
>> the original 20x20 framebuffer commit, then trying to commit larger
>> framebuffers up to and including unity scale.
>>
>> Changes since V1:
>> - try_commit_with_fb_size: Changed igt_try_commit2 to
>>    igt_display_try_commit_atomic instead to avoid redundant commits
>> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>>    of success condition and moved cleanup_crtc back to outside of method
>>
>> Changes since V2:
>> - try_commit_with_fb_size: Replaced igt_display_try_commit_atomic with
>>    igt_display_try_commit2 and removed igt_display_try_commit2 to avoid
>>    redundant checks
>>
>> Tested-on: Qualcomm RB5 (sdm845)
>>
>> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
>> ---
>>   tests/kms_plane_scaling.c | 51 ++++++++++++++++++++++++++++++++-------
>>   1 file changed, 42 insertions(+), 9 deletions(-)
>>
>> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
>> index 85db11ee..55042d40 100644
>> --- a/tests/kms_plane_scaling.c
>> +++ b/tests/kms_plane_scaling.c
>> @@ -1,5 +1,6 @@
>>   /*
>>    * Copyright © 2013,2014 Intel Corporation
>> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
>>    *
>>    * Permission is hereby granted, free of charge, to any person obtaining a
>>    * copy of this software and associated documentation files (the "Software"),
>> @@ -118,6 +119,28 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
>>   	igt_display_commit2(display, COMMIT_ATOMIC);
>>   }
>>   
>> +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
>> +		                    igt_display_t *display, data_t *d,
>> +                                   igt_plane_t *plane,
>> +		                    drmModeModeInfo *mode)
>> +{
>> +	int ret;
>> +
>> +	/* Check min to full resolution upscaling */
>> +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
>> +	igt_fb_set_size(&d->fb[0], plane, width, height);
>> +	igt_plane_set_position(plane, 0, 0);
>> +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>> +	igt_plane_set_rotation(plane, rot);
>> +
>> +	ret = igt_display_try_commit2(display, COMMIT_ATOMIC);
>> +
>> +	igt_plane_set_fb(plane, NULL);
>> +	igt_plane_set_position(plane, 0, 0);
> 
> These set_fb and set_position calls should only be done if the commit
> is successful, maybe?
> 
>> +
>> +	return ret;
>> +}
>> +
>>   static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>>   					 uint32_t pixel_format,
>>   					 uint64_t modifier, enum pipe pipe,
>> @@ -126,6 +149,7 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>>   {
>>   	igt_display_t *display = &d->display;
>>   	int width, height;
>> +	int commit_ret;
>>   	drmModeModeInfo *mode;
>>   
>>   	cleanup_crtc(d);
>> @@ -139,16 +163,25 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>>   		       pixel_format, modifier, 0.0, 1.0, 0.0, &d->fb[0]);
>>   	igt_plane_set_fb(plane, &d->fb[0]);
>>   
>> -	/* Check min to full resolution upscaling */
>> -	igt_fb_set_position(&d->fb[0], plane, 0, 0);
>> -	igt_fb_set_size(&d->fb[0], plane, width, height);
>> -	igt_plane_set_position(plane, 0, 0);
>> -	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
>> -	igt_plane_set_rotation(plane, rot);
>> -	igt_display_commit2(display, COMMIT_ATOMIC);
>> +	commit_ret = try_commit_with_fb_size(width, height, rot, display,
>> +                                            d, plane, mode);
>>   
>> -	igt_plane_set_fb(plane, NULL);
>> -	igt_plane_set_position(plane, 0, 0);
>> +	if(commit_ret == -ERANGE) {
>> +		igt_debug("Scaling for %dx%d plane not supported, trying scale factor of 4x\n", width, height);
>> +		width = height = mode->vdisplay / 4;
>> +		commit_ret = try_commit_with_fb_size(width, height, rot, display,
>> +                                                    d, plane, mode);
>> +	}
>> +
>> +	if (commit_ret == -ERANGE) {
>> +		igt_debug("Scale factor of 4x (or scaling in general) not supported, trying unity scale\n");
>> +		width = mode->hdisplay;
>> +		height = mode->vdisplay;
>> +		commit_ret = try_commit_with_fb_size(width, height, rot, display,
>> +                                                    d, plane, mode);
>> +	}
>> +
> 
> In here, after going through the fallbacks.
>Yes, makes sense.

Thanks,
Jessica Zhang
> 
> -- 
> Petri Latvala
> 
> 
> 
>> +	igt_assert_eq(commit_ret, 0);
>>   }
>>   
>>   static const igt_rotation_t rotations[] = {
>> -- 
>> 2.34.1
>>

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
  2021-12-15 22:51 [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors Jessica Zhang
@ 2021-12-17 12:34 ` Petri Latvala
  2021-12-23 16:20   ` Jessica Zhang
  0 siblings, 1 reply; 13+ messages in thread
From: Petri Latvala @ 2021-12-17 12:34 UTC (permalink / raw)
  To: Jessica Zhang; +Cc: quic_khsieh, swboyd, igt-dev, nganji, seanpaul, aravindh

On Wed, Dec 15, 2021 at 02:51:18PM -0800, Jessica Zhang wrote:
> Catch edge cases where driver doesn't support larger scale factors or
> pipe doesn't support scaling.
> 
> Currently, a 20x20 framebuffer is passed in to be upscaled. However,
> this will cause issues with other drivers as they may not support larger
> scale factors or may not support scaling at all for certain planes.
> 
> This avoids failures due to invalid scale factor by trying
> the original 20x20 framebuffer commit, then trying to commit larger
> framebuffers up to and including unity scale.
> 
> Changes since V1:
> - try_commit_with_fb_size: Changed igt_try_commit2 to
>   igt_display_try_commit_atomic instead to avoid redundant commits
> - try_commit_with_fb_size: Moved calls to clear framebuffer to outside
>   of success condition and moved cleanup_crtc back to outside of method
> 
> Changes since V2:
> - try_commit_with_fb_size: Replaced igt_display_try_commit_atomic with
>   igt_display_try_commit2 and removed igt_display_try_commit2 to avoid
>   redundant checks
> 
> Tested-on: Qualcomm RB5 (sdm845)
> 
> Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
> ---
>  tests/kms_plane_scaling.c | 51 ++++++++++++++++++++++++++++++++-------
>  1 file changed, 42 insertions(+), 9 deletions(-)
> 
> diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
> index 85db11ee..55042d40 100644
> --- a/tests/kms_plane_scaling.c
> +++ b/tests/kms_plane_scaling.c
> @@ -1,5 +1,6 @@
>  /*
>   * Copyright © 2013,2014 Intel Corporation
> + * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
>   *
>   * Permission is hereby granted, free of charge, to any person obtaining a
>   * copy of this software and associated documentation files (the "Software"),
> @@ -118,6 +119,28 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
>  	igt_display_commit2(display, COMMIT_ATOMIC);
>  }
>  
> +static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
> +		                    igt_display_t *display, data_t *d,
> +                                   igt_plane_t *plane,
> +		                    drmModeModeInfo *mode)
> +{
> +	int ret;
> +
> +	/* Check min to full resolution upscaling */
> +	igt_fb_set_position(&d->fb[0], plane, 0, 0);
> +	igt_fb_set_size(&d->fb[0], plane, width, height);
> +	igt_plane_set_position(plane, 0, 0);
> +	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
> +	igt_plane_set_rotation(plane, rot);
> +
> +	ret = igt_display_try_commit2(display, COMMIT_ATOMIC);
> +
> +	igt_plane_set_fb(plane, NULL);
> +	igt_plane_set_position(plane, 0, 0);

These set_fb and set_position calls should only be done if the commit
is successful, maybe?

> +
> +	return ret;
> +}
> +
>  static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>  					 uint32_t pixel_format,
>  					 uint64_t modifier, enum pipe pipe,
> @@ -126,6 +149,7 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>  {
>  	igt_display_t *display = &d->display;
>  	int width, height;
> +	int commit_ret;
>  	drmModeModeInfo *mode;
>  
>  	cleanup_crtc(d);
> @@ -139,16 +163,25 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
>  		       pixel_format, modifier, 0.0, 1.0, 0.0, &d->fb[0]);
>  	igt_plane_set_fb(plane, &d->fb[0]);
>  
> -	/* Check min to full resolution upscaling */
> -	igt_fb_set_position(&d->fb[0], plane, 0, 0);
> -	igt_fb_set_size(&d->fb[0], plane, width, height);
> -	igt_plane_set_position(plane, 0, 0);
> -	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
> -	igt_plane_set_rotation(plane, rot);
> -	igt_display_commit2(display, COMMIT_ATOMIC);
> +	commit_ret = try_commit_with_fb_size(width, height, rot, display,
> +                                            d, plane, mode);
>  
> -	igt_plane_set_fb(plane, NULL);
> -	igt_plane_set_position(plane, 0, 0);
> +	if(commit_ret == -ERANGE) {
> +		igt_debug("Scaling for %dx%d plane not supported, trying scale factor of 4x\n", width, height);
> +		width = height = mode->vdisplay / 4;
> +		commit_ret = try_commit_with_fb_size(width, height, rot, display,
> +                                                    d, plane, mode);
> +	}
> +
> +	if (commit_ret == -ERANGE) {
> +		igt_debug("Scale factor of 4x (or scaling in general) not supported, trying unity scale\n");
> +		width = mode->hdisplay;
> +		height = mode->vdisplay;
> +		commit_ret = try_commit_with_fb_size(width, height, rot, display,
> +                                                    d, plane, mode);
> +	}
> +

In here, after going through the fallbacks.


-- 
Petri Latvala



> +	igt_assert_eq(commit_ret, 0);
>  }
>  
>  static const igt_rotation_t rotations[] = {
> -- 
> 2.34.1
> 

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors
@ 2021-12-15 22:51 Jessica Zhang
  2021-12-17 12:34 ` Petri Latvala
  0 siblings, 1 reply; 13+ messages in thread
From: Jessica Zhang @ 2021-12-15 22:51 UTC (permalink / raw)
  To: igt-dev; +Cc: petri.latvala, quic_khsieh, swboyd, nganji, seanpaul, aravindh

Catch edge cases where driver doesn't support larger scale factors or
pipe doesn't support scaling.

Currently, a 20x20 framebuffer is passed in to be upscaled. However,
this will cause issues with other drivers as they may not support larger
scale factors or may not support scaling at all for certain planes.

This avoids failures due to invalid scale factor by trying
the original 20x20 framebuffer commit, then trying to commit larger
framebuffers up to and including unity scale.

Changes since V1:
- try_commit_with_fb_size: Changed igt_try_commit2 to
  igt_display_try_commit_atomic instead to avoid redundant commits
- try_commit_with_fb_size: Moved calls to clear framebuffer to outside
  of success condition and moved cleanup_crtc back to outside of method

Changes since V2:
- try_commit_with_fb_size: Replaced igt_display_try_commit_atomic with
  igt_display_try_commit2 and removed igt_display_try_commit2 to avoid
  redundant checks

Tested-on: Qualcomm RB5 (sdm845)

Signed-off-by: Jessica Zhang <quic_jesszhan@quicinc.com>
---
 tests/kms_plane_scaling.c | 51 ++++++++++++++++++++++++++++++++-------
 1 file changed, 42 insertions(+), 9 deletions(-)

diff --git a/tests/kms_plane_scaling.c b/tests/kms_plane_scaling.c
index 85db11ee..55042d40 100644
--- a/tests/kms_plane_scaling.c
+++ b/tests/kms_plane_scaling.c
@@ -1,5 +1,6 @@
 /*
  * Copyright © 2013,2014 Intel Corporation
+ * Copyright (c) 2021 Qualcomm Innovation Center, Inc. All rights reserved.
  *
  * Permission is hereby granted, free of charge, to any person obtaining a
  * copy of this software and associated documentation files (the "Software"),
@@ -118,6 +119,28 @@ static void prepare_crtc(data_t *data, igt_output_t *output, enum pipe pipe,
 	igt_display_commit2(display, COMMIT_ATOMIC);
 }
 
+static int try_commit_with_fb_size(int width, int height, igt_rotation_t rot,
+		                    igt_display_t *display, data_t *d,
+                                   igt_plane_t *plane,
+		                    drmModeModeInfo *mode)
+{
+	int ret;
+
+	/* Check min to full resolution upscaling */
+	igt_fb_set_position(&d->fb[0], plane, 0, 0);
+	igt_fb_set_size(&d->fb[0], plane, width, height);
+	igt_plane_set_position(plane, 0, 0);
+	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
+	igt_plane_set_rotation(plane, rot);
+
+	ret = igt_display_try_commit2(display, COMMIT_ATOMIC);
+
+	igt_plane_set_fb(plane, NULL);
+	igt_plane_set_position(plane, 0, 0);
+
+	return ret;
+}
+
 static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
 					 uint32_t pixel_format,
 					 uint64_t modifier, enum pipe pipe,
@@ -126,6 +149,7 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
 {
 	igt_display_t *display = &d->display;
 	int width, height;
+	int commit_ret;
 	drmModeModeInfo *mode;
 
 	cleanup_crtc(d);
@@ -139,16 +163,25 @@ static void check_scaling_pipe_plane_rot(data_t *d, igt_plane_t *plane,
 		       pixel_format, modifier, 0.0, 1.0, 0.0, &d->fb[0]);
 	igt_plane_set_fb(plane, &d->fb[0]);
 
-	/* Check min to full resolution upscaling */
-	igt_fb_set_position(&d->fb[0], plane, 0, 0);
-	igt_fb_set_size(&d->fb[0], plane, width, height);
-	igt_plane_set_position(plane, 0, 0);
-	igt_plane_set_size(plane, mode->hdisplay, mode->vdisplay);
-	igt_plane_set_rotation(plane, rot);
-	igt_display_commit2(display, COMMIT_ATOMIC);
+	commit_ret = try_commit_with_fb_size(width, height, rot, display,
+                                            d, plane, mode);
 
-	igt_plane_set_fb(plane, NULL);
-	igt_plane_set_position(plane, 0, 0);
+	if(commit_ret == -ERANGE) {
+		igt_debug("Scaling for %dx%d plane not supported, trying scale factor of 4x\n", width, height);
+		width = height = mode->vdisplay / 4;
+		commit_ret = try_commit_with_fb_size(width, height, rot, display,
+                                                    d, plane, mode);
+	}
+
+	if (commit_ret == -ERANGE) {
+		igt_debug("Scale factor of 4x (or scaling in general) not supported, trying unity scale\n");
+		width = mode->hdisplay;
+		height = mode->vdisplay;
+		commit_ret = try_commit_with_fb_size(width, height, rot, display,
+                                                    d, plane, mode);
+	}
+
+	igt_assert_eq(commit_ret, 0);
 }
 
 static const igt_rotation_t rotations[] = {
-- 
2.34.1

^ permalink raw reply related	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2021-12-23 19:00 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-09  0:27 [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors Jessica Zhang
2021-12-09 11:26 ` Petri Latvala
2021-12-09 20:54   ` Jessica Zhang
2021-12-10  6:11     ` Petri Latvala
2021-12-14  0:50       ` Jessica Zhang
2021-12-14  9:43         ` Petri Latvala
2021-12-15 19:59           ` Jessica Zhang
2021-12-09 19:28 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors (rev2) Patchwork
2021-12-10  4:02 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-12-15 22:51 [igt-dev] [PATCH i-g-t v2] tests/kms_plane_scaling: Increase buffer size if driver doesn't support larger scale factors Jessica Zhang
2021-12-17 12:34 ` Petri Latvala
2021-12-23 16:20   ` Jessica Zhang
2021-12-23 19:00     ` Jessica Zhang

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.