Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t 1/3] tests/intel/xe_pm: Reword *-basic description
Date: Fri,  3 May 2024 15:47:43 -0700	[thread overview]
Message-ID: <20240503224745.14890-1-lucas.demarchi@intel.com> (raw)

It doesn't make much sense to say the CPU is going to be put in D*
state. Reword it so the CPU and GPU states are better captured.

Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
 tests/intel/xe_pm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/intel/xe_pm.c b/tests/intel/xe_pm.c
index 51442537b..5e79e80ec 100644
--- a/tests/intel/xe_pm.c
+++ b/tests/intel/xe_pm.c
@@ -223,7 +223,7 @@ static void close_fw_handle(int sig)
 #define MAX_VMAS 2
 /**
  * SUBTEST: %s-basic
- * Description: set GPU state to %arg[1] and test suspend/autoresume
+ * Description: test CPU/GPU in and out of s/d state from %arg[1]
  * Functionality: pm - %arg[1]
  * GPU requirements: D3 feature should be supported
  *
-- 
2.43.0


             reply	other threads:[~2024-05-03 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 22:47 Lucas De Marchi [this message]
2024-05-03 22:47 ` [PATCH i-g-t 2/3] lib/igt_aux: Name function according to sysfs file Lucas De Marchi
2024-05-06 14:12   ` Rodrigo Vivi
2024-05-03 22:47 ` [PATCH i-g-t 3/3] tests/intel/xe_pm: S4 to go up to devices only Lucas De Marchi
2024-05-06 14:14   ` Rodrigo Vivi
2024-05-06 16:48     ` Lucas De Marchi
2024-05-03 23:28 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] tests/intel/xe_pm: Reword *-basic description Patchwork
2024-05-04  0:10 ` ✓ CI.xeBAT: " Patchwork
2024-05-04  2:22 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-04 11:51 ` ✗ Fi.CI.IGT: " Patchwork
2024-05-06 14:10 ` [PATCH i-g-t 1/3] " Rodrigo Vivi
2024-05-06 20:05 ` Lucas De Marchi

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=20240503224745.14890-1-lucas.demarchi@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=rodrigo.vivi@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