From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/intel/kms_pm_dc: Ensure eDP detection before skipping test
Date: Fri, 7 Feb 2025 20:25:42 +0530 [thread overview]
Message-ID: <ed3f14eb-0d24-43c6-ad11-ea957b4dc0a4@intel.com> (raw)
In-Reply-To: <20250206155947.973010-1-jeevan.b@intel.com>
Hi Jeevan,
On 06-02-2025 09:29 pm, Jeevan B wrote:
> Ensure all outputs are checked before skipping the test, preventing
> premature exits when an eDP is available later.
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/intel/kms_pm_dc.c | 39 ++++++++++++++++++++++++---------------
> 1 file changed, 24 insertions(+), 15 deletions(-)
>
> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
> index 9551cc6b9..aaf057b68 100644
> --- a/tests/intel/kms_pm_dc.c
> +++ b/tests/intel/kms_pm_dc.c
> @@ -640,30 +640,39 @@ static void test_deep_pkgc_state(data_t *data)
> time_t delay;
> enum pipe pipe;
> bool pkgc_flag = false;
> - bool flip = true;
> + bool flip = true, edp_found = false;
>
> igt_display_t *display = &data->display;
> igt_plane_t *primary;
> igt_output_t *output = NULL;
>
> for_each_pipe_with_valid_output(display, pipe, output) {
> - if (output->config.connector->connector_type != DRM_MODE_CONNECTOR_eDP)
> - igt_skip("No eDP output found, skipping the test.\n");
> - /* Check VRR capabilities before setting up */
> - if (igt_output_has_prop(output, IGT_CONNECTOR_VRR_CAPABLE) &&
> - igt_output_get_prop(output, IGT_CONNECTOR_VRR_CAPABLE)) {
> - /*
> - * TODO: Add check for vmin = vmax = flipline if VRR enabled
> - * when KMD allows for such capability.
> - */
> - igt_pipe_set_prop_value(display, pipe,
> - IGT_CRTC_VRR_ENABLED, false);
> - igt_assert(igt_display_try_commit_atomic(display,
> - DRM_MODE_ATOMIC_ALLOW_MODESET,
> - NULL) == 0);
> + if (output->config.connector->connector_type == DRM_MODE_CONNECTOR_eDP) {
> + edp_found = true;
> break;
> }
> }
> +
> + igt_require_f(edp_found, "No eDP output found, skipping the test.\n");
> +
> + for_each_pipe_with_valid_output(display, pipe, output) {
Why do we need to loop through valid_outputs again? Lets store valid
outputs (eDP) in an array and loop only through that.
> + if (output->config.connector->connector_type == DRM_MODE_CONNECTOR_eDP) {
> + /* Check VRR capabilities before setting up */
> + if (igt_output_has_prop(output, IGT_CONNECTOR_VRR_CAPABLE) &&
> + igt_output_get_prop(output, IGT_CONNECTOR_VRR_CAPABLE)) {
> + /*
> + * TODO: Add check for vmin = vmax = flipline if VRR enabled
> + * when KMD allows for such capability.
> + */
> + igt_pipe_set_prop_value(display, pipe,
> + IGT_CRTC_VRR_ENABLED, false);
> + igt_assert(igt_display_try_commit_atomic(display,
> + DRM_MODE_ATOMIC_ALLOW_MODESET,
> + NULL) == 0);
> + break;
> + }
> + }
> + }
> igt_display_reset(display);
>
> igt_output_set_pipe(output, pipe);
next prev parent reply other threads:[~2025-02-07 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 15:59 [PATCH i-g-t] tests/intel/kms_pm_dc: Ensure eDP detection before skipping test Jeevan B
2025-02-06 21:27 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-02-07 2:47 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-07 4:35 ` [PATCH i-g-t] " Samala, Pranay
2025-02-07 5:03 ` B, Jeevan
2025-02-07 14:54 ` ✓ i915.CI.BAT: success for " Patchwork
2025-02-07 14:55 ` Sharma, Swati2 [this message]
2025-02-07 15:27 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-07 23:14 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-08 0:06 ` ✗ Xe.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-02-10 10:36 [PATCH i-g-t] " Jeevan B
2025-02-18 10:12 ` Sharma, Swati2
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=ed3f14eb-0d24-43c6-ad11-ea957b4dc0a4@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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