From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
uma.shankar@intel.com
Subject: Re: [PATCH 2/2] drm/i915/display: Don't wait for vblank for LUT DSB programming
Date: Fri, 28 Feb 2025 18:31:42 +0200 [thread overview]
Message-ID: <Z8Hk7sSnEyyj1Rtf@intel.com> (raw)
In-Reply-To: <20250225180905.1588084-3-chaitanya.kumar.borah@intel.com>
On Tue, Feb 25, 2025 at 11:39:05PM +0530, Chaitanya Kumar Borah wrote:
> >From PTL, LUT registers are made double buffered. With this change,
> we don't need to wait for vblank to program them. Start DSB1 for
> programming them without waiting for vblank.
>
> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 919e236a9650..9c3fdfcd6759 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -7352,6 +7352,7 @@ static void intel_atomic_dsb_finish(struct intel_atomic_state *state,
> {
> struct intel_crtc_state *new_crtc_state =
> intel_atomic_get_new_crtc_state(state, crtc);
> + struct intel_display *display = to_intel_display(state);
>
> if (!new_crtc_state->use_dsb && !new_crtc_state->dsb_color_vblank)
> return;
> @@ -7408,7 +7409,8 @@ static void intel_atomic_dsb_finish(struct intel_atomic_state *state,
>
> if (new_crtc_state->dsb_color_vblank)
> intel_dsb_chain(state, new_crtc_state->dsb_commit,
> - new_crtc_state->dsb_color_vblank, true);
> + new_crtc_state->dsb_color_vblank,
> + HAS_DOUBLE_BUFFERED_LUT(display) ? false : true);
Using chaining for this is a bit ugly. GOSUB would seem more
appropriate. Here's a quick 1h effort to implement the basics
for that (completely untested):
https://github.com/vsyrjala/linux.git dsb_gosub
>
> intel_dsb_finish(new_crtc_state->dsb_commit);
> }
> --
> 2.25.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-02-28 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 18:09 [PATCH 0/2] drm/xe/display: Program double buffered LUT registers Chaitanya Kumar Borah
2025-02-25 18:09 ` [PATCH 1/2] drm/i915/display: Add MMIO path for double-buffered " Chaitanya Kumar Borah
2025-02-28 15:14 ` Ville Syrjälä
2025-03-04 14:43 ` Borah, Chaitanya Kumar
2025-03-04 15:49 ` Ville Syrjälä
2025-04-02 15:39 ` Borah, Chaitanya Kumar
2025-02-25 18:09 ` [PATCH 2/2] drm/i915/display: Don't wait for vblank for LUT DSB programming Chaitanya Kumar Borah
2025-02-27 12:40 ` Jani Nikula
2025-03-04 14:07 ` Borah, Chaitanya Kumar
2025-02-28 16:31 ` Ville Syrjälä [this message]
2025-03-04 14:31 ` Borah, Chaitanya Kumar
2025-03-19 12:18 ` Borah, Chaitanya Kumar
2025-02-27 17:52 ` ✗ Fi.CI.SPARSE: warning for drm/xe/display: Program double buffered LUT registers (rev4) Patchwork
2025-02-27 18:08 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-28 3:42 ` ✗ i915.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=Z8Hk7sSnEyyj1Rtf@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@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).