Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, Lucas De Marchi <lucas.demarchi@intel.com>,
	dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	David Airlie <airlied@gmail.com>
Subject: [Intel-gfx] [PATCH 01/19] drm/i915: define I915 during i915 driver build
Date: Tue, 12 Sep 2023 14:06:28 +0300	[thread overview]
Message-ID: <97558201836115b91cbe32840239df855d0c2e4c.1694514689.git.jani.nikula@intel.com> (raw)
In-Reply-To: <cover.1694514689.git.jani.nikula@intel.com>

The xe driver will reuse i915 display code by compiling it separately as
part of xe. We'll want to be able to distinguish between building the
i915 display code for i915 and xe. Define I915 when building i915.

Cc: David Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel@ffwll.ch>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
 drivers/gpu/drm/i915/Makefile | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/gpu/drm/i915/Makefile b/drivers/gpu/drm/i915/Makefile
index 1b2e02e9d92c..fa6aa71bb749 100644
--- a/drivers/gpu/drm/i915/Makefile
+++ b/drivers/gpu/drm/i915/Makefile
@@ -28,6 +28,10 @@ CFLAGS_i915_pci.o = $(call cc-disable-warning, override-init)
 CFLAGS_display/intel_display_device.o = $(call cc-disable-warning, override-init)
 CFLAGS_display/intel_fbdev.o = $(call cc-disable-warning, override-init)
 
+# Support compiling the display code separately for both i915 and xe
+# drivers. Define I915 when building i915.
+subdir-ccflags-y += -DI915
+
 subdir-ccflags-y += -I$(srctree)/$(src)
 
 # Please keep these build lists sorted!
-- 
2.39.2


  reply	other threads:[~2023-09-12 11:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 11:06 [Intel-gfx] [PATCH 00/19] drm/i915: prepare for xe driver display integration Jani Nikula
2023-09-12 11:06 ` Jani Nikula [this message]
2023-09-12 11:06 ` [Intel-gfx] [PATCH 02/19] drm/i915/display: add I915 conditional build to intel_lvds.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 03/19] drm/i915/display: add I915 conditional build to hsw_ips.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 04/19] drm/i915/display: add I915 conditional build to i9xx_plane.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 05/19] drm/i915/display: add I915 conditional build to intel_lpe_audio.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 06/19] drm/i915/display: add I915 conditional build to intel_pch_refclk.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 07/19] drm/i915/display: add I915 conditional build to intel_pch_display.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 08/19] drm/i915/display: add I915 conditional build to intel_sprite.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 09/19] drm/i915/display: add I915 conditional build to intel_overlay.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 10/19] drm/i915/display: add I915 conditional build to g4x_dp.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 11/19] drm/i915/display: add I915 conditional build to intel_dpio_phy.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 12/19] drm/i915/display: add I915 conditional build to intel_crt.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 13/19] drm/i915/display: add I915 conditional build to vlv_dsi.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 14/19] drm/i915/display: add I915 conditional build to i9xx_wm.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 15/19] drm/i915/display: add I915 conditional build to g4x_hdmi.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 16/19] drm/i915/display: add I915 conditional build to intel_dvo.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 17/19] drm/i915/display: add I915 conditional build to intel_sdvo.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 18/19] drm/i915/display: add I915 conditional build to intel_tv.h Jani Nikula
2023-09-12 11:06 ` [Intel-gfx] [PATCH 19/19] drm/i915/display: add I915 conditional build to vlv_dsi_pll.h Jani Nikula
2023-09-12 19:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: prepare for xe driver display integration Patchwork
2023-09-12 19:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-12 19:30 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-13 20:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: prepare for xe driver display integration (rev2) Patchwork
2023-09-13 20:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-13 20:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-14  0:53 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-14 14:53 ` [Intel-gfx] [PATCH 00/19] drm/i915: prepare for xe driver display integration Rodrigo Vivi
2023-09-29 11:03   ` Jani Nikula

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=97558201836115b91cbe32840239df855d0c2e4c.1694514689.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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