public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Cc: <ville.syrjala@linux.intel.com>, <arun.r.murthy@intel.com>
Subject: Re: [PATCH 01/12] drm/i915/vrr: Add HAS_EMP_AS_SDP_TL macro
Date: Mon, 13 Apr 2026 14:28:21 +0530	[thread overview]
Message-ID: <d9d07b68-bd4b-4649-9c89-4371fe6489e4@intel.com> (raw)
In-Reply-To: <902d39b5ef740d820ceb73847232102b5a0a6edd@intel.com>


On 4/13/2026 2:01 PM, Jani Nikula wrote:
> On Mon, 13 Apr 2026, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
>> For BMG and LNL+ onwards the EMP_AS_SDP_TL is used for programming
>> double buffering point and transmission line for VRR packets for
>> HDMI2.1/DP/eDP/DP->HDMI2.1 PCON.
> Okay, EMP AS SDP TL is where I draw the line. I don't understand this
> acronym soup anymore. HAS_EMP_AS_SDL_TL() is meaningless to me.

Hmm I was short of naming it HAS_PROGRAMMABLE_VRR_PACKET_TL() or 
something, but then it become overly long and perhaps TL might also be 
very contextual and not very clear.

So I went ahead with EMP_AS_SDP_TL to align with the register we are 
trying to program.

I also realize that I have not mentioned full forms EMP and SDP, which I 
should have atleast in the first patch, especially for EMP (Extended 
Metadata Packet coming from HDMI2.1).

Thanks for pointing it out. I will try to be bit more clearer with the 
naming and provide the full form atleast in the place where they are 
first used.


>
> The idea with the HAS_*() helpers is to make the code more *readable*.
>
> The absolute minimum is to explain what these acronyms mean in commit
> messages or comments, but you could just make the HAS_*() macro more
> readable on its own.
>
> I'm also not convinced we need to put all the HAS_*() macros in
> intel_display_device.h when we could place some of them inside the
> single .c file that uses them.


Currently this is used in couple of files, but I got your point, if this 
finally used only in intel_vrr.c I will place it in the same file.


Thanks & Regards,

Ankit

>
>
> BR,
> Jani.
>
>
>> Add a macro for this and use it in intel_vrr.c
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_display_device.h | 1 +
>>   drivers/gpu/drm/i915/display/intel_vrr.c            | 2 +-
>>   2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h b/drivers/gpu/drm/i915/display/intel_display_device.h
>> index 1170ac346615..9338ea087e92 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_device.h
>> +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
>> @@ -173,6 +173,7 @@ struct intel_display_platforms {
>>   #define HAS_DSC(__display)		(DISPLAY_RUNTIME_INFO(__display)->has_dsc)
>>   #define HAS_DSC_3ENGINES(__display)	(DISPLAY_VERx100(__display) == 1401 && HAS_DSC(__display))
>>   #define HAS_DSC_MST(__display)		(DISPLAY_VER(__display) >= 12 && HAS_DSC(__display))
>> +#define HAS_EMP_AS_SDP_TL(__display)	(DISPLAY_VERx100(__display) == 1401 || DISPLAY_VER(__display) >= 20)
>>   #define HAS_FBC(__display)		(DISPLAY_RUNTIME_INFO(__display)->fbc_mask != 0)
>>   #define HAS_FBC_DIRTY_RECT(__display)	(DISPLAY_VER(__display) >= 30)
>>   #define HAS_FBC_SYS_CACHE(__display)	(DISPLAY_VER(__display) >= 35 && !(__display)->platform.dgfx)
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index fae1186a90b2..1fed597439b0 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -656,7 +656,7 @@ void intel_vrr_set_transcoder_timings(const struct intel_crtc_state *crtc_state)
>>   	 * Since currently we support VRR only for DP/eDP, so this is programmed
>>   	 * to for Adaptive Sync SDP to Vsync start.
>>   	 */
>> -	if (DISPLAY_VERx100(display) == 1401 || DISPLAY_VER(display) >= 20)
>> +	if (HAS_EMP_AS_SDP_TL(display))
>>   		intel_de_write(display,
>>   			       EMP_AS_SDP_TL(display, cpu_transcoder),
>>   			       EMP_AS_SDP_DB_TL(crtc_state->vrr.vsync_start));

  reply	other threads:[~2026-04-13  8:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  3:53 [PATCH 00/12] Add support for Common SDP Transmission Line Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 01/12] drm/i915/vrr: Add HAS_EMP_AS_SDP_TL macro Ankit Nautiyal
2026-04-13  8:31   ` Jani Nikula
2026-04-13  8:58     ` Nautiyal, Ankit K [this message]
2026-04-13  3:53 ` [PATCH 02/12] drm/i915/vrr: Add helper to readback EMP_AS_SDP_TL Ankit Nautiyal
2026-04-13  8:32   ` Jani Nikula
2026-04-13  9:25   ` Ville Syrjälä
2026-04-13  9:54     ` Nautiyal, Ankit K
2026-04-13 10:21       ` Ville Syrjälä
2026-04-13  3:53 ` [PATCH 03/12] drm/i915/vrr: Separate out helper to write EMP_AS_SDP_TL Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 04/12] drm/i915/dp: Add helper to get AS SDP Transmission Line Ankit Nautiyal
2026-04-13  8:34   ` Jani Nikula
2026-04-13  9:38     ` Nautiyal, Ankit K
2026-04-13  3:53 ` [PATCH 05/12] drm/i915/dp: Add crtc state for AS SDP transmission line Ankit Nautiyal
2026-04-13  8:36   ` Jani Nikula
2026-04-13  9:36     ` Nautiyal, Ankit K
2026-04-13  3:53 ` [PATCH 06/12] drm/i915/dp: Store and use AS SDP transmission line from crtc state Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 07/12] drm/i915/nvl: Add register definitions for common SDP Transmission Line Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 08/12] drm/i915/display: Add HAS_CMN_SDP_TL macro Ankit Nautiyal
2026-04-13  8:37   ` Jani Nikula
2026-04-13  3:53 ` [PATCH 09/12] drm/i915/dp: Store SDP transmission lines in crtc_state Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 10/12] drm/i915/dp: Introduce helpers to enable/disable CMN SDP Transmission line Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 11/12] drm/i915/dp: Enable Common " Ankit Nautiyal
2026-04-13  3:53 ` [PATCH 12/12] drm/i915/display: Dump SDP Transmission lines Ankit Nautiyal
2026-04-13  4:18 ` ✗ CI.checkpatch: warning for Add support for Common SDP Transmission Line (rev2) Patchwork
2026-04-13  4:19 ` ✓ CI.KUnit: success " Patchwork
2026-04-13  5:00 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-13  6:04 ` ✗ Xe.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=d9d07b68-bd4b-4649-9c89-4371fe6489e4@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=ville.syrjala@linux.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