Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 4/5] drm/i915/irq: Keep GSE interrupts masked if display is not present
Date: Fri, 06 Nov 2026 11:25:09 +0200	[thread overview]
Message-ID: <5f09f7ca44f89e67ec100eb4714f314c1da4eb4f@intel.com> (raw)
In-Reply-To: <20261105203427.8696-5-ville.syrjala@linux.intel.com>

On Thu, 05 Nov 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Display is the only current user of GSE interrupts. Keep the
> GSE interrupt masked on icl+ if there is no display.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

xe could use the same treatment.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

> ---
>  drivers/gpu/drm/i915/i915_irq.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 823d97284d78..5476472d33bd 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -36,6 +36,7 @@
>  #include <drm/intel/display_parent_interface.h>
>  #include <drm/intel/intel_gmd_interrupt_regs.h>
>  
> +#include "display/intel_display_device.h"
>  #include "display/intel_display_irq.h"
>  
>  #include "gt/intel_breadcrumbs.h"
> @@ -727,9 +728,13 @@ static void gen8_irq_postinstall(struct drm_i915_private *dev_priv)
>  
>  static void gen11_gu_misc_irq_postinstall(struct drm_i915_private *dev_priv)
>  {
> +	struct intel_display *display = dev_priv->display;
>  	struct intel_gt *gt = to_gt(dev_priv);
>  	struct intel_uncore *uncore = gt->uncore;
> -	u32 gu_misc_masked = GEN11_GU_MISC_GSE;
> +	u32 gu_misc_masked = 0;
> +
> +	if (intel_display_device_present(display))
> +		gu_misc_masked |= GEN11_GU_MISC_GSE;
>  
>  	gen2_irq_init(uncore, GEN11_GU_MISC_IRQ_REGS, ~gu_misc_masked, gu_misc_masked);
>  }

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-11-06  9:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 20:34 [PATCH 0/5] drm/i915/irq: Clean up the GEN11_GU_MISC mess Ville Syrjala
2026-11-05 20:34 ` [PATCH 1/5] drm/i915/irq: Relocate gen11_gu_misc_irq_ack() Ville Syrjala
2026-11-06  9:18   ` Jani Nikula
2026-11-05 20:34 ` [PATCH 2/5] drm/i915/irq: s/gen11_gu_misc_irq_handler()/intel_display_gse_irq_handler()/ Ville Syrjala
2026-11-06  9:20   ` Jani Nikula
2026-11-05 20:34 ` [PATCH 3/5] drm/i915/irq: Extract gen11_gu_misc_irq_postinstall() Ville Syrjala
2026-11-06  9:22   ` Jani Nikula
2026-11-05 20:34 ` [PATCH 4/5] drm/i915/irq: Keep GSE interrupts masked if display is not present Ville Syrjala
2026-11-06  9:25   ` Jani Nikula [this message]
2026-11-06 17:00     ` Ville Syrjälä
2026-11-05 20:34 ` [PATCH 5/5] drm/i915/irq: Reorder GU_MISC vs. display in gen11_irq_postinstall() Ville Syrjala
2026-11-06  9:25   ` Jani Nikula
2026-11-05 20:48 ` ✓ CI.KUnit: success for drm/i915/irq: Clean up the GEN11_GU_MISC mess Patchwork
2026-11-05 21:23 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-06 22:22 ` ✗ 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=5f09f7ca44f89e67ec100eb4714f314c1da4eb4f@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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