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] drm/i915: Indicate which pipe lied about its interrupts
Date: Tue, 13 May 2025 14:46:05 +0300 [thread overview]
Message-ID: <87plgcivia.fsf@intel.com> (raw)
In-Reply-To: <20250513092820.18715-1-ville.syrjala@linux.intel.com>
On Tue, 13 May 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Indicate which pipe signalled the spurious DE PIPE interrupt.
> Might help with debugging a bit if we know where the interrupt
> is supposedly coming from.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_irq.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_irq.c b/drivers/gpu/drm/i915/display/intel_display_irq.c
> index 3e73832e5e81..a3261c7aad72 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_irq.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_irq.c
> @@ -1418,7 +1418,8 @@ void gen8_de_irq_handler(struct intel_display *display, u32 master_ctl)
> iir = intel_de_read(display, GEN8_DE_PIPE_IIR(pipe));
> if (!iir) {
> drm_err_ratelimited(display->drm,
> - "The master control interrupt lied (DE PIPE)!\n");
> + "The master control interrupt lied (DE PIPE %c)!\n",
> + pipe_name(pipe));
> continue;
> }
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-05-13 11:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 9:28 [PATCH] drm/i915: Indicate which pipe lied about its interrupts Ville Syrjala
2025-05-13 11:46 ` Jani Nikula [this message]
2025-05-14 8:11 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-14 8:11 ` ✓ CI.checkpatch: " Patchwork
2025-05-14 8:12 ` ✓ CI.KUnit: " Patchwork
2025-05-14 8:22 ` ✓ CI.Build: " Patchwork
2025-05-14 8:25 ` ✓ CI.Hooks: " Patchwork
2025-05-14 8:26 ` ✓ CI.checksparse: " Patchwork
2025-05-14 8:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-14 11:51 ` ✓ Xe.CI.Full: " Patchwork
2025-05-26 22:54 ` ✓ CI.Patch_applied: " Patchwork
2025-05-26 22:54 ` ✓ CI.checkpatch: " Patchwork
2025-05-26 22:55 ` ✓ CI.KUnit: " Patchwork
2025-05-26 23:06 ` ✓ CI.Build: " 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=87plgcivia.fsf@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