Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
To: intel-xe@lists.freedesktop.org, janga.rahul.kumar@intel.com,
	ramadevi.gandi@intel.com
Cc: matthew.d.roper@intel.com, lucas.demarchi@intel.com
Subject: [PATCH v5 1/2] drm/xe: Relocate regs_are_mcr function
Date: Sat,  4 May 2024 01:09:01 +0530	[thread overview]
Message-ID: <20240503193902.2056202-2-janga.rahul.kumar@intel.com> (raw)
In-Reply-To: <20240503193902.2056202-1-janga.rahul.kumar@intel.com>

Relocate regs_are_mcr funciton to a higher position in the file
for improved visibility.

Cc: Matt Roper <matthew.d.roper@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Janga Rahul Kumar <janga.rahul.kumar@intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
 drivers/gpu/drm/xe/xe_mocs.c | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_mocs.c b/drivers/gpu/drm/xe/xe_mocs.c
index 1e92f8ee07ba..aef09eb423e9 100644
--- a/drivers/gpu/drm/xe/xe_mocs.c
+++ b/drivers/gpu/drm/xe/xe_mocs.c
@@ -255,6 +255,16 @@ static const struct xe_mocs_entry gen12_mocs_desc[] = {
 		   L3_1_UC)
 };
 
+static bool regs_are_mcr(struct xe_gt *gt)
+{
+	struct xe_device *xe = gt_to_xe(gt);
+
+	if (xe_gt_is_media_type(gt))
+		return MEDIA_VER(xe) >= 20;
+	else
+		return GRAPHICS_VERx100(xe) >= 1250;
+}
+
 static const struct xe_mocs_entry dg1_mocs_desc[] = {
 	/* UC */
 	MOCS_ENTRY(1, 0, L3_1_UC),
@@ -467,16 +477,6 @@ static u32 get_entry_control(const struct xe_mocs_info *info,
 	return info->table[info->unused_entries_index].control_value;
 }
 
-static bool regs_are_mcr(struct xe_gt *gt)
-{
-	struct xe_device *xe = gt_to_xe(gt);
-
-	if (xe_gt_is_media_type(gt))
-		return MEDIA_VER(xe) >= 20;
-	else
-		return GRAPHICS_VERx100(xe) >= 1250;
-}
-
 static void __init_mocs_table(struct xe_gt *gt,
 			      const struct xe_mocs_info *info)
 {
-- 
2.25.1


  reply	other threads:[~2024-05-03 19:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 19:39 [PATCH v5 0/2] drm/xe/mocs: Add debugfs node to dump mocs Janga Rahul Kumar
2024-05-03 19:39 ` Janga Rahul Kumar [this message]
2024-05-03 19:39 ` [PATCH v5 2/2] " Janga Rahul Kumar
2024-05-06 14:48   ` Lucas De Marchi
2024-05-04  0:16 ` ✓ CI.Patch_applied: success for drm/xe/mocs: Add debugfs node to dump mocs (rev5) Patchwork
2024-05-04  0:17 ` ✓ CI.checkpatch: " Patchwork
2024-05-04  0:18 ` ✓ CI.KUnit: " Patchwork
2024-05-04  0:31 ` ✓ CI.Build: " Patchwork
2024-05-04  0:34 ` ✓ CI.Hooks: " Patchwork
2024-05-04  0:36 ` ✓ CI.checksparse: " Patchwork
2024-05-04  1:29 ` ✗ CI.BAT: failure " Patchwork
2024-05-04  5:45 ` ✓ CI.Patch_applied: success for drm/xe/mocs: Add debugfs node to dump mocs (rev6) Patchwork
2024-05-04  5:45 ` ✓ CI.checkpatch: " Patchwork
2024-05-04  5:46 ` ✓ CI.KUnit: " Patchwork
2024-05-04  5:58 ` ✓ CI.Build: " Patchwork
2024-05-04  6:00 ` ✓ CI.Hooks: " Patchwork
2024-05-04  6:02 ` ✓ CI.checksparse: " Patchwork
2024-05-04  6:35 ` ✓ CI.BAT: " Patchwork
2024-05-06  7:13 ` ✓ CI.FULL: success for drm/xe/mocs: Add debugfs node to dump mocs (rev5) Patchwork
2024-05-06  7:18 ` ✗ CI.FULL: failure for drm/xe/mocs: Add debugfs node to dump mocs (rev6) Patchwork
2024-05-06 16:34 ` [PATCH v5 0/2] drm/xe/mocs: Add debugfs node to dump mocs Lucas De Marchi

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=20240503193902.2056202-2-janga.rahul.kumar@intel.com \
    --to=janga.rahul.kumar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=ramadevi.gandi@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