From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests: i915_pm_rpm : Dump i915_runtime_pm_status
Date: Fri, 11 Feb 2022 17:23:39 -0800 [thread overview]
Message-ID: <878rug27z8.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220211161314.16602-1-anshuman.gupta@intel.com>
On Fri, 11 Feb 2022 08:13:14 -0800, Anshuman Gupta wrote:
>
> Dump i915_runtime_pm_status conditionally whenever runtime pm status
> got active and it was expected to be suspended.
>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
> tests/i915/i915_pm_rpm.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/tests/i915/i915_pm_rpm.c b/tests/i915/i915_pm_rpm.c
> index 648b0cffb..d1ba69af4 100644
> --- a/tests/i915/i915_pm_rpm.c
> +++ b/tests/i915/i915_pm_rpm.c
> @@ -201,10 +201,17 @@ static bool wait_for_pc8_status(enum pc8_status status)
>
> static bool wait_for_suspended(void)
> {
> - if (has_pc8 && !has_runtime_pm)
> + bool suspended = false;
Nit but maybe let's move this into the else, I'll move and merge it:
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> +
> + if (has_pc8 && !has_runtime_pm) {
> return wait_for_pc8_status(PC8_ENABLED);
> - else
> - return igt_wait_for_pm_status(IGT_RUNTIME_PM_STATUS_SUSPENDED);
> + } else {
> + suspended = igt_wait_for_pm_status(IGT_RUNTIME_PM_STATUS_SUSPENDED);
> + if (!suspended)
> + igt_debugfs_dump(drm_fd, "i915_runtime_pm_status");
> +
> + return suspended;
> + }
> }
>
> static bool wait_for_active(void)
> --
> 2.26.2
>
next prev parent reply other threads:[~2022-02-12 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:13 [igt-dev] [PATCH i-g-t] tests: i915_pm_rpm : Dump i915_runtime_pm_status Anshuman Gupta
2022-02-11 16:44 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2022-02-12 1:23 ` Dixit, Ashutosh [this message]
2022-02-14 15:47 ` [igt-dev] [PATCH i-g-t] " Gupta, Anshuman
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=878rug27z8.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.