From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Jakub Kolakowski <jakub1.kolakowski@intel.com>,
<igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/2] tests/kms_cursor_edge_walk: check for display and pipe CRC before cursor size
Date: Tue, 8 Apr 2025 11:12:36 +0530 [thread overview]
Message-ID: <80b003e8-afa6-4a8e-9fd4-7f97fcc071f3@intel.com> (raw)
In-Reply-To: <20250407144504.2907700-3-jakub1.kolakowski@intel.com>
Hi Jakub,
Patch LGTM.
Please add "Closes" tag for the gitlab issue.
On 07-04-2025 08:15 pm, Jakub Kolakowski wrote:
> Currently igt_require_pipe_crc(), igt_display_require() and
> igt_display_require_output() is called after trying to get cursor
> width and height which leads to fails on configurations that do
> not have display enabled.
> Move igt_require_pipe_crc(), igt_display_require() and
> igt_display_require_output() before getting cursor width and
> height so instead test will skip on configurations without
> display.
>
> Signed-off-by: Jakub Kolakowski <jakub1.kolakowski@intel.com>
> ---
> tests/kms_cursor_edge_walk.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/kms_cursor_edge_walk.c b/tests/kms_cursor_edge_walk.c
> index 858d1da9b..27bee4482 100644
> --- a/tests/kms_cursor_edge_walk.c
> +++ b/tests/kms_cursor_edge_walk.c
> @@ -361,6 +361,11 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>
> data.drm_fd = drm_open_driver_master(DRIVER_ANY);
>
> + igt_require_pipe_crc(data.drm_fd);
> +
> + igt_display_require(&data.display, data.drm_fd);
> + igt_display_require_output(&data.display);
> +
> if (is_intel_device(data.drm_fd))
> data.devid = intel_get_drm_devid(data.drm_fd);
>
> @@ -372,11 +377,6 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>
> kmstest_set_vt_graphics_mode();
>
> - igt_require_pipe_crc(data.drm_fd);
> -
> - igt_display_require(&data.display, data.drm_fd);
> - igt_display_require_output(&data.display);
> -
> /* Get active pipes. */
> last_pipe = 0;
> for_each_pipe(&data.display, pipe)
next prev parent reply other threads:[~2025-04-08 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 14:45 [PATCH i-g-t 0/2] check for display before cursor size Jakub Kolakowski
2025-04-07 14:45 ` [PATCH i-g-t 1/2] tests/kms_plane_cursor: " Jakub Kolakowski
2025-04-08 5:42 ` Sharma, Swati2
2025-04-08 11:40 ` Sharma, Swati2
2025-04-07 14:45 ` [PATCH i-g-t 2/2] tests/kms_cursor_edge_walk: check for display and pipe CRC " Jakub Kolakowski
2025-04-08 5:42 ` Sharma, Swati2 [this message]
2025-04-08 11:40 ` Sharma, Swati2
2025-04-07 19:01 ` ✓ Xe.CI.BAT: success for check for display " Patchwork
2025-04-07 19:15 ` ✗ i915.CI.BAT: failure " Patchwork
2025-04-11 18:16 ` Kolakowski, Jakub1
2025-04-08 4:40 ` ✗ Xe.CI.Full: " Patchwork
2025-04-11 18:14 ` Kolakowski, Jakub1
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=80b003e8-afa6-4a8e-9fd4-7f97fcc071f3@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox