public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] drm/i915: fix VDD state tracking after system resume
Date: Mon, 4 Aug 2014 10:08:40 +0200	[thread overview]
Message-ID: <20140804080840.GJ8727@phenom.ffwll.local> (raw)
In-Reply-To: <20140801115654.GY4193@intel.com>

On Fri, Aug 01, 2014 at 02:56:54PM +0300, Ville Syrjälä wrote:
> On Thu, Jul 31, 2014 at 02:03:36PM +0300, Imre Deak wrote:
> > Just like during booting the BIOS can leave the VDD bit enabled after
> > system resume. So apply the same state sanitization there too. This
> > fixes a problem where after resume the port power domain refcount gets
> > unbalanced.
> > 
> > v2:
> > - unchanged
> > v3:
> > - call edp sanitizing from the encoder reset handler (Daniel)
> 
> It happens a bit earlier than with the earlier attempt, but if
> it works it works.
> 
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-08-04  8:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 12:57 [PATCH v2 1/2] drm/i915: factor out intel_edp_panel_vdd_sanitize Imre Deak
2014-07-30 12:57 ` [PATCH v2 2/2] drm/i915: fix VDD state tracking after system resume Imre Deak
2014-07-30 13:41   ` Daniel Vetter
2014-07-31 11:03   ` [PATCH v3 " Imre Deak
2014-08-01 11:56     ` Ville Syrjälä
2014-08-04  8:08       ` Daniel Vetter [this message]
2014-07-30 13:42 ` [PATCH v2 1/2] drm/i915: factor out intel_edp_panel_vdd_sanitize Daniel Vetter

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=20140804080840.GJ8727@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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