public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 3/4] drm/i915/gvt: drop dependency on intel_display_types.h
Date: Thu, 29 Jan 2026 10:01:52 +0530	[thread overview]
Message-ID: <8132cd5e-9592-418b-b065-4146ba2e80da@intel.com> (raw)
In-Reply-To: <2fa5677f5ff3dbeaa75a7984d74fb9855a4ba3d2.1769612208.git.jani.nikula@intel.com>


On 1/28/2026 8:29 PM, Jani Nikula wrote:
> Avoid even accidental use of display details by dropping the include of
> intel_display_types.h. We'll still have to include intel_dpll_mgt.h for


s/intel_dpll_mgt.h/intel_dpll_mgr.h

Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>


> the DPLL IDs, but at least the surface is smaller.
>
> Add duplicate defines of pipe_name() and port_name() to avoid depending
> on display. They're trivial enough to be acceptable.
>
> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>   drivers/gpu/drm/i915/gvt/handlers.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gvt/handlers.c b/drivers/gpu/drm/i915/gvt/handlers.c
> index 383b04160559..6f860c320afc 100644
> --- a/drivers/gpu/drm/i915/gvt/handlers.c
> +++ b/drivers/gpu/drm/i915/gvt/handlers.c
> @@ -46,10 +46,10 @@
>   #include "display/intel_crt_regs.h"
>   #include "display/intel_cursor_regs.h"
>   #include "display/intel_display_regs.h"
> -#include "display/intel_display_types.h"
>   #include "display/intel_dmc_regs.h"
>   #include "display/intel_dp_aux_regs.h"
>   #include "display/intel_dpio_phy.h"
> +#include "display/intel_dpll_mgr.h"
>   #include "display/intel_fbc.h"
>   #include "display/intel_fdi_regs.h"
>   #include "display/intel_pps_regs.h"
> @@ -79,6 +79,9 @@
>   #define PCH_PP_OFF_DELAYS _MMIO(0xc720c)
>   #define PCH_PP_DIVISOR _MMIO(0xc7210)
>   
> +#define pipe_name(p) ((p) + 'A')
> +#define port_name(p) ((p) + 'A')
> +
>   unsigned long intel_gvt_get_device_type(struct intel_gvt *gvt)
>   {
>   	struct drm_i915_private *i915 = gvt->gt->i915;

  reply	other threads:[~2026-01-29  4:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 14:59 [PATCH 0/4] drm/i915/gvt: further reduce dependency on display Jani Nikula
2026-01-28 14:59 ` [PATCH 1/4] drm/i915/display: move enum aux_ch to intel_display_limits.h Jani Nikula
2026-01-29  3:02   ` Kandpal, Suraj
2026-01-29  4:22   ` Nautiyal, Ankit K
2026-01-28 14:59 ` [PATCH 2/4] drm/i915/gvt: drop dependency on display struct dpll Jani Nikula
2026-01-29  4:24   ` Nautiyal, Ankit K
2026-01-28 14:59 ` [PATCH 3/4] drm/i915/gvt: drop dependency on intel_display_types.h Jani Nikula
2026-01-29  4:31   ` Nautiyal, Ankit K [this message]
2026-01-29  8:46     ` Jani Nikula
2026-01-28 14:59 ` [PATCH 4/4] drm/i915/gvt: drop unnecessary include of intel_display.h Jani Nikula
2026-01-29  4:36   ` Nautiyal, Ankit K
2026-01-28 16:48 ` ✓ i915.CI.BAT: success for drm/i915/gvt: further reduce dependency on display Patchwork
2026-01-28 22:01 ` ✓ i915.CI.Full: " 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=8132cd5e-9592-418b-b065-4146ba2e80da@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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