Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	matthew.d.roper@intel.com, andi.shyti@linux.intel.com,
	intel-gfx@lists.freedesktop.org, anshuman.gupta@intel.com,
	badal.nilawar@intel.com, riana.tauro@intel.com
Subject: Re: [PATCH v1] drm/i915/dg2: enable G8 with a workaround
Date: Wed, 9 Oct 2024 19:42:40 +0300	[thread overview]
Message-ID: <ZwaygLe1WIgkL2uE@black.fi.intel.com> (raw)
In-Reply-To: <871q0pa0kv.fsf@intel.com>

On Wed, Oct 09, 2024 at 04:05:20PM +0300, Jani Nikula wrote:
> On Wed, 09 Oct 2024, Raag Jadav <raag.jadav@intel.com> wrote:
> > On Tue, Oct 08, 2024 at 08:24:42PM +0300, Jani Nikula wrote:
> >> On Mon, 07 Oct 2024, Raag Jadav <raag.jadav@intel.com> wrote:
> >> > +
> >> > +/* Wa_14022698589:dg2 */
> >> > +static void intel_enable_g8(struct intel_uncore *uncore)
> >> > +{
> >> > +	if (IS_DG2(uncore->i915)) {
> >> > +		switch (INTEL_DEVID(uncore->i915)) {
> >> 
> >> Even using INTEL_DEVID() is a no-go. There are currently four users, and
> >> even some of them are too much.
> >> 
> >> We try hard to abstract this stuff at a higher level, and there must be
> >> zero direct PCI ID checks in code other than the table driven device
> >> identification. Otherwise it's just impossible to figure out where we do
> >> platform specific stuff for each platform.
> >
> > Even if we use pci_match_id(), we'd need an explicit list to match against.
> 
> Well, we don't use that for individual workarounds or hacks either. When
> you think of using something like that, see what git grep says.
> 
> > Any better way?
> 
> You probably need to turn it into another subplatform, and add it in
> intel_device_info.c. You're probably going to need to rehash the
> INTEL_DG2_*_IDS PCI ID macros too. That's how we tell platforms apart at
> the PCI ID granularity.

Which would be controversial since the ids span across existing subplatforms,
which we don't want to break.

Don't we have quirk mask thing like display?

Raag

  reply	other threads:[~2024-10-09 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 12:24 [PATCH v1] drm/i915/dg2: enable G8 with a workaround Raag Jadav
2024-10-07 13:05 ` Nilawar, Badal
2024-10-07 13:17   ` Nilawar, Badal
2024-10-08  3:43 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-10-08  3:53 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-10-08 17:24 ` [PATCH v1] " Jani Nikula
2024-10-09 12:47   ` Raag Jadav
2024-10-09 13:05     ` Jani Nikula
2024-10-09 16:42       ` Raag Jadav [this message]
2024-10-09 16:50         ` Jani Nikula
2024-10-09 19:05         ` Matt Roper
2024-10-14  4:31     ` Gupta, Anshuman
2024-10-15  8:37       ` Raag Jadav
2024-10-14  6:30 ` kernel test robot

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=ZwaygLe1WIgkL2uE@black.fi.intel.com \
    --to=raag.jadav@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=riana.tauro@intel.com \
    --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