Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t V2 1/2] intel-ci/xe: Update kms blocklist documentation
Date: Thu, 5 Oct 2023 19:18:51 +0530	[thread overview]
Message-ID: <ae35734e-36c6-43c8-888e-9509c489b1fa@intel.com> (raw)
In-Reply-To: <20231005125948.2986826-2-bhanuprakash.modem@intel.com>

LGTM

Reviewed-by: Swati Sharma <swati2.sharma@intel.com>


On 05-Oct-23 6:29 PM, Bhanuprakash Modem wrote:
> Add justification to kms blocklist.
> 
> V2: - Add justification for multidisplay blocklist
> 
> Cc: Swati Sharma <swati2.sharma@intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
>   tests/intel-ci/xe.blocklist.txt | 15 +++++++++------
>   1 file changed, 9 insertions(+), 6 deletions(-)
> 
> diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
> index e73018ec6..f4a57aa01 100644
> --- a/tests/intel-ci/xe.blocklist.txt
> +++ b/tests/intel-ci/xe.blocklist.txt
> @@ -44,20 +44,18 @@ igt@syncobj_.*
>   igt@template
>   igt@tools_test
>   ##################################################################
> -# Pipe E, F, G and H
> +# KMS: Pipe E, F, G and H are not available on Intel hardware,
> +# hence can't use more than 4 displays.
>   ##################################################################
>   igt@.*@.*pipe-(e|f|g|h).*
> -##################################################################
> -# Multidisplay
> -##################################################################
>   igt@kms_bw@.*-(5|6|7|8)-displays-.*
>   ##################################################################
> +# KMS: Tests specific to i915 driver
> +##################################################################
>   igt@kms_draw_crc@draw-method-(mmap-cpu|mmap-gtt|pwrite)
>   igt@kms_pipe_b_c_ivb@.*
>   igt@kms_pwrite_crc
> -igt@kms_ccs@.*
>   igt@kms_frontbuffer_tracking@.*-(cpu|gtt|pwrite)
> -igt@kms_fbcon_fbt@(fbc|psr)(-suspend)
>   igt@kms_fence_pin_leak
>   igt@kms_busy@.*
>   igt@kms_psr@.*_mmap_(cpu|gtt)
> @@ -69,3 +67,8 @@ igt@kms_addfb_basic@clobberred-modifier
>   igt@kms_rotation_crc@exhaust-fences
>   igt@kms_force_connector_basic@force-load-detect
>   ##################################################################
> +# KMS: Yet to add/missing XE support
> +##################################################################
> +igt@kms_ccs@.*
> +igt@kms_fbcon_fbt@(fbc|psr)(-suspend)
> +##################################################################

  reply	other threads:[~2023-10-05 13:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 12:59 [igt-dev] [i-g-t V2 0/2] Update XE blocklist Bhanuprakash Modem
2023-10-05 12:59 ` [igt-dev] [i-g-t V2 1/2] intel-ci/xe: Update kms blocklist documentation Bhanuprakash Modem
2023-10-05 13:48   ` Sharma, Swati2 [this message]
2023-10-05 12:59 ` [igt-dev] [i-g-t V2 2/2] intel-ci/xe: Update XE kms blocklist Bhanuprakash Modem
2023-10-05 14:01   ` Sharma, Swati2
2023-10-05 16:24 ` [igt-dev] ✓ Fi.CI.BAT: success for Update XE blocklist (rev2) Patchwork
2023-10-05 17:23 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-06  6:47 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=ae35734e-36c6-43c8-888e-9509c489b1fa@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=bhanuprakash.modem@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