From: Imre Deak <imre.deak@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: don't disable DP port after a failed link training
Date: Thu, 16 Jan 2014 19:05:40 +0200 [thread overview]
Message-ID: <1389891940.1153.4.camel@intelbox> (raw)
In-Reply-To: <20140116165814.GA4864@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 941 bytes --]
On Thu, 2014-01-16 at 16:58 +0000, Chris Wilson wrote:
> On Thu, Jan 16, 2014 at 06:35:58PM +0200, Imre Deak wrote:
> > The driver shouldn't disable the DP port itself, but let userspace do it
> > through a modeset. See the previous patch for the reasoning.
>
> Eh, this occurs not just during link detection, but also during
> intel_enable_dp, so this comment does not hold. The biggest
> issue of this function is that it can fail but never propagates
> that failure, which itself breaks the users and API expectations,
> as neither the driver or userspace is aware that it is required to
> takeaction.
Right, I haven't thought about this and the commit message is incorrect.
So in the end with proper error handling it's gonna be the kernel that
disables the port along with the rest of the pipe.
I agree with danvet, that we could still have this before a final
solution. (with a fixed commit message).
--Imre
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-01-16 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 16:35 [PATCH 1/2] drm/i915: don't disable the DP port if the link is lost Imre Deak
2014-01-16 16:35 ` [PATCH 2/2] drm/i915: don't disable DP port after a failed link training Imre Deak
2014-01-16 16:58 ` Chris Wilson
2014-01-16 17:01 ` Daniel Vetter
2014-01-16 20:39 ` Chris Wilson
2014-01-16 21:27 ` Daniel Vetter
2014-01-16 17:05 ` Imre Deak [this message]
2014-01-17 13:46 ` [PATCH] " Imre Deak
2014-01-17 13:58 ` Chris Wilson
2014-01-17 17:13 ` Daniel Vetter
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=1389891940.1153.4.camel@intelbox \
--to=imre.deak@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox