From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Luca Coelho <luca@coelho.fi>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/i915: Drop PIPEDMC faults from the fault mask on LNL+
Date: Tue, 13 May 2025 13:05:34 +0300 [thread overview]
Message-ID: <aCMZbi1MBzevFrn7@intel.com> (raw)
In-Reply-To: <904dc733fc6fe6916b75a1a145cbc754413e53be.camel@coelho.fi>
On Tue, May 13, 2025 at 12:47:59PM +0300, Luca Coelho wrote:
> On Mon, 2025-05-12 at 13:33 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > On LNL+ PIPEDMC faults are reported via PIPEDMC interrupts
> > instead of the direct DE_PIPE_* reporting used on earlier
> > platforms. Drop the relevant bits from the fault mask.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_display_irq.c | 10 +++++++++-
> > drivers/gpu/drm/i915/i915_reg.h | 4 ++--
> > 2 files changed, 11 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_irq.c b/drivers/gpu/drm/i915/display/intel_display_irq.c
> > index 3e73832e5e81..a7130b14aace 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_irq.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display_irq.c
> > @@ -1016,7 +1016,15 @@ static u32 gen8_de_port_aux_mask(struct intel_display *display)
> >
> > static u32 gen8_de_pipe_fault_mask(struct intel_display *display)
> > {
> > - if (DISPLAY_VER(display) >= 14)
> > + if (DISPLAY_VER(display) >= 20)
> > + return MTL_PLANE_ATS_FAULT |
> > + GEN9_PIPE_CURSOR_FAULT |
> > + GEN11_PIPE_PLANE5_FAULT |
> > + GEN9_PIPE_PLANE4_FAULT |
> > + GEN9_PIPE_PLANE3_FAULT |
> > + GEN9_PIPE_PLANE2_FAULT |
> > + GEN9_PIPE_PLANE1_FAULT;
> > + else if (DISPLAY_VER(display) >= 14)
> > return MTL_PIPEDMC_ATS_FAULT |
> > MTL_PLANE_ATS_FAULT |
> > GEN12_PIPEDMC_FAULT |
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index 2e4190da3e0d..2d0e04eae763 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -2126,8 +2126,8 @@
> > #define GEN8_PIPE_CDCLK_CRC_ERROR REG_BIT(29)
> > #define GEN8_PIPE_CDCLK_CRC_DONE REG_BIT(28)
> > #define GEN12_PIPEDMC_INTERRUPT REG_BIT(26) /* tgl+ */
> > -#define GEN12_PIPEDMC_FAULT REG_BIT(25) /* tgl+ */
> > -#define MTL_PIPEDMC_ATS_FAULT REG_BIT(24) /* mtl+ */
> > +#define GEN12_PIPEDMC_FAULT REG_BIT(25) /* tgl-mtl */
> > +#define MTL_PIPEDMC_ATS_FAULT REG_BIT(24) /* mtl */
> > #define GEN11_PIPE_PLANE7_FAULT REG_BIT(22) /* icl/tgl */
> > #define GEN11_PIPE_PLANE6_FAULT REG_BIT(21) /* icl/tgl */
> > #define GEN11_PIPE_PLANE5_FAULT REG_BIT(20) /* icl+ */
>
> Out of curiosity, what happens without this patch? Is there going to be
> possible garbage in those bits?
They seem to be unused and tied to zero. So no garbage.
> If so, isn't that an actual bug in the
> current LNL implementation and unrelated to your flip queue preparation
> work?
I noticed the issue when I was hooking up the PIPEDMC interrupts.
>
> Reviewed-by: Luca Coelho <luciano.coelho@intel.com>
>
> --
> Cheers,
> Luca.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-05-13 10:05 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 10:33 [PATCH 0/7] drm/i915/dmc: PIPEDMC stuff Ville Syrjala
2025-05-12 10:33 ` [PATCH 1/7] drm/i915: Drop PIPEDMC faults from the fault mask on LNL+ Ville Syrjala
2025-05-13 9:47 ` Luca Coelho
2025-05-13 10:05 ` Ville Syrjälä [this message]
2025-05-12 10:33 ` [PATCH 2/7] drm/i915: Hook up PIPEDMC interrupts Ville Syrjala
2025-05-13 10:24 ` Luca Coelho
2025-05-13 10:51 ` Ville Syrjälä
2025-05-13 13:42 ` [PATCH v2 " Ville Syrjala
2025-05-13 17:16 ` Luca Coelho
2025-05-14 17:42 ` [PATCH v3 " Ville Syrjala
2025-05-12 10:33 ` [PATCH 3/7] drm/i915/dmc: Define all DMC event IDs Ville Syrjala
2025-05-13 10:27 ` Luca Coelho
2025-05-12 10:33 ` [PATCH 4/7] drm/i915/dmc: Extract dmc_evt_ctl_disable() Ville Syrjala
2025-05-13 11:24 ` Luca Coelho
2025-05-12 10:33 ` [PATCH 5/7] drm/o915/dmc: Relocate is_dmc_evt_{ctl,htp}_reg() Ville Syrjala
2025-05-13 11:41 ` Luca Coelho
2025-05-12 10:33 ` [PATCH 6/7] drm/i915/dmc: Extract is_event_handler() Ville Syrjala
2025-05-13 11:52 ` Luca Coelho
2025-05-13 11:57 ` Luca Coelho
2025-05-12 10:33 ` [PATCH 7/7] drm/i915/dmc: Introduce dmc_configure_event() Ville Syrjala
2025-05-13 12:00 ` Luca Coelho
2025-05-12 10:41 ` ✓ CI.Patch_applied: success for drm/i915/dmc: PIPEDMC stuff Patchwork
2025-05-12 10:42 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-12 10:43 ` ✓ CI.KUnit: success " Patchwork
2025-05-12 10:51 ` ✓ CI.Build: " Patchwork
2025-05-12 10:53 ` ✓ CI.Hooks: " Patchwork
2025-05-12 10:55 ` ✗ CI.checksparse: warning " Patchwork
2025-05-12 11:23 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-05-12 12:32 ` ✗ Xe.CI.Full: " Patchwork
2025-05-14 13:02 ` ✓ CI.Patch_applied: success for drm/i915/dmc: PIPEDMC stuff (rev2) Patchwork
2025-05-14 13:02 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-14 13:03 ` ✓ CI.KUnit: success " Patchwork
2025-05-14 13:13 ` ✓ CI.Build: " Patchwork
2025-05-14 13:16 ` ✓ CI.Hooks: " Patchwork
2025-05-14 13:17 ` ✗ CI.checksparse: warning " Patchwork
2025-05-14 13:40 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-14 18:21 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-15 0:29 ` ✓ CI.Patch_applied: success for drm/i915/dmc: PIPEDMC stuff (rev3) Patchwork
2025-05-15 0:30 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-15 0:31 ` ✓ CI.KUnit: success " Patchwork
2025-05-15 0:41 ` ✓ CI.Build: " Patchwork
2025-05-15 0:44 ` ✓ CI.Hooks: " Patchwork
2025-05-15 0:45 ` ✗ CI.checksparse: warning " Patchwork
2025-05-15 1:08 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-15 10:37 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-27 1:33 ` ✗ CI.Patch_applied: " 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=aCMZbi1MBzevFrn7@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luca@coelho.fi \
/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;
as well as URLs for NNTP newsgroup(s).