Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: igt-dev@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [igt-dev] Mandatory Test Suite for KMS Drivers?
Date: Thu, 3 Mar 2022 05:52:57 -0500	[thread overview]
Message-ID: <YiCeCeNobS2FCiQB@intel.com> (raw)
In-Reply-To: <20220303090507.grenwdro7u4fzmoe@houat>

On Thu, Mar 03, 2022 at 10:05:07AM +0100, Maxime Ripard wrote:
> Hi,
> 
> Back at XDC we floated the idea of creating a test suite for IGT that we
> expect any KMS driver to pass, similar to what v4l2-compliance and
> cec-compliance provide for v4l2 and CEC respectively.
> 
> I was looking at the list of tests, and it's fairly massive, so it's not
> clear to me what tests we could start this suite with. I can only assume
> all the KMS (but the chamelium ones) and fbdev related ones would be a
> good start?
> 
> What do you think?

I believe we should start with the group of the tests that we know that
are reliably passing today on most of the platforms and then increase
the list as the tests and drivers become more reliable.

For instance, many of these would be candidate to be filtered out for now
https://intel-gfx-ci.01.org/tree/drm-next/index.html?testfilter=kms

compared to the whole view of kms tests:
https://intel-gfx-ci.01.org/tree/drm-next/shards-all.html?testfilter=kms

Thanks,
Rodrigo.

> Maxime


  reply	other threads:[~2022-03-03 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03  9:05 [igt-dev] Mandatory Test Suite for KMS Drivers? Maxime Ripard
2022-03-03 10:52 ` Rodrigo Vivi [this message]
2022-03-04  8:45   ` Daniel Stone
2022-03-08 15:57     ` Maxime Ripard
2022-03-08 15:55   ` Maxime Ripard

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=YiCeCeNobS2FCiQB@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maxime@cerno.tech \
    /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