All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Switch over to gen3 irq code on gen2
Date: Fri, 27 Sep 2024 17:45:48 +0300	[thread overview]
Message-ID: <ZvbFHLCwe3_CPv0f@intel.com> (raw)
In-Reply-To: <20240927143545.8665-5-ville.syrjala@linux.intel.com>

On Fri, Sep 27, 2024 at 05:35:45PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> The only real reason why we have the gen2 vs. gen3+ split
> in irq handling is that bspec claims that IIR/IMR/IER/ISR
> and EMR are only 16 bits on gen2, as opposed to being 32
> bits on gen3+. That doesn't seem to be a meaningful
> distinction as 32bit access to these registers works
> perfectly fine on gen2
> 
> Interestingly the 16 msbs of IMR are in fact hardcoded
> to 1 on gen2, which to me indicates that 32bit access
> was the plan all along, and perhaps someone just forgot
> to update the spec.
> 
> Nuke the special 16bit gen2 irq code and switch over to
> the gen3 code.
> 
> Gen2 doesn't have the ASLE interrupt, which just needs
> a small tweak in i915_irq_postinstall().
> 
> And so far we've not had a codepath that could enable the
> legacy BLC interrupt on gen2. Now we do, but we'll never
> actually do it since gen2 machines don't have OpRegion.
> (and neither do i915/i945 machines btw). On these older
> platforms the legacy BLC interrupt is meant to be used
> in conjunction with the LBPC backlight stuff, but we
> never actually switch off the legacy/combination mode
> and thus don't use the interrupt either.
> 
> This was quickly smoke tested on all gen2 variants.
> 
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Hmm. I guess I should do this to the gt code as well.
But I'll hold off on that for the moment.

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2024-09-27 14:45 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ä [this message]
2024-09-27 14:56 ` [PATCH 0/4] drm/i915: Use the gen3+ " Jani Nikula
2024-10-01 15:47   ` Ville Syrjälä
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=ZvbFHLCwe3_CPv0f@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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 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.