Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Uma Shankar <uma.shankar@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/3] drm/xe: Add wrapper function for VGA decode setup
Date: Tue, 19 Sep 2023 13:30:16 +0300	[thread overview]
Message-ID: <87h6nqtpzb.fsf@intel.com> (raw)
In-Reply-To: <20230918173711.625930-3-uma.shankar@intel.com>

On Mon, 18 Sep 2023, Uma Shankar <uma.shankar@intel.com> wrote:
> Some of the VGA functionality is not needed by the Intel
> Xe driver. Adding a wrapper function for VGA decode setup.
>
> Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> ---
>  drivers/gpu/drm/xe/display/ext/i915_utils.c | 5 +++++
>  drivers/gpu/drm/xe/xe_display.h             | 1 +
>  2 files changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/display/ext/i915_utils.c b/drivers/gpu/drm/xe/display/ext/i915_utils.c
> index 981edc2788bc..aa3e9ad718c3 100644
> --- a/drivers/gpu/drm/xe/display/ext/i915_utils.c
> +++ b/drivers/gpu/drm/xe/display/ext/i915_utils.c
> @@ -20,3 +20,8 @@ int __i915_inject_probe_error(struct drm_i915_private *i915, int err,
>  {
>  	return 0;
>  }
> +
> +unsigned int intel_gmch_vga_set_decode(struct pci_dev *pdev, bool enable_decode)
> +{
> +	return -EIO;
> +}

We don't really want to add anything new to i915_utils.c. It's just
temporary cruft that had to be taken from i915 to make the rest compile.

> diff --git a/drivers/gpu/drm/xe/xe_display.h b/drivers/gpu/drm/xe/xe_display.h
> index 03b7ea9268d4..d7a200e6ec30 100644
> --- a/drivers/gpu/drm/xe/xe_display.h
> +++ b/drivers/gpu/drm/xe/xe_display.h
> @@ -38,6 +38,7 @@ void xe_display_pm_suspend(struct xe_device *xe);
>  void xe_display_pm_suspend_late(struct xe_device *xe);
>  void xe_display_pm_resume_early(struct xe_device *xe);
>  void xe_display_pm_resume(struct xe_device *xe);
> +unsigned int intel_gmch_vga_set_decode(struct pci_dev *pdev, bool enable_decode);

We also don't want to add random declarations in xe_display.h either...

BR,
Jani.

>  
>  #else

-- 
Jani Nikula, Intel

  reply	other threads:[~2023-09-19 10:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 17:37 [Intel-xe] [PATCH 0/3] drm/xe: Make vga setup decode co-exist with Xe Uma Shankar
2023-09-18 17:37 ` [Intel-xe] [PATCH 1/3] drm/i915/display: Add a wrapper function for vga decode setup Uma Shankar
2023-09-19 10:26   ` Jani Nikula
2023-09-20  9:27     ` Shankar, Uma
2023-09-18 17:37 ` [Intel-xe] [PATCH 2/3] drm/xe: Add wrapper function for VGA " Uma Shankar
2023-09-19 10:30   ` Jani Nikula [this message]
2023-09-20  9:33     ` Shankar, Uma
2023-09-20 10:08       ` Jani Nikula
2023-09-20 12:39         ` Shankar, Uma
2023-09-21 12:00           ` Shankar, Uma
2023-09-21 12:18           ` Ville Syrjälä
2023-09-21 20:14             ` Shankar, Uma
2023-09-18 17:37 ` [Intel-xe] [PATCH 3/3] drm/i915: Use the wrapper function for vga " Uma Shankar
2023-09-18 18:10 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Make vga setup decode co-exist with Xe Patchwork
2023-09-18 18:11 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-18 18:12 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-18 18:15 ` [Intel-xe] ✗ CI.Build: failure " 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=87h6nqtpzb.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=uma.shankar@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