From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/i915/fbc: update the supported FP16 formats
Date: Mon, 26 Oct 2026 17:15:32 +0200 [thread overview]
Message-ID: <at9ulGJlfF6ImWOl@intel.com> (raw)
In-Reply-To: <20261026145508.235851-1-vinod.govindapillai@intel.com>
On Mon, Oct 26, 2026 at 04:55:06PM +0200, Vinod Govindapillai wrote:
> FBC is supported with FP16 formats with or without alpha. At the
> same time modify the function name for the FP16 format check and
> simplify the FP16 format check calls.
>
> Bspec: 68904
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fbc.c | 21 +++++++--------------
> 1 file changed, 7 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> index 5694d20773f8..dbb16a9ec69d 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> @@ -1180,14 +1180,15 @@ static bool lnl_fbc_pixel_format_is_valid(const struct intel_plane_state *plane_
> }
> }
>
> -static bool
> -xe3p_lpd_fbc_fp16_format_is_valid(const struct intel_plane_state *plane_state)
> +static bool intel_fbc_is_fp16_format(const struct intel_plane_state *plane_state)
> {
> const struct drm_framebuffer *fb = plane_state->hw.fb;
>
> switch (fb->format->format) {
> case DRM_FORMAT_ARGB16161616F:
> + case DRM_FORMAT_XRGB16161616F:
> case DRM_FORMAT_ABGR16161616F:
> + case DRM_FORMAT_XBGR16161616F:
> return true;
> default:
> return false;
> @@ -1196,24 +1197,16 @@ xe3p_lpd_fbc_fp16_format_is_valid(const struct intel_plane_state *plane_state)
>
> static bool xe3p_lpd_fbc_pixel_format_is_valid(const struct intel_plane_state *plane_state)
> {
> - if (lnl_fbc_pixel_format_is_valid(plane_state))
> - return true;
> -
> - if (xe3p_lpd_fbc_fp16_format_is_valid(plane_state))
> - return true;
> -
> - return false;
> + return lnl_fbc_pixel_format_is_valid(plane_state) ||
> + intel_fbc_is_fp16_format(plane_state);
This is getting super messy. Would be much simpler to just list
the actual supported pixel formats here instead of trying to
this hard to follow inheritance thing.
> }
>
> bool intel_fbc_need_pixel_normalizer(const struct intel_plane_state *plane_state)
> {
> struct intel_display *display = to_intel_display(plane_state);
>
> - if (HAS_PIXEL_NORMALIZER(display) &&
> - xe3p_lpd_fbc_fp16_format_is_valid(plane_state))
> - return true;
> -
> - return false;
> + return HAS_PIXEL_NORMALIZER(display) &&
> + intel_fbc_is_fp16_format(plane_state);
> }
>
> static bool pixel_format_is_valid(const struct intel_plane_state *plane_state)
> --
> 2.43.0
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-10-26 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 14:55 [PATCH v2 1/3] drm/i915/fbc: update the supported FP16 formats Vinod Govindapillai
2026-10-26 14:55 ` [PATCH v2 2/3] drm/i915/fbc: Apply Wa_14028723391 Vinod Govindapillai
2026-10-26 14:55 ` [PATCH v2 3/3] drm/i915/fbc: update pixel normalizer condition for FBC FP16 formats Vinod Govindapillai
2026-10-26 15:15 ` Ville Syrjälä [this message]
2026-10-27 9:06 ` [PATCH v2 1/3] drm/i915/fbc: update the supported " Govindapillai, Vinod
2026-10-27 12:48 ` Ville Syrjälä
2026-10-26 15:38 ` ✓ CI.KUnit: success for series starting with [v2,1/3] " Patchwork
2026-10-26 16:15 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-26 20:23 ` ✓ Xe.CI.FULL: " 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=at9ulGJlfF6ImWOl@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox