All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915/irq: s/gen3/gen2/
Date: Thu, 10 Oct 2024 15:22:25 +0300	[thread overview]
Message-ID: <87frp46tby.fsf@intel.com> (raw)
In-Reply-To: <ZwfB6l8nQelIYx2c@intel.com>

On Thu, 10 Oct 2024, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Oct 09, 2024 at 01:20:53PM +0300, Jani Nikula wrote:
>> On Wed, 09 Oct 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
>> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> >
>> > Now that we use the gen3 codepaths also for gen2
>> > rename everything to gen2_ to match.
>> 
>> This was fine for the gt stuff where there are gen5 and gen6 functions,
>> but should we just call these something more generic since there are no
>> platform specific functions?
>> 
>> The naming is a bit funky already.
>> 
>> intel_irq_init() is *not* the higher level function for init. It's
>> actually intel_irq_install() -> intel_irq_postinstall() that calls
>> gen3_irq_init() and some other stuff.
>
> intel_irq_init() seems like it should be ripped apart and distributed to
> more appropriate places. The guc stuff at least. And most of the l3
> parity stuff also lives in some gt code, so the rest should probably
> move as well (Either that or we rip out the wole thing. I suspect no
> is actually using that anywhere).
>
> But no idea what to do about the gen2_ stuff.

*shrug* I guess in the mean time we can go ahead with this.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>



-- 
Jani Nikula, Intel

  reply	other threads:[~2024-10-10 12:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 21:43 [PATCH 0/4] drm/i915: gen2 stuff Ville Syrjala
2024-10-08 21:43 ` [PATCH 1/4] drm/i915/gt: Nuke gen2_irq_{enable,disable}() Ville Syrjala
2024-10-09 11:12   ` Jani Nikula
2024-10-08 21:43 ` [PATCH 2/4] drm/i915/gt: s/gen3/gen2/ Ville Syrjala
2024-10-09 11:12   ` Jani Nikula
2024-10-08 21:43 ` [PATCH 3/4] drm/i915/irq: s/gen3/gen2/ Ville Syrjala
2024-10-09 10:20   ` Jani Nikula
2024-10-10 12:00     ` Ville Syrjälä
2024-10-10 12:22       ` Jani Nikula [this message]
2024-10-08 21:43 ` [PATCH 4/4] drm/i915/pmu: Add support for gen2 Ville Syrjala
2024-10-09 11:17   ` Jani Nikula
2024-10-08 21:49 ` ✓ CI.Patch_applied: success for drm/i915: gen2 stuff Patchwork
2024-10-08 21:49 ` ✓ CI.checkpatch: " Patchwork
2024-10-08 21:51 ` ✓ CI.KUnit: " Patchwork
2024-10-08 22:02 ` ✓ CI.Build: " Patchwork
2024-10-08 22:04 ` ✓ CI.Hooks: " Patchwork
2024-10-08 22:06 ` ✗ CI.checksparse: warning " Patchwork
2024-10-08 22:19 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-10-08 22:24 ` ✓ CI.BAT: success " Patchwork
2024-10-08 22:28 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-09  5:34 ` ✗ CI.FULL: failure " Patchwork
2024-10-10  3:08 ` ✗ 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=87frp46tby.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 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.