From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/dp: Add definition for Panel Replay full-line granularity
Date: Wed, 4 Mar 2026 10:26:10 +0000 [thread overview]
Message-ID: <091a8e15c32ab6bb73964d4f6fabe9fd896e5608.camel@intel.com> (raw)
In-Reply-To: <77e5ca2b-7473-44d1-ba4b-8a301adcd788@linux.intel.com>
Thank you Maarten. These patches are now pushed to drm-intel-next.
Thank you Uma for the review.
BR,
Jouni Högander
On Wed, 2026-03-04 at 09:29 +0100, Maarten Lankhorst wrote:
> Hey,
>
> Den 2026-02-27 kl. 06:49, skrev Hogander, Jouni:
> > On Thu, 2026-02-26 at 21:02 +0000, Shankar, Uma wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On
> > > > Behalf
> > > > Of Jouni
> > > > Högander
> > > > Sent: Wednesday, February 25, 2026 1:12 PM
> > > > To: intel-gfx@lists.freedesktop.org;
> > > > intel-xe@lists.freedesktop.org
> > > > Cc: Hogander, Jouni <jouni.hogander@intel.com>;
> > > > dri-devel@lists.freedesktop.org
> > > > Subject: [PATCH 1/2] drm/dp: Add definition for Panel Replay
> > > > full-
> > > > line granularity
> > > >
> > > > DP specification is saying value 0xff 0xff in PANEL REPLAY
> > > > SELECTIVE
> > > > UPDATE X GRANULARITY CAPABILITY registers (0xb2 and 0xb3) means
> > > > full-
> > > > line granularity. Add definition for this.
> > >
> > > I think it would be good to call this also out also in comment:
> > > "The SU region width shall be equal to the horizontal width of
> > > the
> > > timing being transported"
> > > This clarifies what is meant by full line granularity here.
> >
> > I will add this comment.
> >
> > >
> > > >
> > > > Cc: dri-devel@lists.freedesktop.org
> > > > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > > > ---
> > > > include/drm/display/drm_dp.h | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > > >
> > > > diff --git a/include/drm/display/drm_dp.h
> > > > b/include/drm/display/drm_dp.h index
> > > > e4eebabab975..8b15d3eeb716 100644
> > > > --- a/include/drm/display/drm_dp.h
> > > > +++ b/include/drm/display/drm_dp.h
> > > > @@ -571,6 +571,8 @@
> > > > # define
> > > > DP_PANEL_REPLAY_LINK_OFF_SUPPORTED_IN_PR_AFTER_ADAPTIVE_SYN
> > > > C_SDP (1 << 7)
> > > >
> > > > #define DP_PANEL_REPLAY_CAP_X_GRANULARITY 0xb2
> > > > +# define DP_PANEL_REPLAY_FULL_LINE_GRANULARITY 0xffff
> > >
> > > Space in #define can be removed.
> >
> > I followed convention used elsewhere in drm_dp.h. I.e. register
> > field
> > definitions have this extra space. What do you think?
> >
> > BR,
> > Jouni Högander
> Seems to be the convention here, so fine with me.
>
> For merging through drm-intel:
> Acked-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
> > >
> > > With above fixed, Change looks good to me.
> > > Reviewed-by: Uma Shankar <uma.shankar@intel.com>
> > >
> > > > #define DP_PANEL_REPLAY_CAP_Y_GRANULARITY 0xb4
> > > >
> > > > /* Link Configuration */
> > > > --
> > > > 2.43.0
> > >
> >
>
prev parent reply other threads:[~2026-03-04 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 7:42 [PATCH 1/2] drm/dp: Add definition for Panel Replay full-line granularity Jouni Högander
2026-02-25 7:42 ` [PATCH 2/2] drm/i915/psr: Fix for Panel Replay X granularity DPCD register handling Jouni Högander
2026-02-26 21:04 ` Shankar, Uma
2026-02-25 7:49 ` ✓ CI.KUnit: success for series starting with [1/2] drm/dp: Add definition for Panel Replay full-line granularity Patchwork
2026-02-25 8:21 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-25 12:13 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-26 21:02 ` [PATCH 1/2] " Shankar, Uma
2026-02-27 5:49 ` Hogander, Jouni
2026-03-04 8:29 ` Maarten Lankhorst
2026-03-04 10:26 ` Hogander, Jouni [this message]
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=091a8e15c32ab6bb73964d4f6fabe9fd896e5608.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=uma.shankar@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