public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>,
	 igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/2] tests/kms_plane: Add test_nv12_tile4_src_y planar settings test
Date: Tue, 05 May 2026 10:27:30 +0300	[thread overview]
Message-ID: <2fc6fddd76c5cd00fdb3f8cd6ab7def75a93b008.camel@coelho.fi> (raw)
In-Reply-To: <20260424171123.3963793-3-juhapekka.heikkila@gmail.com>

On Fri, 2026-04-24 at 20:11 +0300, Juha-Pekka Heikkila wrote:
> Add Intel specific dynamic subtest test_nv12_tile4_src_y under
> planar-pixel-format-settings test. This test target dpt
> misconfiguration with specially crafted nv12 framebuffer
> with tile4.
> 
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---

Generally the test seems reasonable, but a bit more explanation on what
it is actually testing would be nice.  The commit message doesn't
really mention the actual problem that it is trying to test.


>  tests/kms_plane.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 95 insertions(+)
> 
> diff --git a/tests/kms_plane.c b/tests/kms_plane.c
> index 6c08f1de8..303bd333f 100644
> --- a/tests/kms_plane.c
> +++ b/tests/kms_plane.c
> @@ -61,6 +61,12 @@
>   *              matches a reference XRGB8888 blue fill on Intel hardware.
>   * Driver requirement: i915, xe
>   *
> + * SUBTEST: planar-pixel-format-settings@nv12-tile4-src-y
> + * Description: Verify that an NV12 Tile4 framebuffer with src_y=1 renders
> + *              correctly on Intel hardware.  CRC comparison detects
> + *              corruption.
> + * Driver requirement: xe
> + *

Also the description here seems a bit more complete, IMHO.


>   * SUBTEST: plane-position-%s
>   * Description: Verify plane position using two planes to create a %arg[1]
>   *
> @@ -1534,6 +1540,92 @@ test_p016_odd_vertical_pan(data_t *data, igt_crtc_t *crtc,
>  		     rval, expected_rval);
>  }
>  
> +/*
> + * test_nv12_tile4_src_y - NV12 Tile4 with src_y=1 CRC correctness check.
> + *
> + * If kernel program wrong UV DPT va, hardware read chroma from
> + * an unmapped page, producing incorrect picture and crc mismatch
> + */
> +static void
> +test_nv12_tile4_src_y(data_t *data, igt_crtc_t *crtc, igt_output_t *output)
> +{
> +	igt_plane_t *primary;
> +	struct igt_fb nv12_fb, ref_fb;
> +	igt_crc_t crc, crc_ref;
> +	drmModeModeInfo *mode;
> +
> +	/* required size for this test, do not change! */
> +	const int fb_w = 1280, fb_h = 768;
> +	int ret;
> +
> +	igt_require_xe(data->drm_fd);
> +	igt_display_reset(&data->display);
> +	igt_output_set_crtc(output, crtc);
> +
> +	primary = igt_output_get_plane_type(output, DRM_PLANE_TYPE_PRIMARY);
> +	mode    = igt_output_get_mode(output);
> +
> +	igt_require_f(igt_plane_has_format_mod(primary, DRM_FORMAT_NV12,
> +					       I915_FORMAT_MOD_4_TILED),
> +		      "Primary plane does not support NV12 + Tile4\n");
> +
> +	igt_require_f(fb_w <= mode->hdisplay && fb_h <= mode->vdisplay,
> +		      "Mode %dx%d too small for %dx%d NV12 test FB\n",
> +		      mode->hdisplay, mode->vdisplay, fb_w, fb_h);
> +
> +	igt_create_color_fb(data->drm_fd, fb_w, fb_h,
> +			    DRM_FORMAT_NV12, I915_FORMAT_MOD_4_TILED,
> +			    0.0, 0.0, 1.0, &nv12_fb);
> +
> +	/*
> +	 * src_y = 1 - this is trigger for dpt uv offset bug
> +	 */
> +	igt_plane_set_fb(primary, &nv12_fb);
> +	igt_fb_set_position(&nv12_fb, primary, 0, 1);
> +	igt_fb_set_size(&nv12_fb, primary, fb_w, fb_h - 1);
> +	igt_plane_set_position(primary, 0, 0);
> +	igt_plane_set_size(primary, fb_w, fb_h - 1);
> +
> +	ret = igt_display_try_commit_atomic(&data->display,
> +					    DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> +	if (ret != 0) {
> +		igt_plane_set_fb(primary, NULL);
> +		igt_remove_fb(data->drm_fd, &nv12_fb);
> +		igt_skip("NV12 Tile4 src_y=1 rejected by kernel (ret=%d)\n", ret);
> +	}
> +
> +	data->pipe_crc = igt_crtc_crc_new(crtc, IGT_PIPE_CRC_SOURCE_AUTO);
> +	set_legacy_lut(data, crtc, LUT_MASK);
> +	igt_pipe_crc_collect_crc(data->pipe_crc, &crc);
> +
> +	/*
> +	 * Get reference crc to check above went ok
> +	 */
> +	igt_create_color_fb(data->drm_fd, fb_w, fb_h - 1,
> +			    DRM_FORMAT_XRGB8888, DRM_FORMAT_MOD_LINEAR,
> +			    0.0, 0.0, 1.0, &ref_fb);
> +	igt_plane_set_fb(primary, &ref_fb);
> +	igt_fb_set_position(&ref_fb, primary, 0, 0);
> +	igt_fb_set_size(&ref_fb, primary, fb_w, fb_h - 1);
> +	igt_plane_set_position(primary, 0, 0);
> +	igt_plane_set_size(primary, fb_w, fb_h - 1);
> +	igt_display_commit_atomic(&data->display,
> +				  DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);

Nitpick: maybe it's because I'm not the most familiar person regarding
this, but it would be nice if both setups (this one immediately above
and the one with src_y = 1 earlier) would visually match each other, so
it would be easier to see what is actually different between them. 
Maybe this would even deserve a helper function so it's very clear what
the difference is between the two?


> +
> +	igt_pipe_crc_collect_crc(data->pipe_crc, &crc_ref);
> +	set_legacy_lut(data, crtc, 0xffff);
> +	igt_pipe_crc_free(data->pipe_crc);
> +	data->pipe_crc = NULL;
> +
> +	igt_plane_set_fb(primary, NULL);
> +	igt_display_commit_atomic(&data->display,
> +				  DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> +	igt_remove_fb(data->drm_fd, &nv12_fb);
> +	igt_remove_fb(data->drm_fd, &ref_fb);
> +
> +	igt_assert_crc_equal(&crc_ref, &crc);
> +}
> +
>  static void test_planar_settings(data_t *data)
>  {
>  	igt_display_t *display = &data->display;
> @@ -1562,6 +1654,9 @@ static void test_planar_settings(data_t *data)
>  
>  	igt_dynamic("p016-odd-vertical-pan")
>  		test_p016_odd_vertical_pan(data, crtc, output, display_ver);
> +
> +	igt_dynamic("nv12-tile4-src-y")
> +		test_nv12_tile4_src_y(data, crtc, output);
>  }
>  
>  static bool is_pipe_limit_reached(int count)


--
Cheers,
Luca.

  reply	other threads:[~2026-05-05  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 17:11 [PATCH i-g-t 0/2] kms_plane planar-pixel-format-settings restructure Juha-Pekka Heikkila
2026-04-24 17:11 ` [PATCH i-g-t 1/2] tests/kms_plane: Restructure planar-pixel-format-settings test and make it Intel only Juha-Pekka Heikkila
2026-04-27 12:28   ` Ville Syrjälä
2026-04-27 16:05     ` Juha-Pekka Heikkilä
2026-04-24 17:11 ` [PATCH i-g-t 2/2] tests/kms_plane: Add test_nv12_tile4_src_y planar settings test Juha-Pekka Heikkila
2026-05-05  7:27   ` Luca Coelho [this message]
2026-05-06 17:56     ` Juha-Pekka Heikkilä
2026-04-24 18:55 ` [PATCH i-g-t 0/2] kms_plane planar-pixel-format-settings restructure Srinivas, Vidya
2026-04-24 19:55 ` ✓ i915.CI.BAT: success for " Patchwork
2026-04-24 20:05 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-24 21:14 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-25  1:31 ` ✗ i915.CI.Full: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2fc6fddd76c5cd00fdb3f8cd6ab7def75a93b008.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox