From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm: Add a new connector property for link status
Date: Wed, 26 Oct 2016 10:42:31 +0100 [thread overview]
Message-ID: <20161026094231.GK10167@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20161026055226.bktnqjnejv3s4ira@phenom.ffwll.local>
On Wed, Oct 26, 2016 at 07:52:26AM +0200, Daniel Vetter wrote:
> I'd go further and just always create this as one of the standard
> properties (and always attach it to the connector, like edid), and only
> expose helpers to set the link status to good or bad.
One of the sketches for this idea was that this could serve as the
failure notification path for nonblocking modesets (well modesets in
general since it appears returning the error is not going to happen).
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-26 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 1:16 [PATCH 1/2] drm: Add a new connector property for link status Manasi Navare
2016-10-26 1:16 ` [PATCH 2/2] drm/i915: Set link status property for DP connector Manasi Navare
2016-10-26 1:19 ` [PATCH 1/2] drm: Add a new connector property for link status Manasi Navare
2016-10-26 9:27 ` Chris Wilson
2016-10-26 1:58 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] " Patchwork
2016-10-26 5:52 ` [Intel-gfx] [PATCH 1/2] " Daniel Vetter
2016-10-26 9:42 ` Chris Wilson [this message]
2016-10-26 9:51 ` Jani Nikula
2016-10-26 11:17 ` [Intel-gfx] " Ville Syrjälä
2016-10-26 13:11 ` Chris Wilson
2016-10-26 13:15 ` Ville Syrjälä
2016-10-26 13:29 ` [Intel-gfx] " Chris Wilson
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=20161026094231.GK10167@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.