From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: [FOR CI 0/4] drm/xe: Fix initial framebuffer handover.
Date: Fri, 18 Oct 2024 14:11:19 +0200 [thread overview]
Message-ID: <20241018121123.5351-1-maarten.lankhorst@linux.intel.com> (raw)
Should be good enough to remove flickering, but does it pass CI?
Maarten Lankhorst (4):
drm/xe: Remove double pageflip
drm/i915/display: Use async flip when available for initial plane
config
drm/xe: Move suballocator init to after display init
drm/xe: Initialise display before GT and tile init
.../drm/i915/display/skl_universal_plane.c | 13 +++++-
drivers/gpu/drm/xe/display/xe_plane_initial.c | 10 -----
drivers/gpu/drm/xe/xe_device.c | 43 +++++++++++++------
drivers/gpu/drm/xe/xe_gt.c | 12 ++++++
drivers/gpu/drm/xe/xe_gt.h | 1 +
drivers/gpu/drm/xe/xe_tile.c | 12 ++++--
drivers/gpu/drm/xe/xe_tile.h | 1 +
7 files changed, 62 insertions(+), 30 deletions(-)
--
2.45.2
next reply other threads:[~2024-10-18 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 12:11 Maarten Lankhorst [this message]
2024-10-18 12:11 ` [FOR CI 1/4] drm/xe: Remove double pageflip Maarten Lankhorst
2024-10-18 12:11 ` [FOR CI 2/4] drm/i915/display: Use async flip when available for initial plane config Maarten Lankhorst
2024-10-18 12:11 ` [FOR CI 3/4] drm/xe: Move suballocator init to after display init Maarten Lankhorst
2024-10-18 12:11 ` [FOR CI 4/4] drm/xe: Initialise display before GT and tile init Maarten Lankhorst
2024-10-18 12:16 ` ✓ CI.Patch_applied: success for drm/xe: Fix initial framebuffer handover Patchwork
2024-10-18 12:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-18 12:17 ` ✓ CI.KUnit: success " Patchwork
2024-10-18 12:29 ` ✓ CI.Build: " Patchwork
2024-10-18 12:31 ` ✓ CI.Hooks: " Patchwork
2024-10-18 12:33 ` ✗ CI.checksparse: warning " Patchwork
2024-10-18 12:53 ` ✗ CI.BAT: failure " Patchwork
2024-10-19 3:58 ` ✗ CI.FULL: " 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=20241018121123.5351-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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