Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 6/6] drm/xe/mtl: Handle PAT_INDEX offset jump
Date: Fri, 24 Mar 2023 22:34:25 +0100	[thread overview]
Message-ID: <5e44e643-ae8d-cd40-5b67-e86758e7d120@linux.intel.com> (raw)
In-Reply-To: <20230324210415.2434992-7-matthew.d.roper@intel.com>


On 3/24/2023 10:04 PM, Matt Roper wrote:
> Starting with MTL, the number of entries in the PAT table increased to
> 16.  The register offset jumped between index 7 and index 8, so a slight
> adjustment is needed to ensure the PAT_INDEX macros select the proper
> offset for the upper half of the table.
>
> Note that although there are 16 registers in the hardware, the driver is
> currently only asked to program the first 5, and we leave the rest at
> their hardware default values.  That means we don't actually touch the
> upper half of the PAT table in the driver today and this patch won't
> have any functional effect [yet].
>
> Bspec: 44235
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>


Reviewed-by: Nirmoy Das<nirmoy.das@intel.com>

> ---
>   drivers/gpu/drm/xe/xe_pat.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pat.c b/drivers/gpu/drm/xe/xe_pat.c
> index 645eb20aea8e..a713afdd0510 100644
> --- a/drivers/gpu/drm/xe/xe_pat.c
> +++ b/drivers/gpu/drm/xe/xe_pat.c
> @@ -8,7 +8,9 @@
>   #include "xe_gt_mcr.h"
>   #include "xe_mmio.h"
>   
> -#define _PAT_INDEX(index)			(0x4800 + (index) * 4)
> +#define _PAT_INDEX(index)			_PICK_EVEN_2RANGES(index, 8, \
> +								   0x4800, 0x4804, \
> +								   0x4848, 0x484c)
>   
>   #define MTL_L4_POLICY_MASK			REG_GENMASK(3, 2)
>   #define MTL_PAT_3_UC				REG_FIELD_PREP(MTL_L4_POLICY_MASK, 3)

  reply	other threads:[~2023-03-24 21:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 21:04 [Intel-xe] [PATCH 0/6] PAT fixes Matt Roper
2023-03-24 21:04 ` [Intel-xe] [PATCH 1/6] drm/xe/pat: Move PAT setup to a dedicated file Matt Roper
2023-03-24 21:40   ` Das, Nirmoy
2023-03-24 21:04 ` [Intel-xe] [PATCH 2/6] drm/xe/pat: Use table-based programming of PAT settings Matt Roper
2023-03-24 21:44   ` Das, Nirmoy
2023-03-24 21:04 ` [Intel-xe] [PATCH 3/6] drm/xe/pat: Handle unicast vs MCR PAT registers Matt Roper
2023-03-24 21:36   ` Das, Nirmoy
2023-03-24 21:04 ` [Intel-xe] [PATCH 4/6] drm/xe/pat: Clean up PAT register definitions Matt Roper
2023-03-24 21:38   ` Das, Nirmoy
2023-03-24 21:04 ` [Intel-xe] [PATCH 5/6] drm/xe/mtl: Fix PAT table coherency settings Matt Roper
2023-03-24 21:34   ` Das, Nirmoy
2023-03-24 21:04 ` [Intel-xe] [PATCH 6/6] drm/xe/mtl: Handle PAT_INDEX offset jump Matt Roper
2023-03-24 21:34   ` Das, Nirmoy [this message]
2023-03-24 21:06 ` [Intel-xe] ✓ CI.Patch_applied: success for PAT fixes Patchwork
2023-03-24 21:07 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-24 21:11 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-24 21:33 ` [Intel-xe] ○ CI.BAT: info " 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=5e44e643-ae8d-cd40-5b67-e86758e7d120@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=intel-xe@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