public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Sonika Jindal <sonika.jindal@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/i915/skl: Read sink supported rates from edp panel
Date: Wed, 4 Mar 2015 12:00:00 +0200	[thread overview]
Message-ID: <20150304100000.GL11371@intel.com> (raw)
In-Reply-To: <1424497333-1393-3-git-send-email-sonika.jindal@intel.com>

On Sat, Feb 21, 2015 at 11:12:11AM +0530, Sonika Jindal wrote:
> v2: Using DP_SUPPORTED_LINK_RATES macro for supported_rates array (Satheesh).
> v3: Reading dpcd's supported link rates tables based upon edp version in the
> same patch.
> v4: Move version check under is_edp (Satheesh)
> v5: Using le16 for rates, some naming, and removing nested if block (Ville)
> v6: Correctly using DP_MAX_SUPPORTED_RATES and removing DP_SUPPORTED_LINK_RATES
> (Ville)
> v7: Incorrectly removed DP_SUPPORTED_LINK_RATES in v6, re-adding it
> 
> Signed-off-by: Sonika Jindal <sonika.jindal@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dp.c  |   38 ++++++++++++++++++++++++++++++++++++++
>  drivers/gpu/drm/i915/intel_drv.h |    1 +
>  2 files changed, 39 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 42ac99f..72deac6 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -1116,6 +1116,33 @@ hsw_dp_set_ddi_pll_sel(struct intel_crtc_state *pipe_config, int link_bw)
>  	}
>  }
>  
> +static int
> +intel_read_sink_rates(struct intel_dp *intel_dp, uint32_t *sink_rates)
> +{
> +	struct drm_device *dev = intel_dp_to_dev(intel_dp);
> +	int i = 0;
> +	uint16_t val;
> +
> +	if (INTEL_INFO(dev)->gen >= 9 && intel_dp->supported_rates[0]) {
> +		/*
> +		 * Receiver supports only main-link rate selection by
> +		 * link rate table method, so read link rates from
> +		 * supported_link_rates
> +		 */
> +		for (i = 0; i < DP_MAX_SUPPORTED_RATES; ++i) {
> +			val = le16_to_cpu(intel_dp->supported_rates[i]);
> +			if (val == 0)
> +				break;
> +
> +			sink_rates[i] = val * 200;
> +		}
> +
> +		if (i <= 0)
> +			DRM_ERROR("No rates in SUPPORTED_LINK_RATES");
> +	}
> +	return i;
> +}
> +
>  static void
>  intel_dp_set_clock(struct intel_encoder *encoder,
>  		   struct intel_crtc_state *pipe_config, int link_bw)
> @@ -3592,6 +3619,7 @@ intel_dp_get_dpcd(struct intel_dp *intel_dp)
>  	struct intel_digital_port *dig_port = dp_to_dig_port(intel_dp);
>  	struct drm_device *dev = dig_port->base.base.dev;
>  	struct drm_i915_private *dev_priv = dev->dev_private;
> +	uint8_t rev;
>  
>  	if (intel_dp_dpcd_read_wake(&intel_dp->aux, 0x000, intel_dp->dpcd,
>  				    sizeof(intel_dp->dpcd)) < 0)
> @@ -3623,6 +3651,16 @@ intel_dp_get_dpcd(struct intel_dp *intel_dp)
>  	} else
>  		intel_dp->use_tps3 = false;
>  
> +	/* Intermediate frequency support */
> +	if (is_edp(intel_dp) &&
> +	    (intel_dp->dpcd[DP_EDP_CONFIGURATION_CAP] &	DP_DPCD_DISPLAY_CONTROL_CAPABLE) &&
> +	    intel_dp_dpcd_read_wake(&intel_dp->aux, DP_EDP_DPCD_REV, &rev, 1) &&

intel_dp_dpcd_read_wake() == 1
would be the right thing to check I think.

With that fixed:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> +	    (rev >= 0x03)) { /* eDp v1.4 or higher */
> +		intel_dp_dpcd_read_wake(&intel_dp->aux,
> +				DP_SUPPORTED_LINK_RATES,
> +				intel_dp->supported_rates,
> +				sizeof(intel_dp->supported_rates));
> +	}
>  	if (!(intel_dp->dpcd[DP_DOWNSTREAMPORT_PRESENT] &
>  	      DP_DWN_STRM_PORT_PRESENT))
>  		return true; /* native DP sink */
> diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> index 6832eb8..24e5411 100644
> --- a/drivers/gpu/drm/i915/intel_drv.h
> +++ b/drivers/gpu/drm/i915/intel_drv.h
> @@ -602,6 +602,7 @@ struct intel_dp {
>  	uint8_t dpcd[DP_RECEIVER_CAP_SIZE];
>  	uint8_t psr_dpcd[EDP_PSR_RECEIVER_CAP_SIZE];
>  	uint8_t downstream_ports[DP_MAX_DOWNSTREAM_PORTS];
> +	__le16 supported_rates[DP_MAX_SUPPORTED_RATES];
>  	struct drm_dp_aux aux;
>  	uint8_t train_set[4];
>  	int panel_power_up_delay;
> -- 
> 1.7.10.4

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-04 10:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  5:42 [PATCH 0/4] drm/i915/skl: Support for edp1.4 intermediate frequencies Sonika Jindal
2015-02-21  5:42 ` [PATCH 1/4] drm: Adding edp1.4 specific dpcd macros Sonika Jindal
2015-02-21  5:42 ` [PATCH 2/4] drm/i915/skl: Read sink supported rates from edp panel Sonika Jindal
2015-03-04 10:00   ` Ville Syrjälä [this message]
2015-03-05  4:33     ` [PATCH] " Sonika Jindal
2015-03-05 13:11       ` shuang.he
2015-02-21  5:42 ` [PATCH 3/4] drm/i915/skl: Add support for edp 1.4 intermediate frequencies Sonika Jindal
2015-03-04 11:24   ` Ville Syrjälä
2015-03-05  4:32     ` [PATCH] " Sonika Jindal
2015-03-05 12:02       ` Daniel Vetter
2015-02-21  5:42 ` [PATCH 4/4] drm/i915/skl: Program PLL for edp1.4 " Sonika Jindal
2015-02-21  8:23   ` shuang.he
2015-03-04 11:25   ` Ville Syrjälä
2015-02-27  6:08 ` [PATCH 0/4] drm/i915/skl: Support " Jindal, Sonika

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=20150304100000.GL11371@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sonika.jindal@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