From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm/i915: fix VDD state tracking after system resume
Date: Wed, 30 Jul 2014 15:41:07 +0200 [thread overview]
Message-ID: <20140730134107.GQ4747@phenom.ffwll.local> (raw)
In-Reply-To: <1406725052-31791-2-git-send-email-imre.deak@intel.com>
On Wed, Jul 30, 2014 at 03:57:32PM +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.
>
> Reported-and-tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 1edfd1a..fdb5657 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -12977,6 +12977,12 @@ void intel_modeset_setup_hw_state(struct drm_device *dev,
> /* HW state is read out, now we need to sanitize this mess. */
> list_for_each_entry(encoder, &dev->mode_config.encoder_list,
> base.head) {
> + /*
> + * Do the following only during resume, since at driver
> + * loading it's done early when initializing the encoder.
> + */
> + if (force_restore)
> + intel_edp_panel_vdd_sanitize(encoder);
This should be put into an encoder->reset callback.
-Daniel
> intel_sanitize_encoder(encoder);
> }
>
> --
> 1.8.4
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2014-07-30 13:40 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 [this message]
2014-07-31 11:03 ` [PATCH v3 " Imre Deak
2014-08-01 11:56 ` Ville Syrjälä
2014-08-04 8:08 ` Daniel Vetter
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=20140730134107.GQ4747@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=imre.deak@intel.com \
--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