From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "juhapekka.heikkila@gmail.com" <juhapekka.heikkila@gmail.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane: add invalid pixel format tests
Date: Tue, 7 Mar 2023 09:48:43 +0000 [thread overview]
Message-ID: <fc46b9775fd7fa5bfab6dac60a2f1d2a265d5885.camel@intel.com> (raw)
In-Reply-To: <20230227113407.20192-1-juhapekka.heikkila@gmail.com>
HI JP
On Mon, 2023-02-27 at 13:34 +0200, Juha-Pekka Heikkila wrote:
> Test settings for pixel formats which are not supposing to be accepted.
>
> Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
> tests/kms_plane.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
>
> diff --git a/tests/kms_plane.c b/tests/kms_plane.c
> index 164dacf40..631531284 100644
> --- a/tests/kms_plane.c
> +++ b/tests/kms_plane.c
> @@ -1125,6 +1125,54 @@ test_pixel_formats(data_t *data, enum pipe pipe)
> igt_assert_f(result, "At least one CRC mismatch happened\n");
> }
>
> +static void test_invalid_settings(data_t *data)
> +{
> + enum pipe pipe = PIPE_A;
> + igt_output_t *output;
> + igt_fb_t fb;
> + igt_plane_t *primary;
> + int rval;
> +
> + /*
> + * If here is added non-intel tests below require will need to be
> + * changed to if(..)
> + */
> + igt_require_intel(data->drm_fd);
> + igt_require(intel_display_ver(intel_get_drm_devid(data->drm_fd)) >= 9);
> +
> + output = igt_get_single_output_for_pipe(&data->display, pipe);
> + igt_require(output);
> +
> + igt_output_set_pipe(output, pipe);
> + primary = igt_output_get_plane_type(output, DRM_PLANE_TYPE_PRIMARY);
> +
> + igt_display_commit2(&data->display, data->display.is_atomic ? COMMIT_ATOMIC :
> COMMIT_LEGACY);
> +
> + /* test against intel_plane_check_src_coordinates() in i915 */
> + if (igt_plane_has_format_mod(primary, DRM_FORMAT_NV12,
> + DRM_FORMAT_MOD_LINEAR)) {
> + igt_create_fb(data->drm_fd, 257, 256,
> + DRM_FORMAT_NV12, DRM_FORMAT_MOD_LINEAR, &fb);
> + igt_plane_set_fb(primary, &fb);
> + rval = igt_display_try_commit_atomic(&data->display, 0, NULL);
> + igt_remove_fb(data->drm_fd, &fb);
> + igt_assert_f(rval == -EINVAL, "Odd width NV12 framebuffer\n");
> + } else
> + igt_debug("Odd width NV12 framebuffer test skipped\n");
You may need the braces in the else branch
> +
> + /* test against intel_plane_check_src_coordinates() in i915 */
> + if (igt_plane_has_format_mod(primary, DRM_FORMAT_NV12,
> + DRM_FORMAT_MOD_LINEAR)) {
> + igt_create_fb(data->drm_fd, 256, 257,
> + DRM_FORMAT_NV12, DRM_FORMAT_MOD_LINEAR, &fb);
> + igt_plane_set_fb(primary, &fb);
> + rval = igt_display_try_commit_atomic(&data->display, 0, NULL);
> + igt_remove_fb(data->drm_fd, &fb);
> + igt_assert_f(rval == -EINVAL, "Odd height NV12 framebuffer\n");
> + } else
> + igt_debug("Odd height NV12 framebuffer test skipped\n");
You may need the braces in the else branch here as well
With that,
Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> +}
> +
> static bool is_pipe_limit_reached(int count) {
> return count >= CRTC_RESTRICT_CNT && !all_pipes;
> }
> @@ -1194,6 +1242,10 @@ run_tests_for_pipe_plane(data_t *data)
> data->flags = TEST_PANNING_BOTTOM_RIGHT | TEST_SUSPEND_RESUME;
> run_test(data, test_plane_panning);
> }
> +
> + igt_describe("verify invalid settings for pixel format are not accepted");
> + igt_subtest_f("invalid-pixel-format-settings")
> + test_invalid_settings(data);
> }
>
> static int opt_handler(int opt, int opt_index, void *_data)
prev parent reply other threads:[~2023-03-07 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:34 [igt-dev] [PATCH i-g-t] tests/kms_plane: add invalid pixel format tests Juha-Pekka Heikkila
2023-02-27 13:29 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-02-27 17:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-02-27 22:30 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane: add invalid pixel format tests (rev2) Patchwork
2023-02-28 3:58 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-02-28 5:58 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane: add invalid pixel format tests (rev3) Patchwork
2023-02-28 9:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-03-01 12:04 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_plane: add invalid pixel format tests (rev4) Patchwork
2023-03-01 13:53 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-03-07 9:48 ` Govindapillai, Vinod [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc46b9775fd7fa5bfab6dac60a2f1d2a265d5885.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--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