public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 09/10] drm/i915: PSR Baytrail: Not available on Pipe C.
Date: Mon, 03 Nov 2014 12:40:50 +0200	[thread overview]
Message-ID: <1415011250.23385.7.camel@intelbox> (raw)
In-Reply-To: <1414521943-3479-10-git-send-email-rodrigo.vivi@intel.com>

On Tue, 2014-10-28 at 11:45 -0700, Rodrigo Vivi wrote:
> Altought VLV/CHV PSR supports per pipe PSR on VLV it isn't available
> on pipe C.
> Cherryview supports on all 3 pipes.
> 
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index ded73ae..b93eb40 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -2370,6 +2370,14 @@ static bool intel_edp_psr_match_conditions(struct intel_dp *intel_dp)
>  		return false;
>  	}
>  
> +	/* Baytrail supports per-pipe PSR configuration, however it is
> +	 * available only on pipes A and B.
> +	 */
> +	if (IS_VALLEYVIEW(dev) && intel_crtc->pipe == PIPE_C) {
> +		DRM_DEBUG_KMS("PSR on BYT isn't available on pipe C.\n");
> +		return false;
> +	}

VLV/BYT has only 2 pipes.

> +
>   out:
>  	dev_priv->psr.source_ok = true;
>  	return true;


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

  reply	other threads:[~2014-11-03 10:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 18:45 [PATCH 00/10] PSR VLV-Braytrail and CHV-Braswell Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 01/10] drm/i915: Add PSR registers for PSR VLV/CHV Rodrigo Vivi
2014-11-06 18:17   ` R, Durgadoss
2014-11-14  0:34     ` Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 02/10] drm/i915: VLV PSR: Status/enabled function Rodrigo Vivi
2014-11-03 12:30   ` Daniel Vetter
2014-11-06 18:25   ` R, Durgadoss
2014-11-07  9:28   ` Daniel Vetter
2014-10-28 18:45 ` [PATCH 03/10] drm/i915: Rename psr_do_exit/psr_exit Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 04/10] drm/i915: PSR VLV/CHV: Introduce setup, enable and disable functions Rodrigo Vivi
2014-11-06 18:32   ` R, Durgadoss
2014-11-14  0:33     ` Rodrigo Vivi
2014-11-14 10:02       ` Daniel Vetter
2014-10-28 18:45 ` [PATCH 05/10] drm/i915: PSR activate function Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 06/10] drm/i915: VLV/CHV PSR Software timer mode control Rodrigo Vivi
2014-11-06 18:39   ` R, Durgadoss
2014-11-14  0:27     ` Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 07/10] drm/i915: VLV/CHV PSR: Increase wait delay time before active PSR Rodrigo Vivi
2014-11-06 18:40   ` R, Durgadoss
2014-11-14  0:30     ` Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 08/10] drm/i915: VLV/CHV PSR debugfs Rodrigo Vivi
2014-11-06 18:45   ` R, Durgadoss
2014-11-14  0:26     ` Rodrigo Vivi
2014-10-28 18:45 ` [PATCH 09/10] drm/i915: PSR Baytrail: Not available on Pipe C Rodrigo Vivi
2014-11-03 10:40   ` Imre Deak [this message]
2014-10-28 18:45 ` [PATCH 10/10] drm/i915: Enable PSR for Baytrail and Braswell Rodrigo Vivi
2014-11-06 18:49   ` R, Durgadoss

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=1415011250.23385.7.camel@intelbox \
    --to=imre.deak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox