From: Jani Nikula <jani.nikula@intel.com>
To: "Sundaresan, Sujaritha" <sujaritha.sundaresan@intel.com>,
"Gupta, Anshuman" <anshuman.gupta@intel.com>,
"Sousa, Gustavo" <gustavo.sousa@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
"Piecielska, Katarzyna" <katarzyna.piecielska@intel.com>,
igt-dev@lists.freedesktop.org, imre.deak@linux.intel.com
Subject: Re: [PATCH i-g-t, v4] tests/intel/xe_pm: Add tests for suspend without display
Date: Mon, 23 Sep 2024 12:30:19 +0300 [thread overview]
Message-ID: <87a5fy7m50.fsf@intel.com> (raw)
In-Reply-To: <99543131-86f3-474b-a9c5-6e28eae5c6ba@intel.com>
On Fri, 13 Sep 2024, "Sundaresan, Sujaritha" <sujaritha.sundaresan@intel.com> wrote:
> So in this case neither disable_display, nor enable_display will work to
> have a truly display free test run ?
xe.enable_display is called xe.probe_display since commit 1eda95cba9df
("drm/xe: Rename enable_display module param") to reduce the confusion
between the two params.
xe.probe_display=0 will give you a "truly display free test run", but
you just can't properly test suspend/resume like that. If the hardware
has display IP, it just won't magically go to sleep if you don't touch
it.
Looks like the premise of the test is flawed.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-23 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 9:20 [PATCH i-g-t, v4] tests/intel/xe_pm: Add tests for suspend without display Sujaritha Sundaresan
2024-08-22 10:07 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-22 10:09 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-22 14:36 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-22 16:52 ` [PATCH i-g-t, v4] " Kamil Konieczny
2024-08-22 17:45 ` Gustavo Sousa
2024-08-22 21:01 ` Lucas De Marchi
2024-08-26 11:12 ` Sundaresan, Sujaritha
2024-08-26 13:57 ` Lucas De Marchi
2024-08-27 8:10 ` Sundaresan, Sujaritha
2024-08-26 14:36 ` Gustavo Sousa
2024-08-27 8:11 ` Sundaresan, Sujaritha
2024-08-27 9:29 ` Gupta, Anshuman
2024-08-27 12:48 ` Gustavo Sousa
[not found] ` <CY5PR11MB6211B873C18594896BD21FA295942@CY5PR11MB6211.namprd11.prod.outlook.com>
2024-08-28 8:46 ` Sundaresan, Sujaritha
2024-09-11 5:19 ` Sundaresan, Sujaritha
2024-09-11 15:10 ` Jani Nikula
2024-09-13 8:29 ` Sundaresan, Sujaritha
2024-09-23 9:30 ` Jani Nikula [this message]
2024-08-23 6:20 ` ✗ 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=87a5fy7m50.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=imre.deak@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=katarzyna.piecielska@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=sujaritha.sundaresan@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