From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/3] drm/i915/irq: clean up irq reset/init macro hacks
Date: Thu, 26 Sep 2024 19:57:45 +0300 [thread overview]
Message-ID: <cover.1727369787.git.jani.nikula@intel.com> (raw)
Add a struct to hold IMR/IER/IIR registers, and pass them together
instead of the ugly macro hacks with macro name concatenation etc.
BR,
Jani.
Jani Nikula (3):
drm/i915/irq: add struct i915_irq_regs triplet
drm/i915/irq: remove GEN3_IRQ_RESET() and GEN3_IRQ_INIT() macros
drm/i915/irq: remove GEN8_IRQ_RESET_NDX() and GEN8_IRQ_INIT_NDX()
macros
.../gpu/drm/i915/display/intel_display_irq.c | 52 ++++++++--------
drivers/gpu/drm/i915/gt/intel_gt_irq.c | 24 ++++----
drivers/gpu/drm/i915/gt/intel_gt_regs.h | 4 ++
drivers/gpu/drm/i915/i915_irq.c | 59 +++++++++----------
drivers/gpu/drm/i915/i915_irq.h | 34 +----------
drivers/gpu/drm/i915/i915_reg.h | 53 +++++++++++++++++
drivers/gpu/drm/i915/i915_reg_defs.h | 10 ++++
drivers/gpu/drm/xe/display/ext/i915_irq.c | 31 +++++-----
8 files changed, 150 insertions(+), 117 deletions(-)
--
2.39.2
next reply other threads:[~2024-09-26 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 16:57 Jani Nikula [this message]
2024-09-26 16:57 ` [PATCH 1/3] drm/i915/irq: add struct i915_irq_regs triplet Jani Nikula
2024-09-26 19:12 ` Rodrigo Vivi
2024-09-27 8:04 ` Jani Nikula
2024-09-26 16:57 ` [PATCH 2/3] drm/i915/irq: remove GEN3_IRQ_RESET() and GEN3_IRQ_INIT() macros Jani Nikula
2024-09-26 19:13 ` Rodrigo Vivi
2024-09-26 16:57 ` [PATCH 3/3] drm/i915/irq: remove GEN8_IRQ_RESET_NDX() and GEN8_IRQ_INIT_NDX() macros Jani Nikula
2024-09-26 19:14 ` Rodrigo Vivi
2024-10-01 2:46 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/irq: clean up irq reset/init macro hacks (rev2) Patchwork
2024-10-01 2:46 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-10-01 2:55 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-01 16:25 ` ✗ Fi.CI.IGT: 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=cover.1727369787.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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