Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Almahallawy, Khaled" <khaled.almahallawy@intel.com>
To: "konrad.dybcio@oss.qualcomm.com" <konrad.dybcio@oss.qualcomm.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"robin.clark@oss.qualcomm.com" <robin.clark@oss.qualcomm.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"lumag@kernel.org" <lumag@kernel.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"sean@poorly.run" <sean@poorly.run>
Subject: Re: [PATCH] drm/display/dp: Rename bit 4 of DPCD TEST_REQUEST to match DP2.1 spec
Date: Wed, 29 Oct 2025 21:42:04 +0000	[thread overview]
Message-ID: <e8902945b65cee777e14bd47ac6e27ff4a0bd281.camel@intel.com> (raw)
In-Reply-To: <78679e08-2a38-477b-a080-be0442465fbe@oss.qualcomm.com>

On Wed, 2025-10-29 at 10:42 +0100, Konrad Dybcio wrote:
> On 10/28/25 11:28 PM, Khaled Almahallawy wrote:
> > The DP_TEST_LINK_FAUX_PATTERN field was deprecated in the DP 1.3
> > spec.
> > Update its name to align with the DP 2.1 definition and reflect its
> > actual use in the code. No functional changes.
> > 
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Cc: Rob Clark <robin.clark@oss.qualcomm.com>
> > Cc: Dmitry Baryshkov <lumag@kernel.org>
> > Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>
> > Cc: Sean Paul <sean@poorly.run>
> > Signed-off-by: Khaled Almahallawy <khaled.almahallawy@intel.com>
> > ---
> >  drivers/gpu/drm/msm/dp/dp_link.c | 2 +-
> >  include/drm/display/drm_dp.h     | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/msm/dp/dp_link.c
> > b/drivers/gpu/drm/msm/dp/dp_link.c
> > index 66e1bbd80db3..5d465cf4dbc2 100644
> > --- a/drivers/gpu/drm/msm/dp/dp_link.c
> > +++ b/drivers/gpu/drm/msm/dp/dp_link.c
> > @@ -665,7 +665,7 @@ static int msm_dp_link_parse_request(struct
> > msm_dp_link_private *link)
> >  		return rlen;
> >  	}
> >  
> > -	if (!data || (data == DP_TEST_LINK_FAUX_PATTERN)) {
> > +	if (!data || (data ==
> > DP_TEST_PHY_TEST_CHANNEL_CODING_TYPE)) {
> >  		drm_dbg_dp(link->drm_dev, "link 0x%x not
> > supported\n", data);
> >  		goto end;
> >  	}
> > diff --git a/include/drm/display/drm_dp.h
> > b/include/drm/display/drm_dp.h
> > index e4eebabab975..610b8cbf1125 100644
> > --- a/include/drm/display/drm_dp.h
> > +++ b/include/drm/display/drm_dp.h
> > @@ -849,7 +849,7 @@
> >  # define DP_TEST_LINK_VIDEO_PATTERN	    (1 << 1)
> >  # define DP_TEST_LINK_EDID_READ		    (1 << 2)
> >  # define DP_TEST_LINK_PHY_TEST_PATTERN	    (1 << 3) /* DPCD >=
> > 1.1 */
> > -# define DP_TEST_LINK_FAUX_PATTERN	    (1 << 4) /* DPCD >=
> > 1.2 */
> > +# define DP_TEST_PHY_TEST_CHANNEL_CODING_TYPE	    (1 << 4)
> 
> I think it'd be useful to keep a comment of what it was before the
> deprecation and rename

Given that msm is currently the only driver that reads this bit and
correctly interprets it when handling automated test requests to
determine 128b/132b support—and following the style used throughout
this file, since I don’t see other examples referencing deprecated
names in comments

what do you think about using something like this instead?

#define DP_TEST_PHY_TEST_CHANNEL_CODING_TYPE  (1 << 4) /* DP 2.1 */

Thank You
Khaled
> 
> Konrad


  reply	other threads:[~2025-10-29 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 22:28 [PATCH] drm/display/dp: Rename bit 4 of DPCD TEST_REQUEST to match DP2.1 spec Khaled Almahallawy
2025-10-29  8:57 ` Dmitry Baryshkov
2025-10-29 21:43   ` Almahallawy, Khaled
2025-10-30  0:12     ` Dmitry Baryshkov
2025-10-29  9:42 ` Konrad Dybcio
2025-10-29 21:42   ` Almahallawy, Khaled [this message]
2025-10-31  9:35     ` Konrad Dybcio

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=e8902945b65cee777e14bd47ac6e27ff4a0bd281.camel@intel.com \
    --to=khaled.almahallawy@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    /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