From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: drop encoder hot_plug calls at resume
Date: Wed, 21 May 2014 08:53:25 +0200 [thread overview]
Message-ID: <20140521065325.GF24095@phenom.ffwll.local> (raw)
In-Reply-To: <1400624735-4220-1-git-send-email-jbarnes@virtuousgeek.org>
On Tue, May 20, 2014 at 03:25:33PM -0700, Jesse Barnes wrote:
> We really just want to go detect displays again and fire off a hotplug
> event if things have changed, not go through full hotplug processing.
>
> Requested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Yeah, still can't remember why we've done this, and the commit message is
silent.
Queued for -next, thanks for the patch.
-Daniel
> ---
> drivers/gpu/drm/i915/i915_drv.c | 20 +-------------------
> 1 file changed, 1 insertion(+), 19 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index b948c71..302495f 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -551,24 +551,6 @@ void intel_console_resume(struct work_struct *work)
> console_unlock();
> }
>
> -static void intel_resume_hotplug(struct drm_device *dev)
> -{
> - struct drm_mode_config *mode_config = &dev->mode_config;
> - struct intel_encoder *encoder;
> -
> - mutex_lock(&mode_config->mutex);
> - DRM_DEBUG_KMS("running encoder hotplug functions\n");
> -
> - list_for_each_entry(encoder, &mode_config->encoder_list, base.head)
> - if (encoder->hot_plug)
> - encoder->hot_plug(encoder);
> -
> - mutex_unlock(&mode_config->mutex);
> -
> - /* Just fire off a uevent and let userspace tell us what to do */
> - drm_helper_hpd_irq_event(dev);
> -}
> -
> static int i915_drm_thaw_early(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> @@ -624,7 +606,7 @@ static int __i915_drm_thaw(struct drm_device *dev, bool restore_gtt_mappings)
> intel_hpd_init(dev);
> dev_priv->enable_hotplug_processing = true;
> /* Config may have changed between suspend and resume */
> - intel_resume_hotplug(dev);
> + drm_helper_hpd_irq_event(dev);
> }
>
> intel_opregion_init(dev);
> --
> 1.8.4.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-05-21 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 22:25 [PATCH 1/3] drm/i915: drop encoder hot_plug calls at resume Jesse Barnes
2014-05-20 22:25 ` [PATCH 2/3] drm: add async version of hpd_irq_event Jesse Barnes
2014-05-21 6:50 ` Daniel Vetter
2014-05-20 22:25 ` [PATCH 3/3] drm/i915: use async hpd_irq_event function on resume Jesse Barnes
2014-05-21 6:52 ` Daniel Vetter
2014-05-21 15:00 ` Jesse Barnes
2014-05-21 15:12 ` Daniel Vetter
2014-05-21 6:53 ` Daniel Vetter [this message]
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=20140521065325.GF24095@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox