Re: [Intel-xe] [PATCH] drm/i915/rps: split out display rps parts to a separate file

[Jani Nikula <jani.nikula@intel.com>]

On Wed, 22 Mar 2023, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> I believe the easiest way will be to remove the display portion of the
> initial mega-squash and create a display only patch/series and make that
> separated.
>
> Also starting to think to leave display out for the initial merge of Xe.
> Then add display later.

This does have a certain appeal to it.

We have 260+ commits on top of the current drm-tip baseline in
drm-xe-next. The vast majority of them are pure xe, unrelated to display
integration in any way. Most people are working on things not related to
display.

Cleaning up the display integration could use a heavy handed rebasing
and refactoring of the display changes, both the xe and i915 changes. It
would be easier if the display developers had more of a free hand with
force pushes, without distracting the rest, i.e. have a
drm-xe-display-next branch or something, regularly rebased on top of
drm-xe-next.

I'd imagine the goal would be to keep the display integration ready to
merge, with the display pull request immediately following the initial
merge of xe.

Now, the big problem with this, of course, is splitting up the display
parts from drm-xe-next and the individual commits there, in a way that
still leaves us with a decent base for the display branch. Basically how
to have new drm-xe-next + new drm-xe-display-next == old drm-xe-next.


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center