From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 5/5] drm/i915/irq: add ilk_display_irq_reset()
Date: Thu, 18 Sep 2025 15:42:35 +0300 [thread overview]
Message-ID: <0169f1407a3df2acfff0e5ee06994113761f20ff@intel.com> (raw)
In-Reply-To: <aMv8fwO34utdfIBP@intel.com>
On Thu, 18 Sep 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, Sep 18, 2025 at 03:25:48PM +0300, Jani Nikula wrote:
>> - gen2_irq_reset(uncore, DE_IRQ_REGS);
>> - display->irq.ilk_de_imr_mask = ~0u;
>> -
>> if (GRAPHICS_VER(dev_priv) == 7)
>> intel_uncore_write(uncore, GEN7_ERR_INT, 0xffffffff);
>
> GEN7_ERR_INT is display stuff as well.
D'oh. v2 on the list.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-09-18 12:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 12:25 [PATCH 0/5] drm/i915/irq: clarify and refactor ->irq_mask Jani Nikula
2025-09-18 12:25 ` [PATCH 1/5] drm/i915/irq: use a dedicated IMR cache for VLV/CHV Jani Nikula
2025-09-18 17:31 ` Ville Syrjälä
2025-09-18 12:25 ` [PATCH 2/5] drm/i915/irq: use a dedicated IMR cache for gen 5-7 Jani Nikula
2025-09-18 17:31 ` Ville Syrjälä
2025-09-18 12:25 ` [PATCH 3/5] drm/i915/irq: rename irq_mask to gen2_imr_mask Jani Nikula
2025-09-18 17:32 ` Ville Syrjälä
2025-09-18 12:25 ` [PATCH 4/5] drm/i915/irq: rename de_irq_mask[] to de_pipe_imr_mask[] Jani Nikula
2025-09-18 17:33 ` Ville Syrjälä
2025-09-18 12:25 ` [PATCH 5/5] drm/i915/irq: add ilk_display_irq_reset() Jani Nikula
2025-09-18 12:35 ` Ville Syrjälä
2025-09-18 12:42 ` Jani Nikula [this message]
2025-09-18 12:41 ` [PATCH v2] " Jani Nikula
2025-09-18 12:54 ` Ville Syrjälä
2025-09-18 13:46 ` Jani Nikula
2025-09-18 13:38 ` [PATCH v3] " Jani Nikula
2025-09-18 17:25 ` Ville Syrjälä
2025-09-19 7:17 ` Jani Nikula
2025-09-18 12:46 ` ✗ CI.checkpatch: warning for drm/i915/irq: clarify and refactor ->irq_mask Patchwork
2025-09-18 12:47 ` ✓ CI.KUnit: success " Patchwork
2025-09-18 13:02 ` ✗ CI.checksparse: warning " Patchwork
2025-09-18 13:30 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-09-18 13:36 ` ✗ CI.checkpatch: warning for drm/i915/irq: clarify and refactor ->irq_mask (rev2) Patchwork
2025-09-18 13:37 ` ✓ CI.KUnit: success " Patchwork
2025-09-18 13:52 ` ✗ CI.checksparse: warning " Patchwork
2025-09-18 14:18 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-18 14:30 ` ✗ CI.checkpatch: warning for drm/i915/irq: clarify and refactor ->irq_mask (rev3) Patchwork
2025-09-18 14:32 ` ✓ CI.KUnit: success " Patchwork
2025-09-18 14:47 ` ✗ CI.checksparse: warning " Patchwork
2025-09-18 15:06 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-18 18:27 ` ✗ i915.CI.BAT: failure for drm/i915/irq: clarify and refactor ->irq_mask (rev2) Patchwork
2025-09-18 18:52 ` ✓ i915.CI.BAT: success for drm/i915/irq: clarify and refactor ->irq_mask (rev3) Patchwork
2025-09-18 21:00 ` ✗ Xe.CI.Full: failure for drm/i915/irq: clarify and refactor ->irq_mask Patchwork
2025-09-18 22:30 ` ✓ Xe.CI.Full: success for drm/i915/irq: clarify and refactor ->irq_mask (rev2) Patchwork
2025-09-18 23:11 ` ✗ Xe.CI.Full: failure for drm/i915/irq: clarify and refactor ->irq_mask (rev3) Patchwork
2025-09-19 4:07 ` ✗ 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=0169f1407a3df2acfff0e5ee06994113761f20ff@intel.com \
--to=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.