From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
stable@vger.kernel.org, Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: tune down the fast link training vs boot fail
Date: Tue, 13 Dec 2016 22:23:05 +0200 [thread overview]
Message-ID: <20161213202305.GQ31595@intel.com> (raw)
In-Reply-To: <20161213195414.28923-1-daniel.vetter@ffwll.ch>
On Tue, Dec 13, 2016 at 08:54:14PM +0100, Daniel Vetter wrote:
> It's been unfixed since a while and no one is immediately working on
> this. And we have the FIXME already. And now also a task in the DP
> team's backlog.
>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: stable@vger.kernel.org
> Cc: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> References: https://lists.freedesktop.org/archives/intel-gfx/2016-July/101951.html
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> Hi Linus,
>
> Feel free to apply directly in case it annoys too much and you don't
> want to wait for your presents ;-)
>
> Cheers, Daniel
> ---
> drivers/gpu/drm/i915/intel_dp.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index db75bb924e48..6e875d42642a 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4014,8 +4014,8 @@ intel_dp_check_link_status(struct intel_dp *intel_dp)
> return;
>
> /* FIXME: we need to synchronize this sort of stuff with hardware
> - * readout */
> - if (WARN_ON_ONCE(!intel_dp->lane_count))
> + * readout. Currently fast link training doesn't work on boot-up. */
s/fast link training/link retraining/ is what I'd put there.
I'm a bit sad to hide it but doesn't look like the proper solution is
going to happen any time soon.
Acked-by: Ville Syrj�l� <ville.syrjala@linux.intel.com>
> + if (!intel_dp->lane_count)
> return;
>
> /* if link training is requested we should perform it always */
> --
> 2.11.0
--
Ville Syrj�l�
Intel OTC
next prev parent reply other threads:[~2016-12-13 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 19:54 [PATCH] drm/i915: tune down the fast link training vs boot fail Daniel Vetter
2016-12-13 19:56 ` Linus Torvalds
2016-12-13 20:23 ` Ville Syrjälä [this message]
2016-12-13 22:37 ` Daniel Vetter
2016-12-14 14:56 ` [Intel-gfx] " Jani Nikula
2016-12-15 7:48 ` Daniel Vetter
2016-12-15 9:10 ` Jani Nikula
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=20161213202305.GQ31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).