From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Deak, Imre" <imre.deak@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Manna, Animesh" <animesh.manna@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Murthy, Arun R" <arun.r.murthy@intel.com>
Subject: Re: [PATCH v7 0/3] Panel Replay BW optimization
Date: Fri, 13 Mar 2026 07:57:43 +0000 [thread overview]
Message-ID: <cbd5a8b6e612da35d03440b18f81138f3fa48349.camel@intel.com> (raw)
In-Reply-To: <abPCARYnIAdJHuxf@ideak-desk.lan>
On Fri, 2026-03-13 at 09:51 +0200, Imre Deak wrote:
> On Fri, Mar 13, 2026 at 07:20:24AM +0200, Hogander, Jouni wrote:
> > On Thu, 2026-03-12 at 17:18 +0200, Imre Deak wrote:
> > > On Thu, Mar 12, 2026 at 10:05:35AM +0200, Hogander, Jouni wrote:
> > > > On Thu, 2026-03-12 at 10:30 +0530, Animesh Manna wrote:
> > > > > Unused bandwidth can be used by external display agents for
> > > > > Panel
> > > > > Replay
> > > > > enabled DP panel during idleness with link on. This patch
> > > > > series
> > > > > enabling the same.
> > > >
> > > > Generic comment on this patch set. Maybe we should add one more
> > > > patch
> > > > with "Fixes" tag:
> > > >
> > > > Fixes: e60cff453b82 ("drm/i915/dp: Enable DP tunnel BW
> > > > allocation
> > > > mode")
> > > > Cc: Imre Deak <imre.deak@intel.com>
> > > > Cc: <stable@vger.kernel.org> # v6.9+
> > >
> > > Why? As I understand the Panel Replay BW optimization on a DP
> > > tunneled
> > > link is an _optional_ feature, whereby the free BW can be used by
> > > the
> > > Thunderbolt protocol for other purposes than for the given
> > > display
> > > stream for which Panel Replay is enabled. IOW, it looks to me a
> > > valid
> > > configuration to enable Panel Replay on a DP tunneled link
> > > without
> > > enabling the Panel Replay BW optimization on it.
> >
> > My original comment was about DP spec:
> >
> > "
> > The DP Source device may optionally enable PR optimization with DP
> > tunneling. The device
> > shall query the Tunneling Bridge’s PR tunneling optimization
> > capability
> > by way of the
> > Panel_Replay_Tunneling_Optimization_Support bit in the
> > DP_TUNNELING_CAPABILITIES
> > register (DPCD E000Dh[6]), and then enable PR only when the
> > Tunneling
> > Bridge is capable.
> > "
> >
> > That sounds like PR can be enabled only when Panel Replay Tunneling
> > Optimization is supported?
>
> The Standard refers to the _optimization_ of the Panel Replay
> functionality over a tunnel. This optimization can be either enabled
> by
> the source when enabling the Panel Replay functionality over a tunnel
> or
> the optimization can be left disabled by the source when enabling the
> Panel Replay functionality over a tunnel.
>
> The optimization means that the BW of the stream, not otherwise used
> for
> transferring active pixels or other data (i.e. dummy pixels) can be
> used
> by the Thunderbolt protocol to transfer non-display traffic. If the
> Panel Replay is enabled over a tunnel without this optimization, then
> the Thunderbolt protocol is not allowed to use this BW for other
> purposes (i.e. it just transfers all the display traffic it receives
> from the source as-is).
Ok, then my original comment wasn't valid at all.
Sorry Animesh for steering into wrong direction here. Based on comment
from Imre I think you can drop patch 3.
BR,
Jouni Högander
>
> >
> > BR,
> > Jouni Högander
> >
> > >
> > > > This patch would just add:
> > > >
> > > > if (intel_dp_tunnel_bw_alloc_is_enabled(intel_dp)) {
> > > > drm_dbg_kms(display->drm,
> > > > "Panel Replay is disabled as DP tunneling
> > > > enabled\n");
> > > > return false;
> > > > }
> > > >
> > > > into _panel_replay_compute_config. this could be first patch in
> > > > your
> > > > set. What do you think?
> > > >
> > > > BR,
> > > > Jouni Högander
> > > >
> > > > >
> > > > > Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> > > > >
> > > > > Animesh Manna (3):
> > > > > drm/i915/display: Add drm helper to check pr optimization
> > > > > support
> > > > > drm/i915/display: Panel Replay BW optimization for DP2.0
> > > > > tunneling
> > > > > drm/i915/display: Disable Panel Replay for DP-tunneling
> > > > > without
> > > > > optimization
> > > > >
> > > > > drivers/gpu/drm/display/drm_dp_tunnel.c | 17
> > > > > ++++++++++
> > > > > .../gpu/drm/i915/display/intel_display_regs.h | 1 +
> > > > > .../gpu/drm/i915/display/intel_dp_tunnel.c | 14 +++++++++
> > > > > .../gpu/drm/i915/display/intel_dp_tunnel.h | 6 ++++
> > > > > drivers/gpu/drm/i915/display/intel_psr.c | 31
> > > > > +++++++++++++++++--
> > > > > include/drm/display/drm_dp_tunnel.h | 6 ++++
> > > > > 6 files changed, 73 insertions(+), 2 deletions(-)
> > > > >
> > > >
> >
next prev parent reply other threads:[~2026-03-13 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 5:00 [PATCH v7 0/3] Panel Replay BW optimization Animesh Manna
2026-03-12 5:00 ` [PATCH v7 1/3] drm/i915/display: Add drm helper to check pr optimization support Animesh Manna
2026-03-12 6:40 ` Hogander, Jouni
2026-03-12 8:36 ` Manna, Animesh
2026-03-12 5:00 ` [PATCH v7 2/3] drm/i915/display: Panel Replay BW optimization for DP2.0 tunneling Animesh Manna
2026-03-12 6:44 ` Hogander, Jouni
2026-03-12 8:44 ` Manna, Animesh
2026-03-12 5:00 ` [PATCH v7 3/3] drm/i915/display: Disable Panel Replay for DP-tunneling without optimization Animesh Manna
2026-03-12 6:17 ` Hogander, Jouni
2026-03-12 8:33 ` Manna, Animesh
2026-03-12 6:56 ` ✓ i915.CI.BAT: success for Panel Replay BW optimization Patchwork
2026-03-12 8:05 ` [PATCH v7 0/3] " Hogander, Jouni
2026-03-12 8:41 ` Manna, Animesh
2026-03-12 15:18 ` Imre Deak
2026-03-13 5:20 ` Hogander, Jouni
2026-03-13 7:51 ` Imre Deak
2026-03-13 7:57 ` Hogander, Jouni [this message]
2026-03-13 4:33 ` ✓ i915.CI.Full: success for " 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=cbd5a8b6e612da35d03440b18f81138f3fa48349.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=animesh.manna@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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