From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 08/12] drm/i915/psr: Re-org Activate after enable
Date: Fri, 14 Jul 2017 13:07:46 +0300 [thread overview]
Message-ID: <87wp7bjpql.fsf@nikula.org> (raw)
In-Reply-To: <20170712192042.19782-9-rodrigo.vivi@intel.com>
On Wed, 12 Jul 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> Let's move the activation calls together after enable is done.
>
> No real functional change should be expected here. Just an attempt
> to get it clear when we are really activating PSR after enabling it.
>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> Cc: Jim Bride <jim.bride@linux.intel.com>
> Cc: Vathsala NAgaraju <vathsala.nagaraju@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_psr.c | 29 +++++++++++++++--------------
> 1 file changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_psr.c b/drivers/gpu/drm/i915/intel_psr.c
> index 422033a6f9f6..750df0172e8b 100644
> --- a/drivers/gpu/drm/i915/intel_psr.c
> +++ b/drivers/gpu/drm/i915/intel_psr.c
> @@ -543,9 +543,6 @@ void intel_psr_enable(struct intel_dp *intel_dp)
> hsw_psr_enable_sink(intel_dp);
>
> hsw_psr_enable_source(intel_dp);
> -
> - if (INTEL_GEN(dev_priv) >= 9)
> - intel_psr_activate(intel_dp);
> } else {
> vlv_psr_setup_vsc(intel_dp);
>
> @@ -555,20 +552,24 @@ void intel_psr_enable(struct intel_dp *intel_dp)
> vlv_psr_enable_source(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
> - * 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_GEN(dev_priv) < 9)
> + dev_priv->psr.enabled = intel_dp;
> +
> + if (INTEL_GEN(dev_priv) >= 9)
> + intel_psr_activate(intel_dp);
> + else
> + /*
> + * FIXME: Activation should happen immediately since this
> + * function is just called after pipe is fully trained and
> + * enabled.
> + * 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.
> + */
> schedule_delayed_work(&dev_priv->psr.work,
> msecs_to_jiffies(intel_dp->panel_power_cycle_delay * 5));
While technically not required, I'd put curly braces around the branches
here for readability, because the comment is so long.
BR,
Jani.
>
> - dev_priv->psr.enabled = intel_dp;
> unlock:
> mutex_unlock(&dev_priv->psr.lock);
> }
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-07-14 10:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 19:20 [PATCH 00/12] PSR clean-up, new vfuncs and more use of HW tracking Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 01/12] drm/i915/psr: Remove vlv_is_active function Rodrigo Vivi
2017-07-12 19:56 ` Chris Wilson
2017-07-12 21:07 ` Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 02/12] drm/i915/psr: Avoid any PSR stuff on platforms without support Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 03/12] drm/i915/psr: vfunc for disabling source Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 04/12] drm/i915/psr: hsw_psr_activate Rodrigo Vivi
2017-09-07 20:07 ` Pandiyan, Dhinakaran
2017-07-12 19:20 ` [PATCH 05/12] drm/i915/psr: Add activate vfunc Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 06/12] drm/i915/psr: Unify VSC setup functions Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 07/12] drm/i915/psr: Re-create a hsw_psr_enable_source Rodrigo Vivi
2017-07-14 10:06 ` Jani Nikula
2017-07-14 16:35 ` [PATCH 1/2] " Rodrigo Vivi
2017-07-14 16:35 ` [PATCH 2/2] drm/i915/psr: Move hsw_enable_source after enabling sink Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 08/12] drm/i915/psr: Re-org Activate after enable Rodrigo Vivi
2017-07-14 10:07 ` Jani Nikula [this message]
2017-07-14 16:40 ` [PATCH] " Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 09/12] drm/i915/psr: Add setup VSC vfunc Rodrigo Vivi
2017-07-12 19:20 ` [PATCH 10/12] drm/i915/psr: Add enable_sink vfunc Rodrigo Vivi
2017-09-07 20:29 ` Pandiyan, Dhinakaran
2017-07-12 19:20 ` [PATCH 11/12] drm/i915/psr: Add enable_source vfunc Rodrigo Vivi
2017-09-07 20:30 ` Pandiyan, Dhinakaran
2017-07-12 19:20 ` [PATCH 12/12] drm/i915/psr: Use more PSR HW tracking Rodrigo Vivi
2017-07-12 19:37 ` ✗ Fi.CI.BAT: warning for PSR clean-up, new vfuncs and more use of " Patchwork
2017-07-14 16:38 ` ✗ Fi.CI.BAT: failure for PSR clean-up, new vfuncs and more use of HW tracking. (rev3) Patchwork
2017-07-14 16:58 ` ✓ Fi.CI.BAT: success for PSR clean-up, new vfuncs and more use of HW tracking. (rev4) Patchwork
2017-09-07 20:18 ` [PATCH 00/12] PSR clean-up, new vfuncs and more use of HW tracking Pandiyan, Dhinakaran
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=87wp7bjpql.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dhinakaran.pandiyan@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.