Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	uma.shankar@intel.com
Subject: Re: [PATCH] drm/i915: move intel_gmch.[ch] from soc/ to display/
Date: Thu, 13 Nov 2025 17:22:41 +0200	[thread overview]
Message-ID: <34d47b777e6aff9b60d95a90357d59c1f1f03aa0@intel.com> (raw)
In-Reply-To: <aRXi1-qchpRzONMd@intel.com>

On Thu, 13 Nov 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, Nov 13, 2025 at 03:37:50PM +0200, Jani Nikula wrote:
>> The sole user of the remaining functions in intel_gmch.[ch] is in
>> display. Move them under display.
>> 
>> This allows us to remove the compat soc/intel_gmch.h from xe.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/Makefile                           | 5 +----
>>  drivers/gpu/drm/i915/{soc => display}/intel_gmch.c      | 3 +--
>>  drivers/gpu/drm/i915/{soc => display}/intel_gmch.h      | 0
>>  drivers/gpu/drm/i915/display/intel_vga.c                | 3 +--
>>  drivers/gpu/drm/xe/compat-i915-headers/soc/intel_gmch.h | 6 ------
>>  5 files changed, 3 insertions(+), 14 deletions(-)
>>  rename drivers/gpu/drm/i915/{soc => display}/intel_gmch.c (95%)
>>  rename drivers/gpu/drm/i915/{soc => display}/intel_gmch.h (100%)
>>  delete mode 100644 drivers/gpu/drm/xe/compat-i915-headers/soc/intel_gmch.h
>> 
>> diff --git a/drivers/gpu/drm/i915/Makefile b/drivers/gpu/drm/i915/Makefile
>> index 90588d5bb908..98822c98d960 100644
>> --- a/drivers/gpu/drm/i915/Makefile
>> +++ b/drivers/gpu/drm/i915/Makefile
>> @@ -57,10 +57,6 @@ i915-y += \
>>  	vlv_iosf_sb.o \
>>  	vlv_suspend.o
>>  
>> -# core peripheral code
>> -i915-y += \
>> -	soc/intel_gmch.o
>> -
>>  # core library code
>>  i915-y += \
>>  	i915_memcpy.o \
>> @@ -280,6 +276,7 @@ i915-y += \
>>  	display/intel_flipq.o \
>>  	display/intel_frontbuffer.o \
>>  	display/intel_global_state.o \
>> +	display/intel_gmch.o \
>
> I think I'd just stick the stuff into intel_vga.c since 
> that's where the vgaarb registration is as well.

Moving this directly to intel_vga.c requires a bunch of in-flight
modifications, because currently it's not compiled for xe, and there's a
dummy implementation of intel_gmch_vga_set_decode(). Or I have to wrap
#ifdef I915 around it or something.

See "[PATCH] drm/xe: use the same vga decode code as i915". If that
regresses, it's trivial to revert that, but if I do that as part of
moving the function to intel_vga.c, it's all mixed up.

Having this in intel_vga.c is the pleasing end result, but none of the
paths there are pleasing. Pick your poison, I guess.


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-11-13 15:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13  9:57 [PATCH 0/8] drm/i915: start dissolving soc/ Jani Nikula
2025-11-13  9:57 ` [PATCH 1/8] drm/i915/edram: extract i915_edram.[ch] for edram detection Jani Nikula
2025-11-13  9:57 ` [PATCH 2/8] drm/i915: split out i915_freq.[ch] Jani Nikula
2025-11-13  9:58 ` [PATCH 3/8] drm/i915: move intel_dram.[ch] from soc/ to display/ Jani Nikula
2025-11-13  9:58 ` [PATCH 4/8] drm/xe: remove MISSING_CASE() from compat i915_utils.h Jani Nikula
2025-11-13  9:58 ` [PATCH 5/8] drm/i915/dram: convert to struct intel_display Jani Nikula
2025-11-13 13:39   ` Ville Syrjälä
2025-11-13 13:45     ` Jani Nikula
2025-11-13  9:58 ` [PATCH 6/8] drm/i915: move dram_info " Jani Nikula
2025-11-13  9:58 ` [PATCH 7/8] drm/i915: move intel_rom.[ch] from soc/ to display/ Jani Nikula
2025-11-13  9:58 ` [PATCH 8/8] drm/xe: remove remaining platform checks from compat i915_drv.h Jani Nikula
2025-11-13 13:29 ` [PATCH 0/8] drm/i915: start dissolving soc/ Jani Nikula
2025-11-13 13:44   ` Jani Nikula
2025-11-13 13:37 ` [PATCH] drm/i915/gmch: split out i915_gmch.[ch] from soc Jani Nikula
2025-11-13 13:37 ` [PATCH] drm/i915: move intel_gmch.[ch] from soc/ to display/ Jani Nikula
2025-11-13 13:53   ` Ville Syrjälä
2025-11-13 15:22     ` Jani Nikula [this message]
2025-11-13 13:37 ` [PATCH] drm/i915/gmch: convert intel_gmch.c to struct intel_display Jani Nikula
2025-11-13 13:38 ` [PATCH] drm/i915/gmch: find bridge device locally Jani Nikula
2025-11-13 15:08   ` Ville Syrjälä
2025-11-13 15:26     ` Jani Nikula
2025-11-13 13:38 ` [PATCH] drm/xe: use the same vga decode code as i915 Jani Nikula
2025-11-14 22:23   ` kernel test robot
2025-11-13 23:21 ` ✗ i915.CI.BAT: failure for " 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=34d47b777e6aff9b60d95a90357d59c1f1f03aa0@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@linux.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