From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [RFC 2/3] drm/xe: Add wrapper over intel_step_name
Date: Tue, 19 Sep 2023 17:04:31 +0300 [thread overview]
Message-ID: <87y1h2s1hs.fsf@intel.com> (raw)
In-Reply-To: <20230918120229.338270-3-chaitanya.kumar.borah@intel.com>
On Mon, 18 Sep 2023, Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com> wrote:
> To maintain compatibility between xe and i915, let's create a
> wrapper with same name over driver specific calls made to
> retrieve the step name.
>
> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/xe/xe_step.c | 5 +++++
> drivers/gpu/drm/xe/xe_step.h | 1 +
These files must not have references to struct drm_i915_private.
Try building with CONFIG_DRM_XE_DISPLAY=n.
BR,
Jani.
> 2 files changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_step.c b/drivers/gpu/drm/xe/xe_step.c
> index 371cac951e0f..9a79451ccf52 100644
> --- a/drivers/gpu/drm/xe/xe_step.c
> +++ b/drivers/gpu/drm/xe/xe_step.c
> @@ -254,3 +254,8 @@ const char *xe_step_name(enum xe_step step)
> return "**";
> }
> }
> +
> +const char *intel_get_step_name(struct drm_i915_private *i915)
> +{
> + return xe_step_name(i915->info.step.display);
> +}
> diff --git a/drivers/gpu/drm/xe/xe_step.h b/drivers/gpu/drm/xe/xe_step.h
> index a384b640f2af..3e78d46566a0 100644
> --- a/drivers/gpu/drm/xe/xe_step.h
> +++ b/drivers/gpu/drm/xe/xe_step.h
> @@ -17,5 +17,6 @@ struct xe_step_info xe_step_gmdid_get(struct xe_device *xe,
> u32 graphics_gmdid_revid,
> u32 media_gmdid_revid);
> const char *xe_step_name(enum xe_step step);
> +const char *intel_get_step_name(struct drm_i915_private *i915);
>
> #endif
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-09-19 14:05 UTC|newest]
Thread overview: 10+ 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 ` [Intel-xe] [RFC 1/3] drm/i915: Add wrapper for xe compatibility Chaitanya Kumar Borah
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 [this message]
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 2/3] drm/xe: Add wrapper over intel_step_name Chaitanya Kumar Borah
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=87y1h2s1hs.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=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 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.