From: Lyude Paul <lyude@redhat.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: "DRM maintainer tools announcements, discussion,
and development" <dim-tools@lists.freedesktop.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Sean Paul <sean@poorly.run>
Subject: [PULL] topic/mst-bw-check-fixes-for-airlied
Date: Thu, 12 Mar 2020 19:59:31 -0400 [thread overview]
Message-ID: <bf16ee577567beed91c86b7d9cda3ec2e8c50a71.camel@redhat.com> (raw)
topic/mst-bw-check-fixes-for-airlied-2020-03-12-2:
UAPI Changes: None
Cross-subsystem Changes: None
Core Changes: Fixed regressions introduced by commit cd82d82cbc04
("drm/dp_mst: Add branch bandwidth validation to MST atomic check"),
which would cause us to:
* Calculate the available bandwidth on an MST topology incorrectly, and
as a result reject most display configurations that would try to enable
more then one sink on a topology
* Occasionally expose MST connectors to userspace before finishing
probing their PBN capabilities, resulting in us rejecting display
configurations because we assumed briefly that no bandwidth was
available
Driver Changes: None
The following changes since commit e3c3b6e66da1caeb39a504b03ddcdd3693e45254:
Merge tag 'exynos-drm-fixes-for-v5.6-rc5-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-fixes (2020-03-12 11:02:52 +1000)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-misc tags/topic/mst-bw-check-fixes-for-airlied-2020-03-12-2
for you to fetch changes up to 047d4cd2067b028e7bca906c5ce20f4c89b65386:
drm/dp_mst: Rewrite and fix bandwidth limit checks (2020-03-12 19:07:49 -0400)
----------------------------------------------------------------
UAPI Changes: None
Cross-subsystem Changes: None
Core Changes: Fixed regressions introduced by commit cd82d82cbc04
("drm/dp_mst: Add branch bandwidth validation to MST atomic check"),
which would cause us to:
* Calculate the available bandwidth on an MST topology incorrectly, and
as a result reject most display configurations that would try to enable
more then one sink on a topology
* Occasionally expose MST connectors to userspace before finishing
probing their PBN capabilities, resulting in us rejecting display
configurations because we assumed briefly that no bandwidth was
available
Driver Changes: None
----------------------------------------------------------------
Lyude Paul (4):
drm/dp_mst: Rename drm_dp_mst_is_dp_mst_end_device() to be less redundant
drm/dp_mst: Use full_pbn instead of available_pbn for bandwidth checks
drm/dp_mst: Reprobe path resources in CSN handler
drm/dp_mst: Rewrite and fix bandwidth limit checks
drivers/gpu/drm/drm_dp_mst_topology.c | 184 +++++++++++++++++++++++-----------
include/drm/drm_dp_mst_helper.h | 4 +-
2 files changed, 128 insertions(+), 60 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2020-03-12 23:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bf16ee577567beed91c86b7d9cda3ec2e8c50a71.camel@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
/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