From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/3] drm/i915/fbc: update the supported FP16 formats
Date: Tue, 27 Oct 2026 14:48:12 +0200 [thread overview]
Message-ID: <auCdjLxz021c2xmT@intel.com> (raw)
In-Reply-To: <9d4f394e56e08def3c9b837291f4e09eb3a2f4b1.camel@intel.com>
On Tue, Oct 27, 2026 at 09:06:58AM +0000, Govindapillai, Vinod wrote:
> On Mon, 2026-10-26 at 17:15 +0200, Ville Syrjälä wrote:
> > 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.
> Ok. I will list all the formats as it is.
>
> But pixel normalizer need to be enabled for fp16 formats, I think, it
> is better to group those as a separate reusable function. are you ok
> with that?
Hmm. I thought the format_info thing has a .is_float already, but
apparently not. We could add that. But in the meantime just a
some format_is_float() function should do.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2026-10-27 12:48 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 ` [PATCH v2 1/3] drm/i915/fbc: update the supported " Ville Syrjälä
2026-10-27 9:06 ` Govindapillai, Vinod
2026-10-27 12:48 ` Ville Syrjälä [this message]
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=auCdjLxz021c2xmT@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