All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [RFC v1 0/4] Update VRR guardband for HRR panel
Date: Fri, 22 Nov 2024 09:53:02 +0200	[thread overview]
Message-ID: <Z0A4XvcYDJ3jeI9a@intel.com> (raw)
In-Reply-To: <20241112085039.1258860-1-mitulkumar.ajitkumar.golani@intel.com>

On Tue, Nov 12, 2024 at 02:20:35PM +0530, Mitul Golani wrote:
> Compute guardband based on enabled feature latency.
> 

We already have some of this stuff in skl_wm_check_vblank().
But it's missing some of scaler/dsc/etc. prefill stuff. That is
the place where all this needs to be checked.

> Mitul Golani (4):
>   drm/i915/scaler: Calculate scaler prefill latency
>   drm/i915/watermark: Add WM0 prefill latency
>   drm/i915/psr: Add latency for PSR
>   display/vrr: Update guardband based on enabled latency
> 
>  drivers/gpu/drm/i915/display/intel_psr.c     | 23 ++++++++++++
>  drivers/gpu/drm/i915/display/intel_psr.h     |  1 +
>  drivers/gpu/drm/i915/display/intel_vrr.c     | 18 ++++++++-
>  drivers/gpu/drm/i915/display/skl_scaler.c    | 39 ++++++++++++++++++++
>  drivers/gpu/drm/i915/display/skl_scaler.h    |  1 +
>  drivers/gpu/drm/i915/display/skl_watermark.c | 21 +++++++++++
>  drivers/gpu/drm/i915/display/skl_watermark.h |  1 +
>  7 files changed, 102 insertions(+), 2 deletions(-)
> 
> -- 
> 2.46.0

-- 
Ville Syrjälä
Intel

      parent reply	other threads:[~2024-11-22  7:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  8:50 [RFC v1 0/4] Update VRR guardband for HRR panel Mitul Golani
2024-11-12  8:50 ` [RFC v1 1/4] drm/i915/scaler: Calculate scaler prefill latency Mitul Golani
2024-11-28  9:31   ` Garg, Nemesa
2024-11-12  8:50 ` [RFC v1 2/4] drm/i915/watermark: Add WM0 " Mitul Golani
2024-11-12  8:50 ` [RFC v1 3/4] drm/i915/psr: Add latency for PSR Mitul Golani
2024-11-12  8:50 ` [RFC v1 4/4] display/vrr: Update guardband based on enabled latency Mitul Golani
2024-11-12  9:31 ` ✓ CI.Patch_applied: success for Update VRR guardband for HRR panel Patchwork
2024-11-12  9:31 ` ✓ CI.checkpatch: " Patchwork
2024-11-12  9:32 ` ✓ CI.KUnit: " Patchwork
2024-11-12  9:44 ` ✓ CI.Build: " Patchwork
2024-11-12  9:46 ` ✓ CI.Hooks: " Patchwork
2024-11-12  9:47 ` ✗ CI.checksparse: warning " Patchwork
2024-11-12 10:21 ` ✓ CI.BAT: success " Patchwork
2024-11-12 10:51 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-11-12 11:05 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-12 11:30 ` ✗ CI.FULL: " Patchwork
2024-11-22  7:53 ` Ville Syrjälä [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=Z0A4XvcYDJ3jeI9a@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mitulkumar.ajitkumar.golani@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.