dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 04 Sep 2015 06:51:58 +0000	[thread overview]
Message-ID: <bug-91871-502-lt4wlvVzDX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91871-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1655 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=91871

Jani Nikula <jani.nikula@intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |conselvan2@gmail.com,
                   |                            |intel-gfx-bugs@lists.freede
                   |                            |sktop.org
          Component|General                     |DRM/Intel
           Assignee|dri-devel@lists.freedesktop |intel-gfx-bugs@lists.freede
                   |.org                        |sktop.org
         QA Contact|                            |intel-gfx-bugs@lists.freede
                   |                            |sktop.org

--- Comment #1 from Jani Nikula <jani.nikula@intel.com> ---
To be fair, the same limitation was there before atomic.

Part of the problem is our modeset sequence, which we can't easily backtrack if
the modeset fails at link training phase. Another part is that even if our
modeset sequence supported that, we couldn't just reduce the mode to
accommodate the lower link rate behind userspace's back. (We already pick the
lowest rate that can support the mode; there's no margin to reduce.) We'd have
to involve userspace somehow.

Drivers are free to use the drm dp helpers or use their own hooks for modeset.
I think we should look at this from drm/i915 perspective, at least at first, so
resassigning to DRM/Intel. If we come up with a way to negotiate this with
userspace, that should be a generic solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3240 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

      parent reply	other threads:[~2015-09-04  6:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 19:26 [Bug 91871] link retraining for DP not possible with current design of Atomic modeset framework bugzilla-daemon
2015-09-03 19:28 ` bugzilla-daemon
2015-09-04  6:51 ` bugzilla-daemon [this message]

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-lt4wlvVzDX@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