From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91871] link retraining for DP not possible with current design of Atomic modeset framework
Date: Thu, 03 Sep 2015 19:26:00 +0000 [thread overview]
Message-ID: <bug-91871-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1234 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91871
Bug ID: 91871
Summary: link retraining for DP not possible with current
design of Atomic modeset framework
Product: DRI
Version: XOrg git
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: General
Assignee: dri-devel@lists.freedesktop.org
Reporter: sivakumar.thulasimani@intel.com
DP spec requires Link training from highest link rate supported by panel to
lowest link rate supported by panel.
It is not possible to implement this in the current atomic modeset logic since
it splits modeset into two half atomic_check and atomic_commit, where it is
expected all values to be calculated in atomic_check and programmed in
atomic_commit.
link training being a negotiation phase of DP modeset it is not possible to
predict if a training at certain link rate will succeed or not. if it does fail
it will require us to disable, calculate new values and enable pll. this is not
possible in current DRM Atomic modeset framework.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2477 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-09-03 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:26 bugzilla-daemon [this message]
2015-09-03 19:28 ` [Bug 91871] link retraining for DP not possible with current design of Atomic modeset framework bugzilla-daemon
2015-09-04 6:51 ` bugzilla-daemon
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=bug-91871-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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