All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2 08/15] drm/xe/xe2: Define Xe2_LPG IP features
Date: Tue, 22 Aug 2023 11:08:10 +0530	[thread overview]
Message-ID: <ZORJwnjGGpepCpAx@bvivekan-mobl> (raw)
In-Reply-To: <hwe6d7pbsibj4lf46gsherwfsq3pzayxvofwlvhj3k6ahwradi@hhwryrzxq2ty>

On 21.08.2023 09:03, Lucas De Marchi wrote:
> On Mon, Aug 21, 2023 at 08:28:45PM +0530, Balasubramani Vivekanandan wrote:
> > On 18.08.2023 15:08, Lucas De Marchi wrote:
> > > From: Matt Roper <matthew.d.roper@intel.com>
> > > 
> > > Define a common set of Xe2 graphics feature flags and definitions that
> > > will be used for all platforms in this family.
> > > 
> > > Several of the feature flags are inherited unchanged from Xe_HP and/or
> > > Xe_HPC platforms:
> > >  - dma_mask_size remains 46   (Bspec 70817)
> > >  - supports_usm=1             (Bspec 59651)
> > >  - has_flatccs=1              (Bspec 58797)
> > >  - has_asid=1                 (Bspec 59654, 59265, 60288)
> > >  - has_range_tlb_invalidate=1 (Bspec 71126)
> > > 
> > > However some of them still need proper implementation in the driver to
> > > be used, so they are disabled.
> > > 
> > > Notable Xe2-specific changes:
> > >  - All Xe2 platforms use a five-level page table, regardless of the
> > >    virtual address space for the platform.  (Bspec 59505)
> > > 
> > > The graphics engine mask represents the Xe2 architecture engines (Bspec
> > > 60149), but individual platforms may have a reduced set of usable
> > > engines, as reflected by their fusing.
> > > 
> > > Cc: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
> > > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> > > Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> > > ---
> > >  drivers/gpu/drm/xe/xe_pci.c | 19 +++++++++++++++++++
> > >  1 file changed, 19 insertions(+)

Reviewed-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>

Regards,
Bala

> > > 
> > > diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> > > index 46e3a9632efe..ed6c4bf8c63b 100644
> > > --- a/drivers/gpu/drm/xe/xe_pci.c
> > > +++ b/drivers/gpu/drm/xe/xe_pci.c
> > > @@ -176,6 +176,24 @@ static const struct xe_graphics_desc graphics_xelpg = {
> > >  	.has_flat_ccs = 0,
> > >  };
> > > 
> > > +#define XE2_GFX_FEATURES \
> > > +	.dma_mask_size = 46, \
> > > +	.has_asid = 1, \
> > > +	.has_flat_ccs = 0 /* FIXME: implementation missing */, \
> > > +	.has_range_tlb_invalidation = 1, \
> > > +	.supports_usm = 0 /* FIXME: implementation missing */, \
> > > +	.vm_max_level = 4, \
> > > +	.hw_engine_mask = \
> > > +		BIT(XE_HW_ENGINE_RCS0) | \
> > > +		BIT(XE_HW_ENGINE_BCS8) | BIT(XE_HW_ENGINE_BCS0) | \
> > > +		GENMASK(XE_HW_ENGINE_CCS3, XE_HW_ENGINE_CCS0)
> > 
> > Bspec: 60149 lists more BCS engines than what is assigned here. Is it
> > intentionally limited to only BCS0, BCS8.
> 
> That's only the mmio address offsets allocated, it doesn't mean the
> platform has those engines. See BSpec 70815: there's one main copy
> engine and one paging copy engine.
> 
> Lucas De Marchi
> 
> > 
> > Regards,
> > Bala
> > 
> > > +
> > > +static const struct xe_graphics_desc graphics_xe2 = {
> > > +	.name = "Xe2_LPG",
> > > +
> > > +	XE2_GFX_FEATURES,
> > > +};
> > > +
> > >  static const struct xe_media_desc media_xem = {
> > >  	.name = "Xe_M",
> > >  	.ver = 12,
> > > @@ -320,6 +338,7 @@ __diag_pop();
> > >  static struct gmdid_map graphics_ip_map[] = {
> > >  	{ 1270, &graphics_xelpg },
> > >  	{ 1271, &graphics_xelpg },
> > > +	{ 2004, &graphics_xe2 },
> > >  };
> > > 
> > >  /* Map of GMD_ID values to media IP */
> > > --
> > > 2.40.1
> > > 

  reply	other threads:[~2023-08-22  5:38 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 22:08 [Intel-xe] [PATCH v2 00/15] Add Lunar Lake support Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 01/15] drm/xe/xe2: Update render/compute context image sizes Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 02/15] drm/xe/xe2: Add GT topology readout Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 03/15] drm/xe/xe2: Add MCR register steering for primary GT Lucas De Marchi
2023-08-21 14:32   ` Balasubramani Vivekanandan
2023-08-22 16:55     ` Matt Atwood
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 04/15] drm/xe/xe2: Add MCR register steering for media GT Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 05/15] drm/xe/xe2: Update context image layouts Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 06/15] drm/xe/xe2: Handle fused-off CCS engines Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 07/15] drm/xe/xe2: AuxCCS is no longer used Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 08/15] drm/xe/xe2: Define Xe2_LPG IP features Lucas De Marchi
2023-08-21 14:58   ` Balasubramani Vivekanandan
2023-08-21 16:03     ` Lucas De Marchi
2023-08-22  5:38       ` Balasubramani Vivekanandan [this message]
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 09/15] drm/xe/xe2: Define Xe2_LPM " Lucas De Marchi
2023-08-21 14:23   ` Matt Roper
2023-08-21 18:46     ` Lucas De Marchi
2023-08-22  5:41   ` Balasubramani Vivekanandan
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 10/15] drm/xe/xe2: Track VA bits independently of max page table level Lucas De Marchi
2023-08-22  5:54   ` Balasubramani Vivekanandan
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 11/15] drm/xe/xe2: Add MOCS table Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 12/15] drm/xe/xe2: Program GuC's MOCS on Xe2 and beyond Lucas De Marchi
2023-08-22  6:27   ` Balasubramani Vivekanandan
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 13/15] drm/xe/lnl: Add LNL platform definition Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 14/15] drm/xe/lnl: Add GuC firmware definition Lucas De Marchi
2023-08-18 22:08 ` [Intel-xe] [PATCH v2 15/15] drm/xe/lnl: Hook up MOCS table Lucas De Marchi
2023-08-18 22:11 ` [Intel-xe] ✓ CI.Patch_applied: success for Add Lunar Lake support (rev2) Patchwork
2023-08-18 22:11 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-18 22:12 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-18 22:16 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-18 22:17 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-18 22:17 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-18 22:44 ` [Intel-xe] ✓ CI.BAT: success " 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=ZORJwnjGGpepCpAx@bvivekan-mobl \
    --to=balasubramani.vivekanandan@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --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.