From: Xiao Lu <xiaolu.xie@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, jani.nikula@linux.intel.com,
rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, Xiao Lu <xiaolu.xie@intel.com>
Subject: [PATCH v3 0/2] drm/i915/dp: Fix MST PBN accounting
Date: Thu, 24 Sep 2026 17:43:14 +0800 [thread overview]
Message-ID: <20260924094316.822211-1-xiaolu.xie@intel.com> (raw)
In-Reply-To: <20260922092647.2263962-1-xiaolu.xie@intel.com>
Use the raw video PBN in ALLOCATE_PAYLOAD requests while keeping the
TU-aligned PBN for source hardware programming. Also track the PBN
actually allocated by downstream branches and use it in later bandwidth
checks.
The series was tested with a three-display PS8650 MST daisy chain.
Changes in v3:
- Preserve allocated_pbn when recalculating an active payload; clear it
only when releasing the payload.
- Patch 1 is unchanged.
Xiao Lu (2):
drm/i915/dp: fix PBN in ALLOCATE_PAYLOAD request to use actual video
bandwidth
drm/dp_mst: Track allocated_pbn from ALLOCATE_PAYLOAD down-reply
drivers/gpu/drm/display/drm_dp_mst_topology.c | 17 +++++++---
drivers/gpu/drm/i915/display/intel_dp_mst.c | 33 ++++++++++++++-----
include/drm/display/drm_dp_mst_helper.h | 10 ++++++
3 files changed, 46 insertions(+), 14 deletions(-)
--
2.43.0
next parent reply other threads:[~2026-09-24 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260922092647.2263962-1-xiaolu.xie@intel.com>
2026-09-24 9:43 ` Xiao Lu [this message]
2026-09-24 9:43 ` [PATCH v3 1/2] drm/i915/dp: fix PBN in ALLOCATE_PAYLOAD request to use actual video bandwidth Xiao Lu
2026-09-24 9:43 ` [PATCH v3 2/2] drm/dp_mst: Track allocated_pbn from ALLOCATE_PAYLOAD down-reply Xiao Lu
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=20260924094316.822211-1-xiaolu.xie@intel.com \
--to=xiaolu.xie@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®