From: Imre Deak <imre.deak@intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: don't take runtime PM reference around freeze/thaw
Date: Thu, 19 Jun 2014 16:25:55 +0300 [thread overview]
Message-ID: <1403184355.27481.8.camel@intelbox> (raw)
In-Reply-To: <1403110376-1889-2-git-send-email-jbarnes@virtuousgeek.org>
[-- Attachment #1.1: Type: text/plain, Size: 1312 bytes --]
On Wed, 2014-06-18 at 09:52 -0700, Jesse Barnes wrote:
> We should be taking the right power well refs these days, so this
> shouldn't be necessary. It also gets in the way of re-using these
> routines for S0iX states, as those need all the power saving features
> enabled.
>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Reviewed-by: Imre Deak <imre.deak@intel.com>
Btw, we also have the same redundancy in intel_dp_detect().
--Imre
> ---
> drivers/gpu/drm/i915/i915_drv.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index be97741..6eb45ac 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -496,8 +496,6 @@ static int i915_drm_freeze(struct drm_device *dev)
> struct drm_crtc *crtc;
> pci_power_t opregion_target_state;
>
> - intel_runtime_pm_get(dev_priv);
> -
> /* ignore lid events during suspend */
> mutex_lock(&dev_priv->modeset_restore_lock);
> dev_priv->modeset_restore = MODESET_SUSPENDED;
> @@ -686,7 +684,6 @@ static int __i915_drm_thaw(struct drm_device *dev, bool restore_gtt_mappings)
>
> intel_opregion_notify_adapter(dev, PCI_D0);
>
> - intel_runtime_pm_put(dev_priv);
> return 0;
> }
>
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-06-19 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 16:52 [PATCH 1/2] drm/i915: use runtime irq suspend/resume in freeze/thaw Jesse Barnes
2014-06-18 16:52 ` [PATCH 2/2] drm/i915: don't take runtime PM reference around freeze/thaw Jesse Barnes
2014-06-19 13:25 ` Imre Deak [this message]
2014-06-19 16:05 ` Daniel Vetter
2014-06-19 13:24 ` [PATCH 1/2] drm/i915: use runtime irq suspend/resume in freeze/thaw Imre Deak
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=1403184355.27481.8.camel@intelbox \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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.