From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/4] drm/i915: Use the gen3+ irq code on gen2
Date: Tue, 1 Oct 2024 18:47:28 +0300 [thread overview]
Message-ID: <ZvwZkJJwOBpi5Iw0@intel.com> (raw)
In-Reply-To: <87ed55xi00.fsf@intel.com>
On Fri, Sep 27, 2024 at 05:56:31PM +0300, Jani Nikula wrote:
> On Fri, 27 Sep 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Eliminate the special gen2 irq code by simply reusing the
> > gen3+ code on gen2. Works just fine on actual hardware.
> >
> > I generated the last patch with -U20 to help with review.
> > Unfortunately it still didn't pick up i915_irq_handler()
> > I don't suppose there's a magic knob to tell git diff
> > to include a specific function wholesale in the context?
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Thanks. Pushed the series. I suppose there might be some
conflicts with your irq macro cleanup.
>
>
> >
> > Ville Syrjälä (4):
> > drm/i915: Introduce i915_has_legacy_blc_interrupt()
> > drm/i915: Clean up gen3 hotplug irq setup
> > drm/i915: Clean up some comments in gmch irq code
> > drm/i915: Switch over to gen3 irq code on gen2
> >
> > .../gpu/drm/i915/display/intel_display_irq.c | 38 ++--
> > .../gpu/drm/i915/display/intel_display_irq.h | 1 -
> > drivers/gpu/drm/i915/i915_irq.c | 202 ++----------------
> > 3 files changed, 28 insertions(+), 213 deletions(-)
>
> --
> Jani Nikula, Intel
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2024-10-01 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 14:35 [PATCH 0/4] drm/i915: Use the gen3+ irq code on gen2 Ville Syrjala
2024-09-27 14:35 ` [PATCH 1/4] drm/i915: Introduce i915_has_legacy_blc_interrupt() Ville Syrjala
2024-09-27 14:35 ` [PATCH 2/4] drm/i915: Clean up gen3 hotplug irq setup Ville Syrjala
2024-09-27 14:35 ` [PATCH 3/4] drm/i915: Clean up some comments in gmch irq code Ville Syrjala
2024-09-27 14:35 ` [PATCH 4/4] drm/i915: Switch over to gen3 irq code on gen2 Ville Syrjala
2024-09-27 14:45 ` Ville Syrjälä
2024-09-27 14:56 ` [PATCH 0/4] drm/i915: Use the gen3+ " Jani Nikula
2024-10-01 15:47 ` Ville Syrjälä [this message]
2024-09-27 22:08 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-09-27 22:25 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-28 20:44 ` ✗ 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=ZvwZkJJwOBpi5Iw0@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.