Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/hwconfig: Future-proof platform checks
Date: Wed, 25 May 2022 11:50:29 -0700	[thread overview]
Message-ID: <0d115c7e-28cf-b478-7885-c428314fab73@intel.com> (raw)
In-Reply-To: <20220524235906.529771-1-matthew.d.roper@intel.com>

On 5/24/2022 16:59, Matt Roper wrote:
> PVC also has a hwconfig table.  Actually the current expectation is that
> all future platforms will have hwconfig, so let's just change the
> condition to an IP version check so that we don't need to keep updating
> this for each new platform that shows up.
>
> Cc: John Harrison <john.c.harrison@intel.com>
> Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>

> ---
>   drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> index 5aaa3948de74..4781fccc2687 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_hwconfig.c
> @@ -96,7 +96,7 @@ static bool has_table(struct drm_i915_private *i915)
>   {
>   	if (IS_ALDERLAKE_P(i915) && !IS_ADLP_N(i915))
>   		return true;
> -	if (IS_DG2(i915))
> +	if (GRAPHICS_VER_FULL(i915) >= IP_VER(12, 55))
>   		return true;
>   
>   	return false;


  parent reply	other threads:[~2022-05-25 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 23:59 [Intel-gfx] [PATCH] drm/i915/hwconfig: Future-proof platform checks Matt Roper
2022-05-25  2:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-05-25  6:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-25 15:23   ` Matt Roper
2022-05-25 19:42     ` Matt Roper
2022-05-26  2:37     ` Vudum, Lakshminarayana
2022-05-25 18:50 ` John Harrison [this message]
2022-05-25 21:47 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-05-25 23:47 ` [Intel-gfx] [PATCH] " Lucas De Marchi
2022-05-26  3:59 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=0d115c7e-28cf-b478-7885-c428314fab73@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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