From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: dri-devel@lists.freedesktop.org,
"André Almeida" <andrealmeid@igalia.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Simon Ser" <contact@emersion.fr>,
intel-gfx@lists.freedesktop.org,
"Maxime Ripard" <mripard@kernel.org>,
"Melissa Wen" <mwen@igalia.com>,
"VMware Graphics Reviewers"
<linux-graphics-maintainer@vmware.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Christian König" <christian.koenig@amd.com>,
"Zack Rusin" <zackr@vmware.com>
Subject: Re: [Intel-gfx] [PATCH 3/5] drm/i915: Remove redundant framebuffer format check
Date: Thu, 12 Jan 2023 17:15:36 +0200 [thread overview]
Message-ID: <Y8AkGO/N2z2/XsEz@intel.com> (raw)
In-Reply-To: <345279ff-680a-52ac-73ed-29e2ab84f0ae@igalia.com>
On Thu, Jan 12, 2023 at 11:07:59AM -0300, Maíra Canal wrote:
> Hi,
>
> On 1/12/23 09:43, Ville Syrjälä wrote:
> > On Mon, Jan 09, 2023 at 07:58:06AM -0300, Maíra Canal wrote:
> >> Now that framebuffer_check() verifies that the format is properly
> >> supported, there is no need to check it again on i915's inside
> >> helpers.
> >>
> >> Therefore, remove the redundant framebuffer format check from the
> >> intel_framebuffer_init() function, letting framebuffer_check()
> >> perform the framebuffer validation.
> >>
> >> Signed-off-by: Maíra Canal <mcanal@igalia.com>
> >> ---
> >> drivers/gpu/drm/i915/display/intel_fb.c | 9 ---------
> >> 1 file changed, 9 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/display/intel_fb.c b/drivers/gpu/drm/i915/display/intel_fb.c
> >> index 63137ae5ab21..230b729e42d6 100644
> >> --- a/drivers/gpu/drm/i915/display/intel_fb.c
> >> +++ b/drivers/gpu/drm/i915/display/intel_fb.c
> >> @@ -1914,15 +1914,6 @@ int intel_framebuffer_init(struct intel_framebuffer *intel_fb,
> >> }
> >> }
> >>
> >> - if (!drm_any_plane_has_format(&dev_priv->drm,
> >> - mode_cmd->pixel_format,
> >> - mode_cmd->modifier[0])) {
> >> - drm_dbg_kms(&dev_priv->drm,
> >> - "unsupported pixel format %p4cc / modifier 0x%llx\n",
> >> - &mode_cmd->pixel_format, mode_cmd->modifier[0]);
> >> - goto err;
> >> - }
> >> -
> >
> > This doesn't work for the legacy tiling->modifier path.
>
> Do you have any idea on how we could remove drm_any_plane_has_format() from
> i915? Or is it strictly necessary to validate the modifier in the legacy
> path?
I guess techinically we could skip it by knowing that X-tile is always
supported. However that may not hold in the future so not a soution I
really like. Also the drm_any_plane_has_format() call from
framebuffer_check() is too early, so instead of checking X-tile
vs. linear based on the tiling it's going to always assume linear.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-01-12 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:58 [Intel-gfx] [PATCH 0/5] Check for valid framebuffer's format Maíra Canal
2023-01-09 10:58 ` [Intel-gfx] [PATCH 1/5] drm/framebuffer: Check for valid formats Maíra Canal
2023-01-11 22:48 ` Daniel Vetter
2023-01-09 10:58 ` [Intel-gfx] [PATCH 2/5] drm/amdgpu: Remove redundant framebuffer format check Maíra Canal
2023-01-12 12:17 ` Simon Ser
2023-01-09 10:58 ` [Intel-gfx] [PATCH 3/5] drm/i915: " Maíra Canal
2023-01-12 12:18 ` Simon Ser
2023-01-12 12:43 ` Ville Syrjälä
2023-01-12 14:07 ` Maíra Canal
2023-01-12 15:15 ` Ville Syrjälä [this message]
2023-01-09 10:58 ` [Intel-gfx] [PATCH 4/5] drm/vmwgfx: " Maíra Canal
2023-01-12 2:52 ` Zack Rusin
2023-01-09 10:58 ` [Intel-gfx] [PATCH 5/5] drm/plane: Unexport drm_any_plane_has_format() Maíra Canal
2023-01-11 22:50 ` Daniel Vetter
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=Y8AkGO/N2z2/XsEz@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=andrealmeid@igalia.com \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=rodrigo.vivi@intel.com \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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