From: Jani Nikula <jani.nikula@linux.intel.com>
To: Xiao Lu <xiaolu.xie@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tvrtko.ursulin@linux.intel.com,
lyude@redhat.com, David.Francis@amd.com,
Xiao Lu <xiaolu.xie@intel.com>
Subject: Re: [PATCH v2 0/2] drm/dp/mst: fix MST payload PBN accounting
Date: Tue, 22 Sep 2026 12:35:16 +0300 [thread overview]
Message-ID: <29cbe9a712812effa11c3e8f9c830a0fda9eb7ed@intel.com> (raw)
In-Reply-To: <20260922092647.2263962-1-xiaolu.xie@intel.com>
On Tue, 22 Sep 2026, Xiao Lu <xiaolu.xie@intel.com> wrote:
> v2: Send the two related patches together as a series, as requested
> by Jani. No code changes from v1.
I bounced this series to intel-xe@lists.freedesktop.org as well, since
the display code is shared with xe, and we want to run xe CI on it too.
MAINTAINERS should indicate this. For future reference, please send
Intel display patches to both intel-xe and intel-gfx mailing lists.
Thanks,
Jani.
>
> This series fixes two related issues in MST payload bandwidth
> accounting that together caused 4K@60Hz to fail alongside two
> 1080p@60Hz displays in a 3-display MST daisy-chain topology
> (PS8650 hub -> ViewSonic VP2468 x2 -> Lenovo Pro 27UD-10).
>
> Patch 1 fixes the PBN value passed in the ALLOCATE_PAYLOAD sideband
> request. The driver was using a TU-aligned PBN (e.g. 537) instead of
> the actual video stream bandwidth (e.g. 496 for 1080p@59.94Hz),
> inflating the requested PBN and causing -ENOSPC failures for
> configurations that should fit within the available link bandwidth.
>
> Patch 2 tracks the allocated_pbn returned in the ALLOCATE_PAYLOAD
> reply, and uses it alongside @pbn for bandwidth limit checks. This
> ensures that any per-hop capacity constraints from intermediate MST
> branches are correctly reflected in the source-side bandwidth check.
>
> 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 reply
>
> drivers/gpu/drm/display/drm_dp_mst_topology.c | 24 ++++++++++++++----
> drivers/gpu/drm/i915/display/intel_dp_mst.c | 24 +++++++++++------
> include/drm/display/drm_dp_mst_helper.h | 10 +++++++
> 3 files changed, 46 insertions(+), 12 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-09-22 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 9:26 [PATCH v2 0/2] drm/dp/mst: fix MST payload PBN accounting Xiao Lu
2026-09-22 9:26 ` [PATCH v2 1/2] drm/i915/dp: fix PBN in ALLOCATE_PAYLOAD request to use actual video bandwidth Xiao Lu
2026-09-22 9:35 ` sashiko-bot
2026-09-22 9:26 ` [PATCH v2 2/2] drm/dp_mst: Track allocated_pbn from ALLOCATE_PAYLOAD down-reply Xiao Lu
2026-09-22 9:41 ` sashiko-bot
2026-09-22 9:35 ` Jani Nikula [this message]
2026-09-24 9:43 ` [PATCH v3 0/2] drm/i915/dp: Fix MST PBN accounting Xiao Lu
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:51 ` sashiko-bot
2026-09-24 9:43 ` [PATCH v3 2/2] drm/dp_mst: Track allocated_pbn from ALLOCATE_PAYLOAD down-reply Xiao Lu
2026-09-24 9:57 ` sashiko-bot
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=29cbe9a712812effa11c3e8f9c830a0fda9eb7ed@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=David.Francis@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lyude@redhat.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=xiaolu.xie@intel.com \
/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