From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [v6 0/3] Fix cursor FB unpinning.
Date: Thu, 30 May 2024 17:44:28 +0300 [thread overview]
Message-ID: <87le3rgy0j.fsf@intel.com> (raw)
In-Reply-To: <20240522053341.137592-1-maarten.lankhorst@linux.intel.com>
On Wed, 22 May 2024, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> Hopefully last attempt.
> Small bug in drm_vblank_work_flush_all left, fixed now hopefully.
Acked-by: Jani Nikula <jani.nikula@intel.com>
for merging via drm-misc, but drm-intel is also fine by me. No big deal
this time of the cycle when we can get the backmerge fairly quickly.
>
> Maarten Lankhorst (2):
> drm: Add drm_vblank_work_flush_all().
> drm/i915: Use the same vblank worker for atomic unpin
>
> Ville Syrjälä (1):
> drm/i915: Use vblank worker to unpin old legacy cursor fb safely
>
> drivers/gpu/drm/drm_vblank_work.c | 22 +++++++++++++
> .../gpu/drm/i915/display/intel_atomic_plane.c | 13 +++++++-
> .../gpu/drm/i915/display/intel_atomic_plane.h | 2 ++
> drivers/gpu/drm/i915/display/intel_crtc.c | 31 +++++++++++++++++++
> drivers/gpu/drm/i915/display/intel_cursor.c | 26 ++++++++++++++--
> drivers/gpu/drm/i915/display/intel_cursor.h | 3 ++
> drivers/gpu/drm/i915/display/intel_display.c | 3 ++
> .../drm/i915/display/intel_display_types.h | 3 ++
> include/drm/drm_vblank_work.h | 2 ++
> 9 files changed, 102 insertions(+), 3 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-05-30 14:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 5:33 [v6 0/3] Fix cursor FB unpinning Maarten Lankhorst
2024-05-22 5:33 ` [v6 1/3] drm: Add drm_vblank_work_flush_all() Maarten Lankhorst
2024-05-28 7:37 ` Shankar, Uma
2024-05-22 5:33 ` [v6 2/3] drm/i915: Use vblank worker to unpin old legacy cursor fb safely Maarten Lankhorst
2024-05-28 7:51 ` Shankar, Uma
2024-05-22 5:33 ` [v6 3/3] drm/i915: Use the same vblank worker for atomic unpin Maarten Lankhorst
2024-05-28 7:56 ` Shankar, Uma
2024-05-22 6:01 ` ✓ CI.Patch_applied: success for Fix cursor FB unpinning Patchwork
2024-05-22 6:01 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-22 6:02 ` ✓ CI.KUnit: success " Patchwork
2024-05-22 6:14 ` ✓ CI.Build: " Patchwork
2024-05-22 6:16 ` ✓ CI.Hooks: " Patchwork
2024-05-22 6:17 ` ✗ CI.checksparse: warning " Patchwork
2024-05-22 6:20 ` ✗ Fi.CI.CHECKPATCH: " Patchwork
2024-05-22 6:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-05-22 6:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-05-22 6:58 ` ✓ CI.BAT: success " Patchwork
2024-05-22 8:05 ` ✓ Fi.CI.BAT: " Patchwork
2024-05-22 9:40 ` ✗ CI.FULL: failure " Patchwork
2024-05-22 18:28 ` ✗ Fi.CI.IGT: " Patchwork
2024-05-28 8:01 ` [v6 0/3] " Shankar, Uma
2024-05-28 9:54 ` ✗ Fi.CI.CHECKPATCH: warning for Fix cursor FB unpinning. (rev2) Patchwork
2024-05-28 9:54 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-05-28 10:02 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-29 2:30 ` ✓ Fi.CI.IGT: " Patchwork
2024-05-30 12:53 ` ✗ Fi.CI.BUILD: failure for Fix cursor FB unpinning. (rev3) Patchwork
2024-05-30 14:44 ` 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=87le3rgy0j.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.