From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2 3/4] i915/i915_pm_rpm: Add PC10 display off test
Date: Thu, 4 Feb 2021 04:12:30 +0000 [thread overview]
Message-ID: <1dde5b334a214d238082734b32477ed1@intel.com> (raw)
In-Reply-To: <161236905581.21832.9494400750427364629@build.alporthouse.com>
> -----Original Message-----
> From: Chris Wilson <chris@chris-wilson.co.uk>
> Sent: Wednesday, February 3, 2021 9:48 PM
> To: Gupta, Anshuman <anshuman.gupta@intel.com>; igt-
> dev@lists.freedesktop.org
> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> Subject: Re: [igt-dev] [PATCH i-g-t v2 3/4] i915/i915_pm_rpm: Add PC10
> display off test
>
> Quoting Anshuman Gupta (2021-02-03 10:03:09)
> > Add a test to validate PC10 residencies while all output's display is
> > off.
>
> The pc10 tests look nice and straightforward. Just a general question on
> whether 30s timeout is too lax or just right?
Thanks for review.
I had just followed timeout time from existing pc8 tests for HASWELL/BROADWEL
which was 30 second. It is not an engineering number.
IMO i915 default auto-suspend ms time 10 sec
(cat /sys/devices/pci0000\:00/0000\:00\:02.0/power/autosuspend_delay_ms)
Considering above it may have some scope of optimization.
Could you please provide some input on it.
Thanks,
Anshuman Gupta.
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-02-04 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 10:03 [igt-dev] [PATCH i-g-t v2 0/4] PC state igt test Anshuman Gupta
2021-02-03 10:03 ` [igt-dev] [PATCH i-g-t v2 1/4] i915/i915_pm_rpm: Enable PC8+ residency test Anshuman Gupta
2021-02-03 11:37 ` Chris Wilson
2021-02-11 10:41 ` Gupta, Anshuman
2021-02-03 10:03 ` [igt-dev] [PATCH i-g-t v2 2/4] i915/i915_pm_rpm: optimize modeset-pc8-residency-stress test Anshuman Gupta
2021-02-03 10:03 ` [igt-dev] [PATCH i-g-t v2 3/4] i915/i915_pm_rpm: Add PC10 display off test Anshuman Gupta
2021-02-03 16:17 ` Chris Wilson
2021-02-04 4:12 ` Gupta, Anshuman [this message]
2021-02-24 12:21 ` Gupta, Anshuman
2021-02-03 10:03 ` [igt-dev] [PATCH i-g-t v2 4/4] i915/i915_pm_rpm: Add PC10 idle display on test Anshuman Gupta
2021-02-03 13:23 ` [igt-dev] ✓ Fi.CI.BAT: success for PC state igt test (rev2) Patchwork
2021-02-03 16:13 ` [igt-dev] ✓ Fi.CI.IGT: " 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=1dde5b334a214d238082734b32477ed1@intel.com \
--to=anshuman.gupta@intel.com \
--cc=chris@chris-wilson.co.uk \
--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