All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
To: Mark Yacoub <markyacoub@chromium.org>
Cc: igt-dev@lists.freedesktop.org, seanpaul@chromium.org,
	petri.latvala@intel.com, Mark Yacoub <markyacoub@google.com>
Subject: Re: [igt-dev] [PATCH 2/2] kms_addfb_basic: Check for AMDGPU and MSM bad pitch.
Date: Tue, 6 Jul 2021 09:41:10 -0400	[thread overview]
Message-ID: <20210706134110.iopwgjfwpnibtyjb@outlook.office365.com> (raw)
In-Reply-To: <20210701174424.2261499-2-markyacoub@chromium.org>

On 07/01, Mark Yacoub wrote:
> From: Mark Yacoub <markyacoub@google.com>
> 
> [Why]
> AMDGPU and MSM devices have a known errno when it fails coorectly for
> bad pitches.
> 
> [How]
> Assert `errno` to `EINVAL` for both AMDGPU and MSM as well.
> 
> Signed-off-by: Mark Yacoub <markyacoub@chromium.org>
> ---
>  tests/kms_addfb_basic.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/kms_addfb_basic.c b/tests/kms_addfb_basic.c
> index 85c14be5..91fb6ac9 100644
> --- a/tests/kms_addfb_basic.c
> +++ b/tests/kms_addfb_basic.c
> @@ -310,7 +310,7 @@ static void pitch_tests(int fd)
>  			f.pitches[0] = bad_pitches[i];
>  			igt_assert_eq(igt_ioctl(fd, DRM_IOCTL_MODE_ADDFB2, &f), -1);
>  			igt_assert(errno != 0);
> -			if (is_i915_device(fd)) {
> +			if (is_i915_device(fd) || is_amdgpu_device(fd) || is_msm_device(fd)) {
>  				igt_assert_eq(errno, EINVAL);
>  			} else if (is_nouveau_device(fd)) {
>  				if (bad_pitches[i] > 4 * 1024)
> -- 
> 2.32.0.93.g670b81a890-goog
> 

Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>

Btw, from the CI log, we have:

igt@kms_addfb_basic@invalid-smem-bo-on-discrete:
  shard-apl: NOTRUN -> FAIL
  shard-tglb: NOTRUN -> FAIL
  shard-glk: NOTRUN -> FAIL
  shard-kbl: NOTRUN -> FAIL
  shard-snb: NOTRUN -> FAIL
  shard-iclb: NOTRUN -> FAIL

igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
  shard-iclb: NOTRUN -> SKIP +1 similar issue

I don't know why your patch makes something that was not running start
to run. Any theory?

Thanks

-- 
Rodrigo Siqueira
https://siqueira.tech
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-07-06 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 17:44 [igt-dev] [PATCH 1/2] drmtest: Add is_msm_device check Mark Yacoub
2021-07-01 17:44 ` [igt-dev] [PATCH 2/2] kms_addfb_basic: Check for AMDGPU and MSM bad pitch Mark Yacoub
2021-07-06 13:41   ` Rodrigo Siqueira [this message]
2021-07-07 16:09     ` Mark Yacoub
2021-07-09 12:32       ` Arkadiusz Hiler
2021-07-01 19:38 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [1/2] drmtest: Add is_msm_device check Patchwork
2021-07-02  0:42 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-06 13:37 ` [igt-dev] [PATCH 1/2] " Rodrigo Siqueira
  -- strict thread matches above, loose matches on Subject: below --
2021-07-01 17:26 Mark Yacoub
2021-07-01 17:26 ` [igt-dev] [PATCH 2/2] kms_addfb_basic: Check for AMDGPU and MSM bad pitch Mark Yacoub

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=20210706134110.iopwgjfwpnibtyjb@outlook.office365.com \
    --to=rodrigo.siqueira@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=markyacoub@chromium.org \
    --cc=markyacoub@google.com \
    --cc=petri.latvala@intel.com \
    --cc=seanpaul@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.