public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"Shankar,  Uma" <uma.shankar@intel.com>,
	"Sharma, Swati2" <swati2.sharma@intel.com>
Subject: Re: [PATCH 2/2] drm/i915/dmc: Enable PIPEDMC_ERROR interrupt
Date: Thu, 12 Mar 2026 17:58:59 +0530	[thread overview]
Message-ID: <dcba6eaf-1f57-4094-be69-0c8d116f92a7@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8D8D1894ECDE4A41681332E344A@DM3PPF208195D8D.namprd11.prod.outlook.com>


On 12-03-2026 08:48, Kandpal, Suraj wrote:
>> Subject: [PATCH 2/2] drm/i915/dmc: Enable PIPEDMC_ERROR interrupt
>>
>> Enable PIPEDMC_ERROR interrupt bit for display version 35+.
>>
> Add same Bspec link here too
>
>> Signed-off-by: Dibin Moolakadan Subrahmanian
>> <dibin.moolakadan.subrahmanian@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_dmc.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c
>> b/drivers/gpu/drm/i915/display/intel_dmc.c
>> index 38b284a0db82..e60f1f977070 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dmc.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dmc.c
>> @@ -510,7 +510,8 @@ static void pipedmc_clock_gating_wa(struct
>> intel_display *display, bool enable)  static u32 pipedmc_interrupt_mask(struct
>> intel_display *display)  {
>>   	if (DISPLAY_VER(display) >= 35)
>> -		return PIPEDMC_FLIPQ_PROG_DONE;
>> +		return PIPEDMC_FLIPQ_PROG_DONE |
>> +			PIPEDMC_ERROR;
>>
> Mostly looks okay but here's my question:
> I know LNL pipe B had an issue with PIPEDMC_ERROR being triggered on LNL pipe B,
> As I can see from Ville's commit message, but is it still the case for PTL ?
> Can we have that tested ?
> If that works we can add the PIPEDMC_ERROR from PTL onwards.
> Then here we can change code to create a mask and then return it finally like :
>
> mask = PIPEDMC_FLIPQ_PROG_DONE
>
> if display ver >= 30
> mask |= PIPEDMC_ERROR
>
> if display ver < 35
> mask |= PIPEDMC_GTT_FAULT |
>                  PIPEDMC_ATS_FAULT;
>
> Return mask;
>
> Obviously that is if PIPEDMC_ERROR works on PTL properly.

Thank you for spotting this, I think its better to add above  logic in new series
rather than combing with 35+ bit mask update.

Regards,
Dibin

>
> Regards,
> Suraj Kandpal
>
>>   	/*
>>   	 * FIXME PIPEDMC_ERROR not enabled for now due to LNL pipe B
>> --
>> 2.43.0

  reply	other threads:[~2026-03-12 12:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  6:32 [PATCH 0/2] drm/i915/dmc: Update PIPEDMC interrupt mask Dibin Moolakadan Subrahmanian
2026-03-11  6:32 ` [PATCH 1/2] drm/i915/dmc: Remove invalid PIPEDMC interrupt bits Dibin Moolakadan Subrahmanian
2026-03-12  3:10   ` Kandpal, Suraj
2026-03-12 12:24     ` Dibin Moolakadan Subrahmanian
2026-03-11  6:32 ` [PATCH 2/2] drm/i915/dmc: Enable PIPEDMC_ERROR interrupt Dibin Moolakadan Subrahmanian
2026-03-12  3:18   ` Kandpal, Suraj
2026-03-12 12:28     ` Dibin Moolakadan Subrahmanian [this message]
2026-03-13  3:26       ` Kandpal, Suraj
2026-03-13  4:25         ` Dibin Moolakadan Subrahmanian
2026-03-13  5:04           ` Kandpal, Suraj
2026-03-13 10:03             ` Ville Syrjälä
2026-03-13 10:08               ` Kandpal, Suraj
2026-03-13 11:25                 ` Ville Syrjälä
2026-03-16  2:49                   ` Kandpal, Suraj
2026-03-16 12:13                     ` Dibin Moolakadan Subrahmanian
2026-03-11  7:58 ` ✓ i915.CI.BAT: success for drm/i915/dmc: Update PIPEDMC interrupt mask (rev2) Patchwork
2026-03-11 18:42 ` ✓ i915.CI.Full: " 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=dcba6eaf-1f57-4094-be69-0c8d116f92a7@intel.com \
    --to=dibin.moolakadan.subrahmanian@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@intel.com \
    --cc=swati2.sharma@intel.com \
    --cc=uma.shankar@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