public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/8] drm/i915/bxt: Also add bxt_resume_prepare() to the S3/S4 path
Date: Mon, 18 May 2015 22:50:10 +0300	[thread overview]
Message-ID: <1431978610.8397.20.camel@ideak-mobl> (raw)
In-Reply-To: <1431975235-1037-4-git-send-email-damien.lespiau@intel.com>

On Mon, 2015-05-18 at 19:53 +0100, Damien Lespiau wrote:
> Currently bxt_resume_prepare() is only used in the runtime-resume path.
> Add it to the full S3/S4 path as well.
> 
> Cc: Imre Deak <imre.deak@intel.com>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>

Yep, this slipped past the review of "drm/i915/bxt: Add DC9 Trigger
sequence". The fix looks ok:
Reviewed-by: Imre Deak <imre.deak@intel.com>

> ---
>  drivers/gpu/drm/i915/i915_drv.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 5a9399c..7eb751b 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -595,6 +595,7 @@ static int intel_suspend_complete(struct drm_i915_private *dev_priv);
>  static int vlv_resume_prepare(struct drm_i915_private *dev_priv,
>  			      bool rpm_resume);
>  static int skl_resume_prepare(struct drm_i915_private *dev_priv);
> +static int bxt_resume_prepare(struct drm_i915_private *dev_priv);
>  
> 
>  static int i915_drm_suspend(struct drm_device *dev)
> @@ -810,7 +811,9 @@ static int i915_drm_resume_early(struct drm_device *dev)
>  
>  	intel_uncore_early_sanitize(dev, true);
>  
> -	if (IS_SKYLAKE(dev_priv))
> +	if (IS_BROXTON(dev))
> +		ret = bxt_resume_prepare(dev_priv);
> +	else if (IS_SKYLAKE(dev_priv))
>  		ret = skl_resume_prepare(dev_priv);
>  	else if (IS_HASWELL(dev_priv) || IS_BROADWELL(dev_priv))
>  		hsw_disable_pc8(dev_priv);


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

  reply	other threads:[~2015-05-18 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 18:53 [PATCH 0/8] SKL S3, take 2 Damien Lespiau
2015-05-18 18:53 ` [PATCH 1/8] drm/i915: Fix 'suspedn' typo Damien Lespiau
2015-05-18 18:53 ` [PATCH 2/8] drm/i915/vlv/chv: Move resume_prepare() after uncore_early_sanitize() Damien Lespiau
2015-05-18 19:30   ` Imre Deak
2015-05-19 10:44     ` Damien Lespiau
2015-05-18 18:53 ` [PATCH 3/8] drm/i915/bxt: Also add bxt_resume_prepare() to the S3/S4 path Damien Lespiau
2015-05-18 19:50   ` Imre Deak [this message]
2015-05-18 18:53 ` [PATCH 4/8] drm/i915: Extract a common intel_resume_prepare() function Damien Lespiau
2015-05-18 18:53 ` [PATCH 5/8] drm/i915: Add a space after ', ' and don't capitalize mid-sentence Damien Lespiau
2015-05-18 18:53 ` [PATCH 6/8] drm/i915: Kill the dev variable in intel_suspend_complete() Damien Lespiau
2015-05-18 18:53 ` [PATCH 7/8] drm/i915: Store boot CDCLK in dev_priv on DDI platforms Damien Lespiau
2015-05-18 18:53 ` [PATCH 8/8] drm/i915/skl: Deinit/init the display at suspend/resume Damien Lespiau
2015-05-19 21:44   ` shuang.he

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=1431978610.8397.20.camel@ideak-mobl \
    --to=imre.deak@intel.com \
    --cc=damien.lespiau@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