From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1767648301==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 27C7A6EB5D for ; Thu, 3 Sep 2015 23:51:59 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1767648301== Content-Type: multipart/alternative; boundary="1441349518.0dB00b5B1.18150"; charset="UTF-8" --1441349518.0dB00b5B1.18150 Date: Fri, 4 Sep 2015 06:51:58 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=91871 Jani Nikula 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 --- 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. --1441349518.0dB00b5B1.18150 Date: Fri, 4 Sep 2015 06:51:58 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" changed bug 91871
What Removed Added
CC   conselvan2@gmail.com, intel-gfx-bugs@lists.freedesktop.org
Component General DRM/Intel
Assignee dri-devel@lists.freedesktop.org intel-gfx-bugs@lists.freedesktop.org
QA Contact   intel-gfx-bugs@lists.freedesktop.org

Comment # 1 on bug 91871 from
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.
--1441349518.0dB00b5B1.18150-- --===============1767648301== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1767648301==--