From: sashiko-bot@kernel.org
To: "Timur Kristóf" <timur.kristof@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/amd/display: Don't use tiling flags anymore
Date: Wed, 22 Jul 2026 17:34:53 +0000 [thread overview]
Message-ID: <20260722173453.CF3FA1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260722165925.15805-5-timur.kristof@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing 2D tiling format modifier for 8 bpp formats on GFX6-8 breaks NV12/NV21 video playback.
--
--- Patch [4]: [PATCH 4/4] drm/amd/display: Don't use tiling flags anymore ---
commit 9ecc330329837cba2c5f2f431e911a3b7ec6c4df
Author: Timur Kristóf <timur.kristof@gmail.com>
Subject: drm/amd/display: Don't use tiling flags anymore
The commit removes the usage of legacy tiling flags from the amdgpu_dm
display code, transitioning all supported GPU generations to rely
completely on DRM format modifiers. It updates plane attribute filling,
surface updates, and cursor checks to reflect this change.
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.c
> index a593a44ef97bc..87187c965d55c 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.c
[ ... ]
> @@ -1235,8 +1201,6 @@ int amdgpu_dm_plane_fill_plane_buffer_attributes(struct amdgpu_device *adev,
> address);
> if (ret)
> return ret;
> - } else if (afb->base.modifier == DRM_FORMAT_MOD_INVALID) {
> - amdgpu_dm_plane_fill_gfx8_tiling_info_from_flags(tiling_info, tiling_flags);
> } else {
> ret = amdgpu_dm_plane_fill_gfx6_tiling_info_from_modifier(tiling_info,
> afb->base.modifier);
[Severity: High]
By removing the legacy tiling flags fallback here, does this break NV12/NV21
video playback on GFX6-8?
Looking at amdgpu_dm_plane_add_gfx6_modifiers(), it appears to add 2D tiled
modifiers only for 16, 32, and 64 bpp:
amdgpu_dm_plane_add_modifier(mods, size, capacity,
amdgpu_dm_plane_calc_gfx6_mod(adev, 16, DC_ARRAY_2D_TILED_THIN1));
amdgpu_dm_plane_add_modifier_dedup(mods, size, capacity,
amdgpu_dm_plane_calc_gfx6_mod(adev, 32, DC_ARRAY_2D_TILED_THIN1));
amdgpu_dm_plane_add_modifier_dedup(mods, size, capacity,
amdgpu_dm_plane_calc_gfx6_mod(adev, 64, DC_ARRAY_2D_TILED_THIN1));
Since the modifier calculation for 8 bpp (which is required for NV12/NV21
formats) is missing, when userspace allocates a 2D-tiled NV12 framebuffer,
won't drm_plane_check_pixel_format() reject the atomic commit since it
cannot find the 8bpp modifier in the plane's advertised list?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722165925.15805-1-timur.kristof@gmail.com?part=4
next prev parent reply other threads:[~2026-07-22 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 16:59 [PATCH 0/4] drm/amdgpu: Support DRM format modifiers on GFX6-8 (v4) Timur Kristóf
2026-07-22 16:59 ` [PATCH 1/4] drm/fourcc: Add modifiers for AMD GFX6-8 Timur Kristóf
2026-07-22 16:59 ` [PATCH 2/4] drm/amdgpu: Convert tiling flags to modifiers on GFX6-8 Timur Kristóf
2026-07-22 16:59 ` [PATCH 3/4] drm/amd/display: Support DRM format " Timur Kristóf
2026-07-22 16:59 ` [PATCH 4/4] drm/amd/display: Don't use tiling flags anymore Timur Kristóf
2026-07-22 17:34 ` sashiko-bot [this message]
2026-07-27 15:44 ` Alex Deucher
2026-07-27 16:04 ` Alex Deucher
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 14:24 [PATCH 0/4] drm/amdgpu: Support DRM format modifiers on GFX6-8 (v3) Timur Kristóf
2026-07-20 14:24 ` [PATCH 4/4] drm/amd/display: Don't use tiling flags anymore Timur Kristóf
2026-07-20 15:00 ` sashiko-bot
2026-07-15 10:57 [PATCH 0/4] drm/amdgpu: Support DRM format modifiers on GFX6-8 (v2) Timur Kristóf
2026-07-15 10:57 ` [PATCH 4/4] drm/amd/display: Don't use tiling flags anymore Timur Kristóf
2026-07-15 11:42 ` sashiko-bot
2026-07-15 20:12 ` Timur Kristóf
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=20260722173453.CF3FA1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=timur.kristof@gmail.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