From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Nuke drm_driver irq vfuncs
Date: Wed, 19 Jun 2019 21:54:12 +0300 [thread overview]
Message-ID: <20190619185412.GF5942@intel.com> (raw)
In-Reply-To: <156096988267.664.152988980390708525@skylake-alporthouse-com>
On Wed, Jun 19, 2019 at 07:44:42PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-06-19 18:08:41)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Stop using the irq vfuncs under drm_driver. That's not going to fly
> > in a mixed gen environment since the structure is shared between all
> > the devices.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > ---
> > drivers/gpu/drm/i915/i915_drv.c | 2 +-
> > drivers/gpu/drm/i915/i915_irq.c | 280 ++++++++++++++++----------------
> > 2 files changed, 140 insertions(+), 142 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> > index f62e3397d936..ea6b06109d5a 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.c
> > +++ b/drivers/gpu/drm/i915/i915_drv.c
> > @@ -754,7 +754,7 @@ static int i915_load_modeset_init(struct drm_device *dev)
> > cleanup_modeset:
> > intel_modeset_cleanup(dev);
>
> Ahah! intel_modeset_cleanup() also calls intel_irq_uninstall()
Oh dear. This could be a deep gopher hole...
>
> > cleanup_irq:
> > - drm_irq_uninstall(dev);
> > + intel_irq_uninstall(dev_priv);
> > intel_gmbus_teardown(dev_priv);
> > cleanup_csr:
> > intel_csr_ucode_fini(dev_priv);
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-19 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 17:08 [PATCH 0/4] drm/i915: Eliminate platform specific drm_driver vfuncs Ville Syrjala
2019-06-19 17:08 ` [PATCH 1/4] drm/i915: Fix various tracepoints for gen2 Ville Syrjala
2019-06-19 17:08 ` [PATCH 2/4] drm/i915: Switch to per-crtc vblank vfuncs Ville Syrjala
2019-06-19 17:30 ` Chris Wilson
2019-06-19 17:08 ` [PATCH 3/4] drm/i915: Nuke drm_driver irq vfuncs Ville Syrjala
2019-06-19 18:44 ` Chris Wilson
2019-06-19 18:54 ` Ville Syrjälä [this message]
2019-06-20 10:33 ` [PATCH v2 " Ville Syrjala
2019-06-20 10:35 ` Chris Wilson
2019-06-19 17:08 ` [PATCH 4/4] drm/i915: Initialize drm_driver vblank funcs at compile time Ville Syrjala
2019-06-19 18:09 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Eliminate platform specific drm_driver vfuncs Patchwork
2019-06-19 18:12 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-19 18:27 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-20 10:41 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Eliminate platform specific drm_driver vfuncs (rev2) Patchwork
2019-06-20 10:44 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-20 15:27 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-25 22:21 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Eliminate platform specific drm_driver vfuncs (rev3) Patchwork
2019-06-25 22:24 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-25 22:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-26 3:27 ` ✓ Fi.CI.IGT: " 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=20190619185412.GF5942@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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