From: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Cc: <ville.syrjala@linux.intel.com>, <uma.shankar@intel.com>,
<swati2.sharma@intel.com>, <suraj.kandpal@intel.com>
Subject: Re: [PATCH v3 0/2] drm/i915/dmc: Update PIPEDMC interrupt mask/
Date: Thu, 12 Mar 2026 19:14:09 +0530 [thread overview]
Message-ID: <c84d549e-cbd0-442c-b57d-9ac84eb8c10e@intel.com> (raw)
In-Reply-To: <20260312132654.2614433-1-dibin.moolakadan.subrahmanian@intel.com>
Hi,
Please ignore this series. The cover letter was incorrect.
I will resend the patches in the correct series.
Regards,
Dibin
On 12-03-2026 18:56, Dibin Moolakadan Subrahmanian wrote:
> On display version 35+ the PIPEDMC_ATS_FAULT and
> PIPEDMC_GTT_FAULT interrupt bits are no longer defined.
> Update the interrupt mask accordingly and enable the
> PIPEDMC_ERROR interrupt.
>
> Changes in v2:
> - Move PIPEDMC_ERROR interrupt enable to a separate patch (Ville Syrjala)
> Changes in v3:
> - Add Bspec reference (Suraj Kandpal)
>
> Dibin Moolakadan Subrahmanian (2):
> drm/i915/dmc: Remove invalid PIPEDMC interrupt bits
> drm/i915/dmc: Enable PIPEDMC_ERROR interrupt
>
> drivers/gpu/drm/i915/display/intel_dmc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
next prev parent reply other threads:[~2026-03-12 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 13:26 [PATCH v3 0/2] drm/i915/dmc: Update PIPEDMC interrupt mask/ Dibin Moolakadan Subrahmanian
2026-03-12 13:26 ` [PATCH v3 1/2] drm/i915/dmc: Remove invalid PIPEDMC interrupt bits Dibin Moolakadan Subrahmanian
2026-03-12 13:26 ` [PATCH v3 2/2] drm/i915/dmc: Enable PIPEDMC_ERROR interrupt Dibin Moolakadan Subrahmanian
2026-03-12 13:44 ` Dibin Moolakadan Subrahmanian [this message]
2026-03-12 14:52 ` ✓ i915.CI.BAT: success for drm/i915/dmc: Update PIPEDMC interrupt mask/ Patchwork
2026-03-13 12:58 ` ✗ i915.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=c84d549e-cbd0-442c-b57d-9ac84eb8c10e@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