Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [RFC 1/3] drm/i915: Add wrapper for xe compatibility
Date: Mon, 18 Sep 2023 17:32:27 +0530	[thread overview]
Message-ID: <20230918120229.338270-2-chaitanya.kumar.borah@intel.com> (raw)
In-Reply-To: <20230918120229.338270-1-chaitanya.kumar.borah@intel.com>

Add a wrapper around intel_step_name to maintain compatibility
with xe driver. The wrapper will share the same name as the one
to be used by xe while both drivers include different files as
needed during compilation.

Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Signed-off-by: Animesh Manna <animesh.manna@intel.com>
---
 drivers/gpu/drm/i915/intel_step.c | 5 +++++
 drivers/gpu/drm/i915/intel_step.h | 1 +
 2 files changed, 6 insertions(+)

diff --git a/drivers/gpu/drm/i915/intel_step.c b/drivers/gpu/drm/i915/intel_step.c
index c02a6f156a00..6b62b5fcc792 100644
--- a/drivers/gpu/drm/i915/intel_step.c
+++ b/drivers/gpu/drm/i915/intel_step.c
@@ -352,3 +352,8 @@ const char *intel_step_name(enum intel_step step)
 		return "**";
 	}
 }
+
+const char *intel_get_step_name(struct drm_i915_private *i915)
+{
+	return intel_step_name(RUNTIME_INFO(i915)->step.display_step);
+}
diff --git a/drivers/gpu/drm/i915/intel_step.h b/drivers/gpu/drm/i915/intel_step.h
index 96dfca4cba73..25a1b1948a43 100644
--- a/drivers/gpu/drm/i915/intel_step.h
+++ b/drivers/gpu/drm/i915/intel_step.h
@@ -78,5 +78,6 @@ enum intel_step {
 
 void intel_step_init(struct drm_i915_private *i915);
 const char *intel_step_name(enum intel_step step);
+const char *intel_get_step_name(struct drm_i915_private *i915);
 
 #endif /* __INTEL_STEP_H__ */
-- 
2.25.1


  reply	other threads:[~2023-09-18 12:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 12:02 [Intel-xe] [RFC 0/3] Use common wrapper to get step name Chaitanya Kumar Borah
2023-09-18 12:02 ` Chaitanya Kumar Borah [this message]
2023-09-18 12:02 ` [Intel-xe] [RFC 2/3] drm/xe: Add wrapper over intel_step_name Chaitanya Kumar Borah
2023-09-19 14:04   ` Jani Nikula
2023-09-20  7:24     ` Borah, Chaitanya Kumar
2023-09-18 12:02 ` [Intel-xe] [RFC 3/3] drm/i915/dmc: Use common wrapper to get step name Chaitanya Kumar Borah
2023-09-18 14:17 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-09-18 14:17 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-18 14:18 ` [Intel-xe] ✗ CI.KUnit: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-09-20  7:16 [Intel-xe] [RFC 0/3] " Chaitanya Kumar Borah
2023-09-20  7:16 ` [Intel-xe] [RFC 1/3] drm/i915: Add wrapper for xe compatibility Chaitanya Kumar Borah
2023-09-20  9:52   ` Jani Nikula
2023-10-05  4:34     ` Borah, Chaitanya Kumar

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=20230918120229.338270-2-chaitanya.kumar.borah@intel.com \
    --to=chaitanya.kumar.borah@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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