From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, airlied@gmail.com,
daniel@ffwll.ch, stable@vger.kernel.org, tprevite@gmail.com
Subject: Re: [PATCH] drm/i915/dp: only use training pattern 3 on platforms that support it
Date: Wed, 29 Oct 2014 13:09:12 +0200 [thread overview]
Message-ID: <20141029110912.GH4284@intel.com> (raw)
In-Reply-To: <1414573406-17071-1-git-send-email-jani.nikula@intel.com>
On Wed, Oct 29, 2014 at 11:03:26AM +0200, Jani Nikula wrote:
> Ivybridge + 30" monitor prints a drm error on every modeset, since IVB
> doesn't support DP3 we should even bother trying to use it.
>
> This regression has been introduced in
>
> commit 06ea66b6bb445043dc25a9626254d5c130093199
> Author: Todd Previte <tprevite@gmail.com>
> Date: Mon Jan 20 10:19:39 2014 -0700
>
> drm/i915: Enable 5.4Ghz (HBR2) link rate for Displayport 1.2-capable
> devices
>
> Reported-by: Dave Airlie <airlied@redhat.com>
> Reference: http://mid.gmane.org/1414566170-9868-1-git-send-email-airlied@gmail.com
> Cc: Todd Previte <tprevite@gmail.com>
> Cc: stable@vger.kernel.org (3.15+)
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 82e47dafe293..47e9d71c14a3 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -3945,9 +3945,10 @@ intel_dp_get_dpcd(struct intel_dp *intel_dp)
> }
> }
>
> - /* Training Pattern 3 support */
> + /* Training Pattern 3 support, both source and sink */
> if (intel_dp->dpcd[DP_DPCD_REV] >= 0x12 &&
> - intel_dp->dpcd[DP_MAX_LANE_COUNT] & DP_TPS3_SUPPORTED) {
> + intel_dp->dpcd[DP_MAX_LANE_COUNT] & DP_TPS3_SUPPORTED &&
> + (IS_HASWELL(dev_priv) || INTEL_INFO(dev_priv)->gen >= 8)) {
Yep that looks better. Additonally we could drop the
'link_bw == DP_LINK_BW_5_4' check from intel_dp_complete_link_train()
and just rely on use_tps3 since pattern 3 is mandatory for HBR2
capable sinks, and so they really should advertise DP_TPS3_SUPPORTED.
But on the other hand I don't see any harm in keeping the current
logic there.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> intel_dp->use_tps3 = true;
> DRM_DEBUG_KMS("Displayport TPS3 supported\n");
> } else
> --
> 2.1.1
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2014-10-29 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 9:03 [PATCH] drm/i915/dp: only use training pattern 3 on platforms that support it Jani Nikula
2014-10-29 11:09 ` Ville Syrjälä [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=20141029110912.GH4284@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=stable@vger.kernel.org \
--cc=tprevite@gmail.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