From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/irq: Uninstall should be called just once
Date: Tue, 17 Sep 2024 20:08:04 +0300 [thread overview]
Message-ID: <874j6eciob.fsf@intel.com> (raw)
In-Reply-To: <20240916161937.537334-1-rodrigo.vivi@intel.com>
On Mon, 16 Sep 2024, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> There shouldn't be any path where the irq uninstall is called
> twice nowadays. So, remove the FIXME commend and change
> the check to a WARN.
>
> Suggested-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Please double check the CI results, I didn't spot anything related to
this.
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_irq.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index d42997fdee65..f2ea7a550a26 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1431,13 +1431,7 @@ void intel_irq_uninstall(struct drm_i915_private *dev_priv)
> {
> int irq = to_pci_dev(dev_priv->drm.dev)->irq;
>
> - /*
> - * FIXME we can get called twice during driver probe
> - * error handling as well as during driver remove due to
> - * intel_display_driver_remove() calling us out of sequence.
> - * Would be nice if it didn't do that...
> - */
> - if (!dev_priv->irqs_enabled)
> + if (drm_WARN_ON(&dev_priv->drm, !dev_priv->irqs_enabled))
> return;
>
> intel_irq_reset(dev_priv);
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-09-17 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 16:19 [PATCH] drm/i915/irq: Uninstall should be called just once Rodrigo Vivi
2024-09-16 20:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-09-17 10:15 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-17 23:49 ` Rodrigo Vivi
2024-09-17 17:08 ` Jani Nikula [this message]
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=874j6eciob.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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