All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak <deepak.s@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Don't bypass LRC on CHV
Date: Mon, 5 Oct 2015 15:55:54 +0530	[thread overview]
Message-ID: <56125032.2090005@linux.intel.com> (raw)
In-Reply-To: <1441724745-10515-1-git-send-email-ville.syrjala@linux.intel.com>



On Tuesday 08 September 2015 08:35 PM, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The docs are unclear as usual, so it's not clear whether LRC should be
> bypassed, performed normally or GRC code should be used as the LRC code.
> Some old docs stated that LRC bypass ought to be used, more recent ones
> no longer say that. Some docs indicated that we could use GRC as the LRC
> code on CHV, but the BIOS doesn't do that, so let's not do it either.
>
> Besides to enable LRC bypass properly, I believe we should set the bit
> already before deasserting cmnreset.

Can we add a Log to indicate what BIOS is configuring? I think it helps in debugging?


Change looks fine.
Reviewed-by: Deepak S<deepak.s@linux.intel.com>


> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/intel_dp.c   | 5 -----
>   drivers/gpu/drm/i915/intel_hdmi.c | 5 -----
>   2 files changed, 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 45ab25e..825d5ab 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -3416,11 +3416,6 @@ static uint32_t chv_signal_levels(struct intel_dp *intel_dp)
>   		vlv_dpio_write(dev_priv, pipe, VLV_PCS23_DW10(ch), val);
>   	}
>   
> -	/* LRC Bypass */
> -	val = vlv_dpio_read(dev_priv, pipe, CHV_CMN_DW30);
> -	val |= DPIO_LRC_BYPASS;
> -	vlv_dpio_write(dev_priv, pipe, CHV_CMN_DW30, val);
> -
>   	mutex_unlock(&dev_priv->sb_lock);
>   
>   	return 0;
> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
> index feb31d8..9d7923d 100644
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1941,11 +1941,6 @@ static void chv_hdmi_pre_enable(struct intel_encoder *encoder)
>   	val |= DPIO_PCS_SWING_CALC_TX0_TX2 | DPIO_PCS_SWING_CALC_TX1_TX3;
>   	vlv_dpio_write(dev_priv, pipe, VLV_PCS23_DW10(ch), val);
>   
> -	/* LRC Bypass */
> -	val = vlv_dpio_read(dev_priv, pipe, CHV_CMN_DW30);
> -	val |= DPIO_LRC_BYPASS;
> -	vlv_dpio_write(dev_priv, pipe, CHV_CMN_DW30, val);
> -
>   	mutex_unlock(&dev_priv->sb_lock);
>   
>   	intel_hdmi->set_infoframes(&encoder->base,

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

      parent reply	other threads:[~2015-10-05 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 15:05 [PATCH 1/2] drm/i915: Don't bypass LRC on CHV ville.syrjala
2015-09-08 15:05 ` [PATCH 2/2] drm/i915: Skip CHV PHY asserts until PHY has been fully reset ville.syrjala
2015-10-05 10:27   ` Deepak
2015-10-06  8:30     ` Daniel Vetter
2015-10-05 10:25 ` Deepak [this message]

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=56125032.2090005@linux.intel.com \
    --to=deepak.s@linux.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 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.