public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@amd.com>
To: Jani Nikula <jani.nikula@intel.com>, igt-dev@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com,
	Aurabindo Pillai <aurabindo.pillai@amd.com>,
	Harry Wentland <harry.wentland@amd.com>,
	Vitaly Prosyak <vitaly.prosyak@amd.com>
Subject: Re: [PATCH i-g-t v3 1/5] tests/amdgpu/amd_multidisplay_modeset: Prepare for returning NULL from igt_crtc_for_pipe()
Date: Thu, 26 Mar 2026 18:49:32 -0600	[thread overview]
Message-ID: <29138133-adad-4586-a2e0-30772cb915e0@amd.com> (raw)
In-Reply-To: <42c82fdc808ed80c3b3eebc8e2d324bf06c4cb87.1774529527.git.jani.nikula@intel.com>

Reviewed-by: Alex Hung <alex.hung@amd.com>

On 3/26/26 06:53, Jani Nikula wrote:
> AMD should always have enough CRTCs for the test. Assert this is the
> case by checking the CRTC returned from igt_crtc_for_pipe() is valid.
> 
> This prepares for returning NULL for invalid pipes from
> igt_crtc_for_pipe() by ensuring the test logic is sound. The follow-up
> can change the check from crtc->valid to crtc != NULL with no functional
> change here.
> 
> Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>
> Cc: Alex Hung <alex.hung@amd.com>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>   tests/amdgpu/amd_multidisplay_modeset.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/tests/amdgpu/amd_multidisplay_modeset.c b/tests/amdgpu/amd_multidisplay_modeset.c
> index 98ca2c79470b..3aa7b3483a28 100644
> --- a/tests/amdgpu/amd_multidisplay_modeset.c
> +++ b/tests/amdgpu/amd_multidisplay_modeset.c
> @@ -327,6 +327,8 @@ static void multiple_display_test(struct data_t *data, enum sub_test test_mode)
>   
>   			crtc = igt_crtc_for_pipe(display, j);
>   
> +			igt_assert_f(crtc->valid, "There is no pipe %s\n", kmstest_pipe_name(j));
> +
>   			igt_create_pattern_fb(data->fd, kmode->hdisplay,
>   					kmode->vdisplay, DRM_FORMAT_XRGB8888,
>   					0, (buf + j));


  reply	other threads:[~2026-03-27  0:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 12:53 [PATCH i-g-t v3 0/5] Prepare for returning NULL from igt_crtc_for_pipe() Jani Nikula
2026-03-26 12:53 ` [PATCH i-g-t v3 1/5] tests/amdgpu/amd_multidisplay_modeset: " Jani Nikula
2026-03-27  0:49   ` Alex Hung [this message]
2026-03-26 12:53 ` [PATCH i-g-t v3 2/5] tests/intel/kms_joiner: " Jani Nikula
2026-03-26 12:53 ` [PATCH i-g-t v3 3/5] tests/intel/kms_joiner_helper: " Jani Nikula
2026-03-26 12:53 ` [PATCH i-g-t v3 4/5] tests/intel/kms_pipe_b_c_ivb: " Jani Nikula
2026-03-26 12:53 ` [PATCH i-g-t v3 5/5] tests/intel/kms_pipe_stress: " Jani Nikula
2026-03-26 22:17 ` ✓ Xe.CI.BAT: success for Prepare for returning NULL from igt_crtc_for_pipe() (rev3) Patchwork
2026-03-26 22:24 ` ✓ i915.CI.BAT: " Patchwork
2026-03-27 15:20 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-27 22:17 ` ✓ 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=29138133-adad-4586-a2e0-30772cb915e0@amd.com \
    --to=alex.hung@amd.com \
    --cc=aurabindo.pillai@amd.com \
    --cc=harry.wentland@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=ville.syrjala@linux.intel.com \
    --cc=vitaly.prosyak@amd.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