From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/selftests; Do not try to sanitize mock HW
Date: Fri, 27 Sep 2019 23:45:23 +0300 [thread overview]
Message-ID: <20190927204523.GB2902@intel.intel> (raw)
In-Reply-To: <20190927191443.14126-2-chris@chris-wilson.co.uk>
Hi Chris,
On Fri, Sep 27, 2019 at 08:14:43PM +0100, Chris Wilson wrote:
> If we are mocking the device, skip trying to sanitize the pm HW state.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Andi Shyti <andi.shyti@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gt_pm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_pm.c b/drivers/gpu/drm/i915/gt/intel_gt_pm.c
> index 42f175d9b98c..29fa1dabbc2e 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_pm.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_pm.c
> @@ -137,7 +137,8 @@ void intel_gt_sanitize(struct intel_gt *gt, bool force)
>
> void intel_gt_pm_disable(struct intel_gt *gt)
> {
> - intel_sanitize_gt_powersave(gt->i915);
> + if (!is_mock_gt(gt))
> + intel_sanitize_gt_powersave(gt->i915);
Cool!
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-09-27 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 19:14 [PATCH 1/2] drm/i915/selftests: Provide a mock GPU reset routine Chris Wilson
2019-09-27 19:14 ` [PATCH 2/2] drm/i915/selftests; Do not try to sanitize mock HW Chris Wilson
2019-09-27 20:45 ` Andi Shyti [this message]
2019-09-27 20:12 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/selftests: Provide a mock GPU reset routine Patchwork
2019-09-27 20:41 ` [PATCH 1/2] " Andi Shyti
2019-09-27 20:54 ` Chris Wilson
2019-09-27 21:09 ` Chris Wilson
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=20190927204523.GB2902@intel.intel \
--to=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox