From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane
Date: Thu, 27 Aug 2026 15:15:46 +0530 [thread overview]
Message-ID: <c0fcd686-3f10-4919-8bf3-3eb320d8669e@intel.com> (raw)
In-Reply-To: <20260821044755.2234490-3-nemesa.garg@intel.com>
On 8/21/2026 10:17 AM, Nemesa Garg wrote:
> Move cursor fast path plane state update into helper
> function. The target hw.crtc is passed as a parameter
> so a later patch can reuse the helper for joiner
> secondary pipes, where hw.crtc points at the secondary
> being programmed while uapi.crtc stays on the primary.
>
> v4: Drop uapi.crtc assignment from the helper. [Chaitanya]
LGTM
Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>
> Assisted-by: Claude:claude-sonnet-4.6
> Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_cursor.c | 39 ++++++++++++++-------
> 1 file changed, 27 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_cursor.c b/drivers/gpu/drm/i915/display/intel_cursor.c
> index bc1e58d5c4c5..db4eaa74fc58 100644
> --- a/drivers/gpu/drm/i915/display/intel_cursor.c
> +++ b/drivers/gpu/drm/i915/display/intel_cursor.c
> @@ -840,6 +840,29 @@ intel_cursor_joiner_commits_idle(struct intel_display *display,
> return true;
> }
>
> +static void
> +intel_cursor_fastpath_update_plane_state(struct intel_plane_state *plane_state,
> + struct drm_framebuffer *fb,
> + struct intel_crtc *hw_crtc,
> + int crtc_x, int crtc_y,
> + unsigned int crtc_w, unsigned int crtc_h,
> + u32 src_x, u32 src_y,
> + u32 src_w, u32 src_h)
> +{
> + drm_atomic_set_fb_for_plane(&plane_state->uapi, fb);
> +
> + plane_state->uapi.src_x = src_x;
> + plane_state->uapi.src_y = src_y;
> + plane_state->uapi.src_w = src_w;
> + plane_state->uapi.src_h = src_h;
> + plane_state->uapi.crtc_x = crtc_x;
> + plane_state->uapi.crtc_y = crtc_y;
> + plane_state->uapi.crtc_w = crtc_w;
> + plane_state->uapi.crtc_h = crtc_h;
> +
> + intel_plane_copy_uapi_to_hw_state(NULL, plane_state, plane_state, hw_crtc);
> +}
> +
> static int
> intel_legacy_cursor_update(struct drm_plane *_plane,
> struct drm_crtc *_crtc,
> @@ -915,18 +938,10 @@ intel_legacy_cursor_update(struct drm_plane *_plane,
> goto out_free;
> }
>
> - drm_atomic_set_fb_for_plane(&new_plane_state->uapi, fb);
> -
> - new_plane_state->uapi.src_x = src_x;
> - new_plane_state->uapi.src_y = src_y;
> - new_plane_state->uapi.src_w = src_w;
> - new_plane_state->uapi.src_h = src_h;
> - new_plane_state->uapi.crtc_x = crtc_x;
> - new_plane_state->uapi.crtc_y = crtc_y;
> - new_plane_state->uapi.crtc_w = crtc_w;
> - new_plane_state->uapi.crtc_h = crtc_h;
> -
> - intel_plane_copy_uapi_to_hw_state(NULL, new_plane_state, new_plane_state, crtc);
> + intel_cursor_fastpath_update_plane_state(new_plane_state, fb,
> + crtc,
> + crtc_x, crtc_y, crtc_w, crtc_h,
> + src_x, src_y, src_w, src_h);
>
> ret = intel_plane_atomic_check_with_state(crtc_state, new_crtc_state,
> old_plane_state, new_plane_state);
next prev parent reply other threads:[~2026-08-27 9:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 4:47 [PATCH 0/6] Enable joiner cursor fast updates Nemesa Garg
2026-08-21 4:47 ` [PATCH 1/6] drm/i915/cursor: Check joiner cursor commit status Nemesa Garg
2026-08-27 9:45 ` Borah, Chaitanya Kumar
2026-08-21 4:47 ` [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane Nemesa Garg
2026-08-27 9:45 ` Borah, Chaitanya Kumar [this message]
2026-08-21 4:47 ` [PATCH 3/6] drm/i915/cursor: Handle secondary cursor state Nemesa Garg
2026-08-27 9:45 ` Borah, Chaitanya Kumar
2026-08-21 4:47 ` [PATCH 4/6] drm/i915/cursor: Program secondary cursor planes Nemesa Garg
2026-08-27 9:46 ` Borah, Chaitanya Kumar
2026-08-21 4:47 ` [PATCH 5/6] drm/i915/cursor: Schedule cursor unpin per joined pipe Nemesa Garg
2026-08-27 9:46 ` Borah, Chaitanya Kumar
2026-08-21 4:47 ` [PATCH 6/6] drm/i915/cursor: Allow joiner cursor fast path update Nemesa Garg
2026-08-27 9:46 ` Borah, Chaitanya Kumar
2026-08-21 5:49 ` ✓ i915.CI.BAT: success for Enable joiner cursor fast updates (rev6) Patchwork
2026-08-21 9:05 ` ✗ i915.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-08-18 8:42 [PATCH 0/6] Enable joiner cursor fast updates Nemesa Garg
2026-08-18 8:42 ` [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane Nemesa Garg
2026-07-06 11:56 [PATCH 0/6] Enable joiner cursor fast updates Nemesa Garg
2026-07-06 11:56 ` [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane Nemesa Garg
2026-06-08 6:26 [PATCH 0/6] Enable joiner cursor fast updates Nemesa Garg
2026-06-08 6:26 ` [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane Nemesa Garg
2026-07-01 16:26 ` Borah, Chaitanya Kumar
2026-07-06 8:40 ` Garg, Nemesa
2026-04-28 14:16 [PATCH 0/6] Enable joiner cursor fast updates Nemesa Garg
2026-04-28 14:16 ` [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane Nemesa Garg
2026-04-22 7:37 [PATCH 0/6] Enable joiner cursor fast updates Nemesa Garg
2026-04-22 7:37 ` [PATCH 2/6] drm/i915/cursor: Add helper to update cursor plane Nemesa Garg
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=c0fcd686-3f10-4919-8bf3-3eb320d8669e@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nemesa.garg@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