All of lore.kernel.org
 help / color / mirror / Atom feed
From: "R, Durgadoss" <durgadoss.r@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm/i915: Also delay first activation for SKL+
Date: Thu, 19 Nov 2015 06:07:50 +0000	[thread overview]
Message-ID: <4D68720C2E767A4AA6A8796D42C8EB59092B63D9@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <1447893575-25369-2-git-send-email-rodrigo.vivi@intel.com>

>-----Original Message-----
>From: Vivi, Rodrigo
>Sent: Thursday, November 19, 2015 6:10 AM
>To: intel-gfx@lists.freedesktop.org
>Cc: Vivi, Rodrigo; R, Durgadoss
>Subject: [PATCH 1/3] drm/i915: Also delay first activation for SKL+
>
>In certain platforms we face strange and different issues
>when activating PSR right after a modeset so quickly.
>So we delayed the first activation for the platforms
>where we saw the issues with 'commit d0ac896a477d
>("drm/i915: Delay first PSR activation.")'.
>
>So, let's apply the same delay on first activation
>for SKL+ so we avoid any kind of confusion and
>handle similar implentations in the same way.

Thanks for the quick change Rodrigo!! 

Reviewed-by: Durgadoss R <durgadoss.r@intel.com>

Thanks,
Durga

>
>Cc: Durgadoss R <durgadoss.r@intel.com>
>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>---
> drivers/gpu/drm/i915/intel_psr.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
>diff --git a/drivers/gpu/drm/i915/intel_psr.c b/drivers/gpu/drm/i915/intel_psr.c
>index 465d36b..38ea4d0 100644
>--- a/drivers/gpu/drm/i915/intel_psr.c
>+++ b/drivers/gpu/drm/i915/intel_psr.c
>@@ -420,9 +420,6 @@ void intel_psr_enable(struct intel_dp *intel_dp)
>
> 		/* Enable PSR on the panel */
> 		hsw_psr_enable_sink(intel_dp);
>-
>-		if (INTEL_INFO(dev)->gen >= 9)
>-			intel_psr_activate(intel_dp);
> 	} else {
> 		vlv_psr_setup_vsc(intel_dp);
>
>@@ -441,15 +438,14 @@ void intel_psr_enable(struct intel_dp *intel_dp)
> 	/*
> 	 * FIXME: Activation should happen immediately since this function
> 	 * is just called after pipe is fully trained and enabled.
>-	 * However on every platform we face issues when first activation
>+	 * However on some platforms we face issues when first activation
> 	 * follows a modeset so quickly.
> 	 *     - On VLV/CHV we get bank screen on first activation
> 	 *     - On HSW/BDW we get a recoverable frozen screen until next
> 	 *       exit-activate sequence.
> 	 */
>-	if (INTEL_INFO(dev)->gen < 9)
>-		schedule_delayed_work(&dev_priv->psr.work,
>-				      msecs_to_jiffies(intel_dp->panel_power_cycle_delay * 5));
>+	schedule_delayed_work(&dev_priv->psr.work,
>+			      msecs_to_jiffies(intel_dp->panel_power_cycle_delay * 5));
>
> 	dev_priv->psr.enabled = intel_dp;
> unlock:
>--
>2.4.3

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-11-19  6:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  0:39 [PATCH 0/3] More PSR improvements Rodrigo Vivi
2015-11-19  0:39 ` [PATCH 1/3] drm/i915: Also delay first activation for SKL+ Rodrigo Vivi
2015-11-19  6:07   ` R, Durgadoss [this message]
2015-11-19  8:44   ` Daniel Stone
2015-11-19 18:45     ` Vivi, Rodrigo
2015-11-19  0:39 ` [PATCH 2/3] drm/i915: Remove PSR Perf Counter " Rodrigo Vivi
2015-11-19  6:09   ` R, Durgadoss
2015-11-19  7:45     ` Jindal, Sonika
2015-11-19 18:31       ` Rodrigo Vivi
2015-11-20  6:01         ` Jindal, Sonika
2015-11-20 19:14           ` Vivi, Rodrigo
2015-11-23 22:16             ` [PATCH] " Rodrigo Vivi
2015-11-24 12:33               ` Daniel Vetter
2015-11-19  0:39 ` [PATCH 3/3] drm/i915: Also disable PSR on Sink when disabling it on Source Rodrigo Vivi
2015-11-19  4:26   ` Jindal, Sonika
2015-11-23 22:19     ` [PATCH] " Rodrigo Vivi
2015-11-24  4:40       ` Jindal, Sonika
2015-11-24 12:34         ` 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=4D68720C2E767A4AA6A8796D42C8EB59092B63D9@BGSMSX101.gar.corp.intel.com \
    --to=durgadoss.r@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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 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.