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, intel-xe@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, uma.shankar@intel.com
Subject: Re: [PATCH 0/8] drm/i915: start dissolving soc/
Date: Thu, 13 Nov 2025 15:44:53 +0200	[thread overview]
Message-ID: <dc52de2ad62897a90672497b04b1a3dbed3087ab@intel.com> (raw)
In-Reply-To: <85590237a138e9a6acbd53a8e9ec96cf76dd8078@intel.com>

On Thu, 13 Nov 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> On Thu, 13 Nov 2025, Jani Nikula <jani.nikula@intel.com> wrote:
>> soc/ has served a useful purpose, and way back when it was the obvious
>> thing to do. However, it has become a bit awkward, sitting somewhere
>> between i915, xe and display.
>>
>> Split the i915 core specific parts out of intel_dram.c, and move
>> intel_dram.c and intel_rom.c under display. This allows us to clean up
>> the xe build and compat headers very nicely.
>>
>> intel_gmch.[ch] still remains under soc/, as it requires a bit more
>> thought. But this series is a good start.
>
> After a discussion with Ville, I've got this figured out and the patches
> ready as well.

Sent the patches in-reply-to the cover letter for review, though it'll
probably confuse CI and b4. :)


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-11-13 13:44 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 [this message]
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
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=dc52de2ad62897a90672497b04b1a3dbed3087ab@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