Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] docs/reference: add links to testplan-based documentation
Date: Thu, 17 Aug 2023 23:08:24 +0530	[thread overview]
Message-ID: <d8019c58-6de5-77af-967e-bb5494e9e9cb@intel.com> (raw)
In-Reply-To: <20230817093504.75749-1-mauro.chehab@linux.intel.com>

Hi Mauro,

On Thu-17-08-2023 03:05 pm, Mauro Carvalho Chehab wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
> 
> Instead of relying on runtime-based docs, use the documentation
> parsed via testplan for i915, Xe and KMS tests.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>   .../igt-gpu-tools/igt_test_programs.xml       | 63 ++++++++-----------
>   docs/reference/igt-gpu-tools/meson.build      |  4 --
>   2 files changed, 27 insertions(+), 40 deletions(-)
> 
> diff --git a/docs/reference/igt-gpu-tools/igt_test_programs.xml b/docs/reference/igt-gpu-tools/igt_test_programs.xml
> index 92bc33ba83f6..51f8cac05f98 100644
> --- a/docs/reference/igt-gpu-tools/igt_test_programs.xml
> +++ b/docs/reference/igt-gpu-tools/igt_test_programs.xml
> @@ -147,42 +147,6 @@
>       <xi:include href="igt_test_programs_gem_description.xml"/>
>     </refentry>
>   
> -  <refentry id="igt-gen3-tests">
> -    <refnamediv>
> -      <refname>Gen 3 Tests</refname>
> -      <refpurpose>Tests specific to gen 3</refpurpose>
> -    </refnamediv>
> -    <xi:include href="igt_test_programs_gen3_programs.xml"/>
> -    <xi:include href="igt_test_programs_gen3_description.xml"/>
> -  </refentry>
> -
> -  <refentry id="igt-gen7-tests">
> -    <refnamediv>
> -      <refname>Gen 7 Tests</refname>
> -      <refpurpose>Tests specific to gen 7</refpurpose>
> -    </refnamediv>
> -    <xi:include href="igt_test_programs_gen7_programs.xml"/>
> -    <xi:include href="igt_test_programs_gen7_description.xml"/>
> -  </refentry>
> -
> -  <refentry id="igt-i915-tests">
> -    <refnamediv>
> -      <refname>i915 Tests</refname>
> -      <refpurpose>Tests for overall i915 driver behaviour</refpurpose>
> -    </refnamediv>
> -    <xi:include href="igt_test_programs_i915_programs.xml"/>
> -    <xi:include href="igt_test_programs_i915_description.xml"/>
> -  </refentry>
> -
> -  <refentry id="igt-kms-tests">
> -    <refnamediv>
> -      <refname>KMS Tests</refname>
> -      <refpurpose>Tests for kernel mode setting</refpurpose>
> -    </refnamediv>
> -    <xi:include href="igt_test_programs_kms_programs.xml"/>
> -    <xi:include href="igt_test_programs_kms_description.xml"/>
> -  </refentry>
> -
>     <refentry id="igt-meta-tests">
>       <refnamediv>
>         <refname>Meta Tests</refname>
> @@ -255,6 +219,33 @@
>       <xi:include href="igt_test_programs_vgem_description.xml"/>
>     </refentry>
>   
> +  <refentry id="igt-xe-tests">
> +    <refnamediv>
> +      <refname>
> +          <ulink url="../testplan/xe_tests.html" type="http">Xe Tests</ulink>

As the testplan is not inside the reference dir, the URL must be: 
"../../../testplan/xe_tests.html"

Also, is there anyway to put these urls in index.html, instead of 
opening igt-xe-tests.html and from there open the actual xe_tests.html?

> +      </refname>
> +      <refpurpose>Tests for the Intel Xe driver</refpurpose>
> +    </refnamediv>
> +  </refentry>
> +
> +  <refentry id="igt-i915-tests">
> +    <refnamediv>
> +      <refname>
> +        <ulink url="../testplan/i915_tests.html" type="http">i915 Tests</ulink>
> +      </refname>
> +      <refpurpose>Tests for the Intel i915 driver</refpurpose>
> +    </refnamediv>
> +  </refentry>
> +
> +  <refentry id="igt-kms-tests">
> +    <refnamediv>
> +      <refname>
> +        <ulink url="../testplan/kms_tests.html" type="http">KMS Tests</ulink>
> +      </refname>
> +      <refpurpose>Tests for kernel mode setting</refpurpose>
> +    </refnamediv>
> +  </refentry>
> +
>     <glossary>
>       <title>Glossary</title>
>   
> diff --git a/docs/reference/igt-gpu-tools/meson.build b/docs/reference/igt-gpu-tools/meson.build
> index 6b832ad279cf..9bb5ca7e0798 100644
> --- a/docs/reference/igt-gpu-tools/meson.build
> +++ b/docs/reference/igt-gpu-tools/meson.build
> @@ -29,10 +29,6 @@ test_groups = [
>   	'debugfs',
>   	'drm',
>   	'gem',
> -	'gen3',
> -	'gen7',
> -	'i915',
> -	'kms',

Also, we must drop testdisplay, since it is already covered by kms tests.

- Bhanu

>   	'meta',
>   	'perf',
>   	'pm',


  parent reply	other threads:[~2023-08-17 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17  9:35 [igt-dev] [PATCH i-g-t] docs/reference: add links to testplan-based documentation Mauro Carvalho Chehab
2023-08-17 11:00 ` [igt-dev] ○ CI.xeBAT: info for " Patchwork
2023-08-17 11:01 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-17 16:00 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-08-17 17:38 ` Modem, Bhanuprakash [this message]
2023-08-29 11:51   ` Mauro Carvalho Chehab
2023-08-18  1:02 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=d8019c58-6de5-77af-967e-bb5494e9e9cb@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mauro.chehab@linux.intel.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