From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <dev@lankhorst.se>, intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
Maarten Lankhorst <dev@lankhorst.se>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 0/5] drm/xe/display: Rework display init for reducing flickering.
Date: Mon, 09 Dec 2024 12:39:13 +0200 [thread overview]
Message-ID: <871pyh16pa.fsf@intel.com> (raw)
In-Reply-To: <20241206185956.3290-1-dev@lankhorst.se>
On Fri, 06 Dec 2024, Maarten Lankhorst <dev@lankhorst.se> wrote:
> I have rebased the previous series and took out the GuC parts. This makes it a lot easier to review missing parts,
> and not be dependent on GuC loading changes for merging.
I think all of the patches need more explanations in the commit
messages. Why are we doing this? Why is this okay? How does this work
with the plans to unify display code between i915 and xe, especially wrt
the init ordering and the expectations on irqs.
BR,
Jani.
>
> Maarten Lankhorst (5):
> drm/xe/display: Add intel_plane_initial_vblank_wait
> drm/xe: Remove double pageflip
> drm/xe: Move suballocator init to after display init
> drm/xe: Defer irq init until after xe_display_init_noaccel
> drm/xe/display: Use a single early init call for display
>
> drivers/gpu/drm/i915/display/intel_display.c | 6 +-
> .../drm/i915/display/intel_plane_initial.c | 7 +-
> .../drm/i915/display/intel_plane_initial.h | 2 +
> drivers/gpu/drm/xe/display/xe_display.c | 71 +++++--------------
> drivers/gpu/drm/xe/display/xe_display.h | 8 +--
> drivers/gpu/drm/xe/display/xe_plane_initial.c | 29 +++++---
> drivers/gpu/drm/xe/xe_device.c | 28 +++-----
> drivers/gpu/drm/xe/xe_tile.c | 19 +++--
> drivers/gpu/drm/xe/xe_tile.h | 1 +
> 9 files changed, 77 insertions(+), 94 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-09 10:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 18:59 [PATCH 0/5] drm/xe/display: Rework display init for reducing flickering Maarten Lankhorst
2024-12-06 18:59 ` [PATCH 1/5] drm/xe/display: Add intel_plane_initial_vblank_wait Maarten Lankhorst
2024-12-06 18:59 ` [PATCH 2/5] drm/xe: Remove double pageflip Maarten Lankhorst
2024-12-06 18:59 ` [PATCH 3/5] drm/xe: Move suballocator init to after display init Maarten Lankhorst
2024-12-06 18:59 ` [PATCH 4/5] drm/xe: Defer irq init until after xe_display_init_noaccel Maarten Lankhorst
2024-12-09 11:17 ` [PATCH v2] " Maarten Lankhorst
2024-12-06 18:59 ` [PATCH 5/5] drm/xe/display: Use a single early init call for display Maarten Lankhorst
2024-12-09 15:51 ` [PATCH] " Maarten Lankhorst
2024-12-10 9:35 ` Jani Nikula
2024-12-11 18:32 ` Maarten Lankhorst
2024-12-12 14:27 ` Rodrigo Vivi
2024-12-06 20:37 ` ✓ CI.Patch_applied: success for drm/xe/display: Rework display init for reducing flickering Patchwork
2024-12-06 20:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-06 20:39 ` ✓ CI.KUnit: success " Patchwork
2024-12-06 20:57 ` ✓ CI.Build: " Patchwork
2024-12-06 20:59 ` ✓ CI.Hooks: " Patchwork
2024-12-06 21:00 ` ✓ CI.checksparse: " Patchwork
2024-12-06 21:24 ` ✗ Xe.CI.BAT: failure " Patchwork
2024-12-07 1:36 ` ✗ Xe.CI.Full: " Patchwork
2024-12-09 10:39 ` Jani Nikula [this message]
2024-12-09 14:33 ` ✗ CI.Patch_applied: failure for drm/xe/display: Rework display init for reducing flickering. (rev2) Patchwork
2024-12-09 15:56 ` ✓ CI.Patch_applied: success for drm/xe/display: Rework display init for reducing flickering. (rev3) Patchwork
2024-12-09 15:56 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-09 15:58 ` ✓ CI.KUnit: success " Patchwork
2024-12-09 16:16 ` ✓ CI.Build: " Patchwork
2024-12-09 16:18 ` ✓ CI.Hooks: " Patchwork
2024-12-09 16:20 ` ✓ CI.checksparse: " Patchwork
2024-12-09 16:37 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-09 17:32 ` ✗ Xe.CI.Full: failure " 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=871pyh16pa.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).