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 15:47:34 +0300 [thread overview]
Message-ID: <ZwZ7ZrcBObuIrPqh@black.fi.intel.com> (raw)
In-Reply-To: <87ttdmbj8l.fsf@intel.com>
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:
> > Host BIOS doesn't enable G8 power mode due to an issue on DG2, so we
> > enable it from kernel with Wa_14022698589. Currently it is enabled for
> > all DG2 devices with the exception of a few, for which, it is enabled
> > only when paired with whitelisted CPU models.
>
> In commit messages "currently" and the present tense usually refer to
> the status quo before the patch has been merged. Doesn't seem to be the
> case here, and it confuses what we have now and what the patch changes.
True.
> >
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > ---
> > drivers/gpu/drm/i915/gt/intel_workarounds.c | 43 +++++++++++++++++++++
> > drivers/gpu/drm/i915/i915_reg.h | 1 +
> > 2 files changed, 44 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > index e539a656cfc3..b2db51377488 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> > @@ -14,11 +14,30 @@
> > #include "intel_gt_mcr.h"
> > #include "intel_gt_print.h"
> > #include "intel_gt_regs.h"
> > +#include "intel_pcode.h"
> > #include "intel_ring.h"
> > #include "intel_workarounds.h"
> >
> > #include "display/intel_fbc_regs.h"
> >
> > +#ifdef CONFIG_X86
> > +#include <asm/cpu_device_id.h>
> > +#include <asm/intel-family.h>
> > +
> > +static const struct x86_cpu_id g8_cpu_ids[] = {
> > + X86_MATCH_VFM(INTEL_ALDERLAKE, NULL),
> > + X86_MATCH_VFM(INTEL_ALDERLAKE_L, NULL),
> > + X86_MATCH_VFM(INTEL_COMETLAKE, NULL),
> > + X86_MATCH_VFM(INTEL_KABYLAKE, NULL),
> > + X86_MATCH_VFM(INTEL_KABYLAKE_L, NULL),
> > + X86_MATCH_VFM(INTEL_RAPTORLAKE, NULL),
> > + X86_MATCH_VFM(INTEL_RAPTORLAKE_P, NULL),
> > + X86_MATCH_VFM(INTEL_RAPTORLAKE_S, NULL),
> > + X86_MATCH_VFM(INTEL_ROCKETLAKE, NULL),
> > + {}
> > +};
> > +#endif
> > +
> > /**
> > * DOC: Hardware workarounds
> > *
> > @@ -1770,9 +1789,33 @@ static void wa_list_apply(const struct i915_wa_list *wal)
> > intel_gt_mcr_unlock(gt, flags);
> > }
> >
> > +#define DG2_G8_WA_RANGE_1 0x56A0 ... 0x56AF
> > +#define DG2_G8_WA_RANGE_2 0x56B0 ... 0x56B9
>
> Absolutely not.
I had an "ugly" self-note which I forgot to add while sending out :D
> > +
> > +/* 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.
Any better way?
Raag
next prev parent reply other threads:[~2024-10-09 12:47 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 [this message]
2024-10-09 13:05 ` Jani Nikula
2024-10-09 16:42 ` Raag Jadav
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=ZwZ7ZrcBObuIrPqh@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