From: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
To: daniel.vetter@intel.com, jani.nikula@linux.intel.com,
seanpaul@chromium.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
ville.syrjala@linux.intel.com
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Subject: [PATCH v2 2/2] Test case for drm_vblank_cleanup refcount validation patch
Date: Tue, 24 Oct 2017 22:18:17 +0530 [thread overview]
Message-ID: <20171024164817.11287-2-prasannatsmkumar@gmail.com> (raw)
In-Reply-To: <20171024164817.11287-1-prasannatsmkumar@gmail.com>
In i915 driver unload drm_vblank_get is added to test whether
drm_vblank_cleanup refcount validation patch is working.
Signed-off-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
---
Changes in v2:
Use drm_crtc_vblank_get instead of _put. In previous patch _put was wrongly
used.
drivers/gpu/drm/i915/i915_drv.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index 9f45cfe..4aee1c0 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -1373,6 +1373,13 @@ void i915_driver_unload(struct drm_device *dev)
struct drm_i915_private *dev_priv = to_i915(dev);
struct pci_dev *pdev = dev_priv->drm.pdev;
+ enum pipe pipe;
+ for_each_pipe(dev_priv, pipe) {
+ struct intel_crtc *crtc = intel_get_crtc_for_pipe(dev_priv,
+ pipe);
+ drm_crtc_vblank_get(&crtc->base);
+ }
+
i915_driver_unregister(dev_priv);
if (i915_gem_suspend(dev_priv))
--
2.10.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-24 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 16:48 [PATCH v2 1/2] drm: drm_vblank_cleanup: WARN when refcount > 0 PrasannaKumar Muralidharan
2017-10-24 16:48 ` PrasannaKumar Muralidharan [this message]
2017-10-25 15:14 ` [PATCH v2 2/2] Test case for drm_vblank_cleanup refcount validation patch PrasannaKumar Muralidharan
2017-10-30 10:10 ` [Intel-gfx] " Daniel Vetter
2017-10-30 12:31 ` PrasannaKumar Muralidharan
2017-10-31 10:21 ` Daniel Vetter
2017-10-31 15:07 ` PrasannaKumar Muralidharan
2017-10-31 16:27 ` Daniel Vetter
2017-11-01 4:18 ` [Intel-gfx] " PrasannaKumar Muralidharan
2017-11-01 8:53 ` Daniel Vetter
2017-11-01 16:00 ` PrasannaKumar Muralidharan
2017-10-24 17:19 ` ✗ Fi.CI.BAT: warning for series starting with [v2,1/2] drm: drm_vblank_cleanup: WARN when refcount > 0 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=20171024164817.11287-2-prasannatsmkumar@gmail.com \
--to=prasannatsmkumar@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=seanpaul@chromium.org \
--cc=ville.syrjala@linux.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