All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, ville.syrjala@intel.com,
	santhosh.reddy.guddati@intel.com, jani.saarinen@intel.com
Subject: Re: [PATCH v6 0/7] drm/i915/xe3: FBC Dirty rect feature support
Date: Tue, 04 Feb 2025 11:09:31 +0200	[thread overview]
Message-ID: <875xlq6ppw.fsf@intel.com> (raw)
In-Reply-To: <20250130210027.591927-1-vinod.govindapillai@intel.com>

On Thu, 30 Jan 2025, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> Dirty rect support for FBC in xe3 onwards based on the comments after the
> initial RFC series.

I think "drm/i915/fbc" subject prefix is more appropriate than
"drm/i915/xe3".

(Please don't resend just for that.)

>
> v2: Dirty rect related compute and storage moved to fbc state (Ville)
>
> V3: Dont call fbc activate if FBC is already active
>
> v4: Dirty rect compute and programming moved within DSB scope
>     New changes are added as separate patches to make it easy for review
>     But could be squashed if the reviews as ok.
>
> v5: add HAS_FBC_DIRTY_RECT()
>     FBC Damage area updates in 3 steps. 
>     1. As part of plane_atomic_check() get, adjust coordinates and store
>        the merged damage area in plane_state
>     2. Atomic_commit, update merged damage are to fbc_state and prepare the
>        damage area satifying all conditions
>     3  update the FBC dirty rect registers as part of DSB commit.
>
> v6: Use dmage_merged helper earlier to handle bigjoiner cases (Ville)
>     Place the damage_merged handling code under HAS_FBC_DIRTY_RECT()
>     Added a variable to check if the damage_merged received from
>     the helper is valid. And if it is not valid, the FBC dirty rect
>     is updated with full plane reqion.
>
> Vinod Govindapillai (7):
>   drm/i915/xe3: add register definitions for fbc dirty rect support
>   drm/i915/xe3: introduce HAS_FBC_DIRTY_RECT() for FBC dirty rect
>     support
>   drm/damage-helper: add const qualifier in
>     drm_atomic_helper_damage_merged()
>   drm/i915/xe3: update and store the plane damage clips
>   drm/i915/xe3: dirty rect support for FBC
>   drm/i915/xe3: avoid calling fbc activate if fbc is active
>   drm/i915/xe3: disable FBC if PSR2 selective fetch is enabled
>
>  drivers/gpu/drm/drm_damage_helper.c           |   2 +-
>  .../gpu/drm/i915/display/intel_atomic_plane.c |  28 ++++
>  drivers/gpu/drm/i915/display/intel_display.c  |   7 +
>  .../drm/i915/display/intel_display_device.h   |   1 +
>  .../drm/i915/display/intel_display_types.h    |   2 +
>  drivers/gpu/drm/i915/display/intel_fbc.c      | 152 +++++++++++++++++-
>  drivers/gpu/drm/i915/display/intel_fbc.h      |   6 +
>  drivers/gpu/drm/i915/display/intel_fbc_regs.h |   9 ++
>  .../drm/i915/display/skl_universal_plane.c    |  45 +++++-
>  include/drm/drm_damage_helper.h               |   2 +-
>  10 files changed, 246 insertions(+), 8 deletions(-)

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2025-02-04  9:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 21:00 [PATCH v6 0/7] drm/i915/xe3: FBC Dirty rect feature support Vinod Govindapillai
2025-01-30 21:00 ` [PATCH v6 1/7] drm/i915/xe3: add register definitions for fbc dirty rect support Vinod Govindapillai
2025-02-05  9:42   ` Kandpal, Suraj
2025-01-30 21:00 ` [PATCH v6 2/7] drm/i915/xe3: introduce HAS_FBC_DIRTY_RECT() for FBC " Vinod Govindapillai
2025-02-05  9:43   ` Kandpal, Suraj
2025-01-30 21:00 ` [PATCH v6 3/7] drm/damage-helper: add const qualifier in drm_atomic_helper_damage_merged() Vinod Govindapillai
2025-02-04  9:08   ` Jani Nikula
2025-01-30 21:00 ` [PATCH v6 4/7] drm/i915/xe3: update and store the plane damage clips Vinod Govindapillai
2025-02-05  9:39   ` Kandpal, Suraj
2025-02-05 10:08     ` Jani Nikula
2025-02-05 11:21       ` Govindapillai, Vinod
2025-02-05 12:43   ` Ville Syrjälä
2025-02-05 13:29     ` Govindapillai, Vinod
2025-02-05 14:05       ` Ville Syrjälä
2025-01-30 21:00 ` [PATCH v6 5/7] drm/i915/xe3: dirty rect support for FBC Vinod Govindapillai
2025-02-05 13:31   ` Ville Syrjälä
2025-02-05 14:49     ` Govindapillai, Vinod
2025-02-05 15:45       ` Ville Syrjälä
2025-02-10 12:15         ` Govindapillai, Vinod
2025-02-10 21:49           ` Govindapillai, Vinod
2025-01-30 21:00 ` [PATCH v6 6/7] drm/i915/xe3: avoid calling fbc activate if fbc is active Vinod Govindapillai
2025-01-30 21:00 ` [PATCH v6 7/7] drm/i915/xe3: disable FBC if PSR2 selective fetch is enabled Vinod Govindapillai
2025-02-05  9:58   ` Kandpal, Suraj
2025-01-30 21:09 ` ✓ CI.Patch_applied: success for drm/i915/xe3: FBC Dirty rect feature support (rev7) Patchwork
2025-01-30 21:10 ` ✗ CI.checkpatch: warning " Patchwork
2025-01-30 21:11 ` ✓ CI.KUnit: success " Patchwork
2025-01-30 21:27 ` ✓ CI.Build: " Patchwork
2025-01-30 21:30 ` ✓ CI.Hooks: " Patchwork
2025-01-30 21:31 ` ✗ CI.checksparse: warning " Patchwork
2025-01-30 22:00 ` ✗ Fi.CI.CHECKPATCH: " Patchwork
2025-01-30 22:00 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-01-30 22:14 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-31  1:13 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-31  6:34 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-31  7:30 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-04  9:09 ` 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=875xlq6ppw.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=santhosh.reddy.guddati@intel.com \
    --cc=ville.syrjala@intel.com \
    --cc=vinod.govindapillai@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.