From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: don't try using training pattern 3 on pre-haswell
Date: Wed, 29 Oct 2014 11:07:32 +0200 [thread overview]
Message-ID: <87lhnzjlbf.fsf@intel.com> (raw)
In-Reply-To: <20141029084058.GF4284@intel.com>
On Wed, 29 Oct 2014, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Oct 29, 2014 at 10:23:50AM +0200, Jani Nikula wrote:
>> On Wed, 29 Oct 2014, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>> > On Wed, Oct 29, 2014 at 05:02:50PM +1000, Dave Airlie wrote:
>> >> From: Dave Airlie <airlied@redhat.com>
>> >>
>> >> Ivybridge + 30" monitor prints a drm error on every modeset, since
>> >> IVB doesn't support DP3 we should even bother trying to use it.
>> >>
>> >> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> (on irc)
>> >> Signed-off-by: Dave Airlie <airlied@redhat.com>
>> >> ---
>> >> drivers/gpu/drm/i915/intel_dp.c | 4 +++-
>> >> 1 file changed, 3 insertions(+), 1 deletion(-)
>> >>
>> >> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> >> index f6a3fdd..87cfb92 100644
>> >> --- a/drivers/gpu/drm/i915/intel_dp.c
>> >> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> >> @@ -3547,13 +3547,15 @@ intel_dp_start_link_train(struct intel_dp *intel_dp)
>> >> void
>> >> intel_dp_complete_link_train(struct intel_dp *intel_dp)
>> >> {
>> >> + struct drm_encoder *encoder = &dp_to_dig_port(intel_dp)->base.base;
>> >> + struct drm_device *dev = encoder->dev;
>> >> bool channel_eq = false;
>> >> int tries, cr_tries;
>> >> uint32_t DP = intel_dp->DP;
>> >> uint32_t training_pattern = DP_TRAINING_PATTERN_2;
>> >>
>> >> /* Training Pattern 3 for HBR2 ot 1.2 devices that support it*/
>> >> - if (intel_dp->link_bw == DP_LINK_BW_5_4 || intel_dp->use_tps3)
>> >> + if ((intel_dp->link_bw == DP_LINK_BW_5_4 || intel_dp->use_tps3) && !HAS_DDI(dev))
>> >
>> > CHV has pattern 3.
>>
>> Is "supports tps3" the same set of platforms as "supports 5.4 Gbps"? We
>> should abstract the check from intel_dp_max_link_bw.
>
> Not quite. HSW-ULX supports pattern 3 even though it doesn't do 5.4 Gbps.
How about [1] instead? I forgot --in-reply-to, sorry.
BR,
Jani.
[1] http://mid.gmane.org/1414573406-17071-1-git-send-email-jani.nikula@intel.com
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-10-29 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 7:02 [PATCH] drm/i915: don't try using training pattern 3 on pre-haswell Dave Airlie
2014-10-29 7:40 ` [Intel-gfx] " Daniel Vetter
2014-10-29 8:15 ` Ville Syrjälä
2014-10-29 8:22 ` [Intel-gfx] " Ville Syrjälä
2014-10-29 8:23 ` Jani Nikula
2014-10-29 8:40 ` [Intel-gfx] " Ville Syrjälä
2014-10-29 9:07 ` Jani Nikula [this message]
2014-10-30 21:16 ` Jesse Barnes
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=87lhnzjlbf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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