From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
"Suraj Kandpal" <suraj.kandpal@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v4] drm/i915: split out display register macros to a separate file
Date: Mon, 09 Jun 2025 13:26:55 +0300 [thread overview]
Message-ID: <ce5c6405b693f85edc17cdf6ae93e1c2e72fd9f9@intel.com> (raw)
In-Reply-To: <cqww6aekcmcy7h3mlttlp6v3udmxw2yh6hlzbhz2dnpmanbkda@lbuwmw2i7bcg>
On Fri, 06 Jun 2025, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Jun 06, 2025 at 01:22:56PM +0300, Jani Nikula wrote:
>>This is a scripted split of the display related register macros from
>>i915_reg.h to display/intel_display_regs.h. As a starting point, move
>>all the macros that are only used in display code (or GVT). If there are
>>users in core i915 code or soc/, or no users anywhere, keep the macros
>>in i915_reg.h. This is done in groups of macros separated by blank
>>lines, moving the comments along with the groups.
>>
>>Some manually picked macro groups are kept/moved regardless of the
>>heuristics above.
>>
>>This is obviously a very crude approach. It's not perfect. But there are
>>4.2k lines in i915_reg.h, and its refactoring has ground to a halt. This
>>is the big hammer that splits the file to two, and enables further
>>cleanup.
>>
>>Cc: Suraj Kandpal <suraj.kandpal@intel.com>
>>Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> I skimmed over the registers and didn't spot non-display related ones.
> For the code move, there are a few unrelated changes due to sorting the
> includes, but that should be fine as it's easier to just sort the block.
>
> Changes in drivers/gpu/drm/i915/display/intel_display_regs.h indeed come
> verbatim from the other file, as colored by git show --color-moved.
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> Let's get this in before it conflicts again.
Thanks for the review. It's not perfect, but I think it's good enough to
make forward progress. Pushed to din.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-06-09 10:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 10:22 [PATCH v4] drm/i915: split out display register macros to a separate file Jani Nikula
2025-06-06 10:28 ` ✓ CI.Patch_applied: success for drm/i915: split out display register macros to a separate file (rev2) Patchwork
2025-06-06 10:29 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-06 10:30 ` ✓ CI.KUnit: success " Patchwork
2025-06-06 10:41 ` ✓ CI.Build: " Patchwork
2025-06-06 10:43 ` ✓ CI.Hooks: " Patchwork
2025-06-06 10:45 ` ✓ CI.checksparse: " Patchwork
2025-06-06 11:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-06 14:49 ` [PATCH v4] drm/i915: split out display register macros to a separate file Lucas De Marchi
2025-06-09 10:26 ` Jani Nikula [this message]
2025-06-08 13:56 ` ✗ Xe.CI.Full: failure for drm/i915: split out display register macros to a separate file (rev2) 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=ce5c6405b693f85edc17cdf6ae93e1c2e72fd9f9@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=suraj.kandpal@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