All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/pvc: GuC depriv applies to PVC
Date: Fri, 3 Jun 2022 14:26:13 +0000	[thread overview]
Message-ID: <1d9962984a84999de2130f188c302758ec5e0bb7.camel@intel.com> (raw)
In-Reply-To: <20220602233019.1659283-1-matthew.d.roper@intel.com>

On Thu, 2022-06-02 at 16:30 -0700, Matt Roper wrote:
> We missed this setting in the initial device info patch's definition of
> XE_HPC_FEATURES.

Reviewed-by: José Roberto de Souza <jose.souza@intel.com>

> 
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 047a6e326031..a5a1a7647320 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -1089,6 +1089,7 @@ static const struct intel_device_info ats_m_info = {
>  	XE_HP_FEATURES, \
>  	.dma_mask_size = 52, \
>  	.has_3d_pipeline = 0, \
> +	.has_guc_deprivilege = 1, \
>  	.has_l3_ccs_read = 1, \
>  	.has_one_eu_per_fuse_bit = 1
>  


WARNING: multiple messages have this Message-ID (diff)
From: "Souza, Jose" <jose.souza@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pvc: GuC depriv applies to PVC
Date: Fri, 3 Jun 2022 14:26:13 +0000	[thread overview]
Message-ID: <1d9962984a84999de2130f188c302758ec5e0bb7.camel@intel.com> (raw)
In-Reply-To: <20220602233019.1659283-1-matthew.d.roper@intel.com>

On Thu, 2022-06-02 at 16:30 -0700, Matt Roper wrote:
> We missed this setting in the initial device info patch's definition of
> XE_HPC_FEATURES.

Reviewed-by: José Roberto de Souza <jose.souza@intel.com>

> 
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 047a6e326031..a5a1a7647320 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -1089,6 +1089,7 @@ static const struct intel_device_info ats_m_info = {
>  	XE_HP_FEATURES, \
>  	.dma_mask_size = 52, \
>  	.has_3d_pipeline = 0, \
> +	.has_guc_deprivilege = 1, \
>  	.has_l3_ccs_read = 1, \
>  	.has_one_eu_per_fuse_bit = 1
>  


  parent reply	other threads:[~2022-06-03 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 23:30 [PATCH] drm/i915/pvc: GuC depriv applies to PVC Matt Roper
2022-06-02 23:30 ` [Intel-gfx] " Matt Roper
2022-06-03  0:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-03  3:54 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-06-03 14:32   ` Matt Roper
2022-06-03 14:26 ` Souza, Jose [this message]
2022-06-03 14:26   ` [Intel-gfx] [PATCH] " Souza, Jose

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=1d9962984a84999de2130f188c302758ec5e0bb7.camel@intel.com \
    --to=jose.souza@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 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.