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 v3] drm/i915: split out display register macros to a separate file
Date: Fri, 06 Jun 2025 12:59:37 +0300 [thread overview]
Message-ID: <c3e3c1e35d933b4bec911e78ec1af494e5aa3c40@intel.com> (raw)
In-Reply-To: <ipmzkkad7742bmgeessnbwz5or43wup5j73y7j6bwvxbgst2k5@pgu2bxyol2so>
On Thu, 05 Jun 2025, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Wed, Jun 04, 2025 at 02:02:25PM +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.
>
> I wonder if with this we couldn't end up moving wrong registers.
> Maybe we should double check the address range too?
I think at this point aiming for perfection in the split is already
blocking progress.
It's been almost four months since I posted this first, and I've mostly
just been polishing the 300+ lines of python/bash scripts to do
this. And that's all for a one time change, after which the scripts are
useless.
We could've merged the first version, fixed the issues in the following
months, and we would be ahead.
IMO just getting the first split done is the most important part,
because 4k lines is impossible to navigate manually.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-06-06 9:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 11:02 [PATCH v3] drm/i915: split out display register macros to a separate file Jani Nikula
2025-06-04 12:09 ` ✓ CI.Patch_applied: success for " Patchwork
2025-06-04 12:09 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-04 12:11 ` ✓ CI.KUnit: success " Patchwork
2025-06-04 12:21 ` ✓ CI.Build: " Patchwork
2025-06-04 12:24 ` ✓ CI.Hooks: " Patchwork
2025-06-04 12:25 ` ✓ CI.checksparse: " Patchwork
2025-06-04 13:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-05 7:59 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-05 12:42 ` [PATCH v3] " Jani Nikula
2025-06-05 15:34 ` Lucas De Marchi
2025-06-06 9:59 ` Jani Nikula [this message]
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=c3e3c1e35d933b4bec911e78ec1af494e5aa3c40@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