From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: juha-pekka.heikkila@intel.com, suresh.kumar.kurmi@intel.com
Subject: Re: [igt-dev] [i-g-t, v3] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test
Date: Mon, 23 Jan 2023 21:34:40 +0530 [thread overview]
Message-ID: <1d4508e3-a5ed-e748-7d1c-da5d481e1229@intel.com> (raw)
In-Reply-To: <20230123153050.113763-1-dnyaneshwar.bhadane@intel.com>
On Mon-23-01-2023 09:00 pm, Dnyaneshwar Bhadane wrote:
> Only the valid pipe connector combination reach to the igt commit.
> Cursor max-size test will not affect existing flow as only skip
> for invalid connector.
> For cursor-dpms and cursor-suspend not require to check require_cursor_size
> becuase the cursor height and width used from drm capablities.
>
> --v3
> - Added for_each_pipe_valid_connector() to check for valid connection.
> - initialize pipe with default 0/PIPE_A suggestion from Petri.
>
> Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
>
> ---
> lib/igt_kms.h | 15 +++++++++++++++
> tests/kms_cursor_crc.c | 18 ++++--------------
> 2 files changed, 19 insertions(+), 14 deletions(-)
>
> diff --git a/lib/igt_kms.h b/lib/igt_kms.h
> index be5482e0..5daa751a 100644
> --- a/lib/igt_kms.h
> +++ b/lib/igt_kms.h
> @@ -534,6 +534,21 @@ static inline bool igt_output_is_connected(igt_output_t *output)
>
> return false;
> }
> +/**
> + * for_each_pipe_valid_connector:
> + * @display: a pointer to an #igt_display_t structure
> + * @pipe: from pipe to iterate.
> + * @output: #igt_output_t to check.
> + *
> + * It loop over the all the pipe and check for the given
> + * @output/@pipe can be used together.
> + *
> + */
> +#define for_each_pipe_valid_connector(display, pipe, output) \
> + for_each_pipe_static(pipe) \
> + for_each_if ((((display)->pipes[(pipe)].enabled) && \
> + igt_pipe_connector_valid((pipe), (output))))
> +
>
> /**
> * igt_pipe_connector_valid:
> diff --git a/tests/kms_cursor_crc.c b/tests/kms_cursor_crc.c
> index d5a4b30b..0394768b 100644
> --- a/tests/kms_cursor_crc.c
> +++ b/tests/kms_cursor_crc.c
> @@ -749,7 +749,7 @@ static void run_size_tests(data_t *data, int w, int h)
> }
> }
>
> - for_each_pipe(&data->display, pipe) {
> + for_each_pipe_valid_connector(&data->display, pipe, data->output) {
> data->pipe = pipe;
>
> if (require_cursor_size(data, w, h)) {
> @@ -772,7 +772,7 @@ static void run_tests_on_pipe(data_t *data)
> {
> enum pipe pipe;
> int cursor_size;
> -
> + pipe = PIPE_A;
This looks ugly to me.
> igt_fixture {
> data->output = igt_get_single_output_for_pipe(&data->display, pipe);
Probably, this might be the bug in existing code. Perhaps, you can drop
data->output from igt_fixture and update each subtest to check for the
valid output. Please check my engg patch for BJ [1].
s/for_each_pipe/for_each_pipe_with_single_output/
[1]: https://patchwork.freedesktop.org/patch/519058/
- Bhanu
> igt_require(data->output);
> @@ -850,15 +850,10 @@ static void run_tests_on_pipe(data_t *data)
>
> igt_describe("Check random placement of a cursor with DPMS.");
> igt_subtest_with_dynamic("cursor-dpms") {
> - for_each_pipe(&data->display, pipe) {
> + for_each_pipe_valid_connector(&data->display, pipe, data->output) {
> data->pipe = pipe;
> data->flags = TEST_DPMS;
>
> - if (require_cursor_size(data, data->cursor_max_w, data->cursor_max_h)) {
> - igt_debug("Cursor size %dx%d not supported by driver\n",
> - data->cursor_max_w, data->cursor_max_h);
> - continue;
> - }
>
> igt_dynamic_f("pipe-%s-%s",
> kmstest_pipe_name(pipe),
> @@ -871,15 +866,10 @@ static void run_tests_on_pipe(data_t *data)
>
> igt_describe("Check random placement of a cursor with suspend.");
> igt_subtest_with_dynamic("cursor-suspend") {
> - for_each_pipe(&data->display, pipe) {
> + for_each_pipe_valid_connector(&data->display, pipe, data->output) {
> data->pipe = pipe;
> data->flags = TEST_SUSPEND;
>
> - if (require_cursor_size(data, data->cursor_max_w, data->cursor_max_h)) {
> - igt_debug("Cursor size %dx%d not supported by driver\n",
> - data->cursor_max_w, data->cursor_max_h);
> - continue;
> - }
>
> igt_dynamic_f("pipe-%s-%s",
> kmstest_pipe_name(pipe),
next prev parent reply other threads:[~2023-01-23 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 10:57 [igt-dev] [i-g-t] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test Dnyaneshwar Bhadane
2023-01-12 12:36 ` Ville Syrjälä
2023-01-16 6:42 ` Bhadane, Dnyaneshwar
2023-01-16 10:14 ` Modem, Bhanuprakash
2023-01-12 15:06 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-12 21:39 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-01-16 14:32 ` [igt-dev] [PATCH] [i-g-t, v2] " Dnyaneshwar Bhadane
2023-01-16 14:42 ` Petri Latvala
2023-01-23 9:58 ` Bhadane, Dnyaneshwar
2023-01-23 10:15 ` Petri Latvala
2023-01-23 10:39 ` Bhadane, Dnyaneshwar
2023-01-16 15:06 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev2) Patchwork
2023-01-23 15:30 ` [igt-dev] [i-g-t, v3] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test Dnyaneshwar Bhadane
2023-01-23 16:04 ` Modem, Bhanuprakash [this message]
2023-01-23 17:12 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev3) Patchwork
2023-01-24 3:56 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-24 13:03 ` [igt-dev] [i-g-t, v4] tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test Dnyaneshwar Bhadane
2023-01-24 13:39 ` Modem, Bhanuprakash
2023-01-24 15:33 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev4) Patchwork
2023-01-25 10:49 ` [igt-dev] [i-g-t, v5] tests/kms_cursor_crc: s/for_each_pipe/for_each_pipe_with_single_output/ Dnyaneshwar Bhadane
2023-01-25 16:44 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_cursor_crc: skip pipe on invalid connector in cursor size test (rev5) Patchwork
2023-01-26 1:52 ` [igt-dev] ✓ Fi.CI.IGT: " 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=1d4508e3-a5ed-e748-7d1c-da5d481e1229@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=suresh.kumar.kurmi@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