Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Chauhan, Shekhar" <shekhar.chauhan@intel.com>
To: Matt Atwood <matthew.s.atwood@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: Haridhar Kalvala <haridhar.kalvala@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [PATCH 4/6] drm/xe/ptl: PTL re-uses Xe2 MOCS table
Date: Tue, 8 Oct 2024 18:49:02 +0530	[thread overview]
Message-ID: <fdcfe5a1-a875-499a-b46b-630c3516dd2c@intel.com> (raw)
In-Reply-To: <20241008013509.61233-5-matthew.s.atwood@intel.com>


On 10/8/2024 7:05, Matt Atwood wrote:
> From: Haridhar Kalvala <haridhar.kalvala@intel.com>
>
> PTL is Xe3 architecture but there is no difference between LNL and PTL
> in MOCS table.  So, PTL uses the same MOCS table as LNL.
>
> Bpsec: 71582

Also, similar to another review by Matt Roper on Patch 5/6, we can 
remove the empty line here below the BSpec. There appears to be a typo 
as well. But yes, patch itself LGTM. The RB is already present below, 
adding it again

Reviewed-by: Shekhar Chauhan <shekhar.chauhan@intel.com>

>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Shekhar Chauhan <shekhar.chauhan@intel.com>
> Signed-off-by: Haridhar Kalvala <haridhar.kalvala@intel.com>
> Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> Reviewed-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_mocs.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_mocs.c b/drivers/gpu/drm/xe/xe_mocs.c
> index 8df41cd12d51..231d0e86ed83 100644
> --- a/drivers/gpu/drm/xe/xe_mocs.c
> +++ b/drivers/gpu/drm/xe/xe_mocs.c
> @@ -576,6 +576,7 @@ static unsigned int get_mocs_settings(struct xe_device *xe,
>   	memset(info, 0, sizeof(struct xe_mocs_info));
>   
>   	switch (xe->info.platform) {
> +	case XE_PANTHERLAKE:
>   	case XE_LUNARLAKE:
>   	case XE_BATTLEMAGE:
>   		info->ops = &xe2_mocs_ops;

-- 
-shekhar


  reply	other threads:[~2024-10-08 13:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  1:35 [PATCH 0/6 v3] Add Xe3 and Panther Lake support Matt Atwood
2024-10-08  1:35 ` [PATCH 1/6] drm/xe/xe3: Xe3 uses the same PAT settings as Xe2 Matt Atwood
2024-10-08  1:35 ` [PATCH 2/6] drm/xe/xe3: Define Xe3 feature flags Matt Atwood
2024-10-08  2:23   ` Chauhan, Shekhar
2024-10-08 16:15     ` Matt Roper
2024-10-08 17:49       ` Chauhan, Shekhar
2024-10-08 18:06         ` Matt Roper
2024-10-08 18:28           ` Chauhan, Shekhar
2024-10-08  1:35 ` [PATCH 3/6] drm/xe/xe3: Add initial set of workarounds Matt Atwood
2024-10-08 13:46   ` Chauhan, Shekhar
2024-10-08 16:17   ` Matt Roper
2024-10-08  1:35 ` [PATCH 4/6] drm/xe/ptl: PTL re-uses Xe2 MOCS table Matt Atwood
2024-10-08 13:19   ` Chauhan, Shekhar [this message]
2024-10-08  1:35 ` [PATCH 5/6] drm/xe/ptl: Add PTL platform definition Matt Atwood
2024-10-08 13:25   ` Chauhan, Shekhar
2024-10-08  1:35 ` [PATCH 6/6] drm/xe/xe3lpm: Add new "instance0" steering table Matt Atwood
2024-10-08  1:40 ` ✓ CI.Patch_applied: success for Add Xe3 and Panther Lake support (rev3) Patchwork
2024-10-08  1:40 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-08  1:41 ` ✓ CI.KUnit: success " Patchwork
2024-10-08  1:53 ` ✓ CI.Build: " Patchwork
2024-10-08  1:56 ` ✓ CI.Hooks: " Patchwork
2024-10-08  1:58 ` ✓ CI.checksparse: " Patchwork
2024-10-08  2:23 ` ✓ CI.BAT: " Patchwork
2024-10-08 10:01 ` ✗ CI.FULL: failure " Patchwork
2024-10-08 16:26   ` Matt Roper
2024-10-08 16:08 ` [PATCH 0/6 v3] Add Xe3 and Panther Lake support Matt Roper
  -- strict thread matches above, loose matches on Subject: below --
2024-10-04 22:05 [PATCH 0/6] " Matt Atwood
2024-10-04 22:05 ` [PATCH 4/6] drm/xe/ptl: PTL re-uses Xe2 MOCS table Matt Atwood

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=fdcfe5a1-a875-499a-b46b-630c3516dd2c@intel.com \
    --to=shekhar.chauhan@intel.com \
    --cc=haridhar.kalvala@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=matthew.s.atwood@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