Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kunal Joshi <kunal1.joshi@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: imre.deak@intel.com, jani.nikula@intel.com,
	Kunal Joshi <kunal1.joshi@intel.com>
Subject: [RFC 0/7] drm/display/dp_tunnel: Add debugfs surface for BWA validation
Date: Mon, 11 May 2026 11:10:21 +0530	[thread overview]
Message-ID: <20260511054028.1310995-1-kunal1.joshi@intel.com> (raw)

Add a debugfs surface to the DRM display DP-tunnel core so IGT
(kms_tbt) can drive deterministic tests of Bandwidth Allocation
Mode on Thunderbolt / USB4 docks without depending on transient
sink behaviour.

Three debugfs files are exposed per tunnel:
  - info       (read-only)  estimated BW, allocated BW, DPRX caps, BWA state
  - bw_alloc_enable (r/w)   toggle BWA on/off
  - bw_limit        (r/w)   inject a BW cap for mode-filtering pressure

Patches 1-3 add the DRM-core helpers, 4-5 wire them into i915,
and 6-7 fix two latent BWA bugs found while testing:
  - allocated_bw not synced after BWA enable (teardown loop)
  - MST children lose dp_tunnel/ after tunnel re-detect

Companion IGT series (kms_tbt) posted separately.

Kunal Joshi (7):
  drm/display/dp_tunnel: Add debugfs interface with info file
  drm/display/dp_tunnel: Add bw_alloc_enable debugfs knob
  drm/display/dp_tunnel: Add bw_limit debugfs cap for BW pressure
    injection
  drm/i915/dp_tunnel: Wire up DP tunnel debugfs from DRM core
  drm/i915/display: Expose DP tunnel debugfs under each connector
  drm/display/dp_tunnel: Sync SW allocated_bw after enabling BW alloc
  drm/i915/dp_tunnel: Re-attach dp_tunnel debugfs to MST children on
    re-detect

 drivers/gpu/drm/display/drm_dp_tunnel.c       | 402 +++++++++++++++++-
 .../drm/i915/display/intel_display_debugfs.c  |  22 +
 drivers/gpu/drm/i915/display/intel_dp.c       |  11 +
 drivers/gpu/drm/i915/display/intel_dp_mst.c   |  11 +
 .../gpu/drm/i915/display/intel_dp_tunnel.c    |  50 ++-
 include/drm/display/drm_dp_tunnel.h           |  17 +
 6 files changed, 511 insertions(+), 2 deletions(-)

-- 
2.25.1


             reply	other threads:[~2026-05-11  5:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  5:40 Kunal Joshi [this message]
2026-05-11  5:40 ` [RFC 1/7] drm/display/dp_tunnel: Add debugfs interface with info file Kunal Joshi
2026-05-11  5:40 ` [RFC 2/7] drm/display/dp_tunnel: Add bw_alloc_enable debugfs knob Kunal Joshi
2026-05-11  5:40 ` [RFC 3/7] drm/display/dp_tunnel: Add bw_limit debugfs cap for BW pressure injection Kunal Joshi
2026-05-11  5:40 ` [RFC 4/7] drm/i915/dp_tunnel: Wire up DP tunnel debugfs from DRM core Kunal Joshi
2026-05-11  5:40 ` [RFC 5/7] drm/i915/display: Expose DP tunnel debugfs under each connector Kunal Joshi
2026-05-11  5:40 ` [RFC 6/7] drm/display/dp_tunnel: Sync SW allocated_bw after enabling BW alloc Kunal Joshi
2026-05-11  5:40 ` [RFC 7/7] drm/i915/dp_tunnel: Re-attach dp_tunnel debugfs to MST children on re-detect Kunal Joshi
2026-05-11 14:54 ` ✓ i915.CI.BAT: success for drm/display/dp_tunnel: Add debugfs surface for BWA validation Patchwork
2026-05-11 20:10 ` ✗ i915.CI.Full: failure " Patchwork

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=20260511054028.1310995-1-kunal1.joshi@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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