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 6/6] drm/i915/irq: split ILK display irq handling
Date: Tue, 23 Sep 2025 17:15:52 +0300 [thread overview]
Message-ID: <b11c1170e758467a3637fd62545b7b65101417be@intel.com> (raw)
In-Reply-To: <aM1IOabvrlmkzQsk@intel.com>
On Fri, 19 Sep 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, Sep 19, 2025 at 12:51:49PM +0300, Jani Nikula wrote:
>> +bool ilk_display_irq_handler(struct intel_display *display, u32 de_ier, u32 sde_ier)
>> +{
>> + u32 de_iir;
>> + bool handled = false;
>> +
>> + de_iir = intel_de_read(display, DEIIR);
>> + if (de_iir) {
>> + intel_de_write(display, DEIIR, de_iir);
>> + if (DISPLAY_VER(display) >= 7)
>> + _ivb_display_irq_handler(display, de_iir);
>> + else
>> + _ilk_display_irq_handler(display, de_iir);
>> + handled = true;
>> + }
>> +
>> + intel_de_write(display, DEIER, de_ier);
>> +
>> + if (sde_ier)
>> + intel_de_write(display, SDEIER, sde_ier);
>
> Maybe the re-enable should be its own function just to make
> things a bit less confusing?
With that I can actually drop patch 5/6.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-09-23 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 9:51 [PATCH 0/6] drm/i915/irq: display irq refactoring Jani Nikula
2025-09-19 9:51 ` [PATCH 1/6] drm/i915/irq: drop intel_psr_regs.h include Jani Nikula
2025-09-19 9:51 ` [PATCH 2/6] drm/i915/irq: initialize gen2_imr_mask in terms of enable_mask Jani Nikula
2025-09-19 9:51 ` [PATCH 3/6] drm/i915/irq: abstract i9xx_display_irq_enable_mask() Jani Nikula
2025-09-19 9:51 ` [PATCH 4/6] drm/i915/irq: move check for HAS_HOTPLUG() inside i9xx_hpd_irq_ack() Jani Nikula
2025-09-19 9:51 ` [PATCH 5/6] drm/i915/irq: change ILK irq handling order Jani Nikula
2025-09-19 9:51 ` [PATCH 6/6] drm/i915/irq: split ILK display irq handling Jani Nikula
2025-09-19 12:10 ` Ville Syrjälä
2025-09-23 14:15 ` Jani Nikula [this message]
2025-09-19 12:23 ` Ville Syrjälä
2025-09-23 14:17 ` Jani Nikula
2025-09-19 9:58 ` ✗ CI.checkpatch: warning for drm/i915/irq: display irq refactoring Patchwork
2025-09-19 9:59 ` ✓ CI.KUnit: success " Patchwork
2025-09-19 18:42 ` ✗ 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=b11c1170e758467a3637fd62545b7b65101417be@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox