dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 20 Jul 2026 15:00:28 +0000	[thread overview]
Message-ID: <20260720150029.5EA371F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260720142440.22076-5-timur.kristof@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] KUnit tests fail to compile and execute due to un-updated function signatures and test logic.
--

--- Patch [4]: [PATCH 4/4] drm/amd/display: Don't use tiling flags anymore ---
commit d732188b7192db7cd4cbe5558fd7f9823861ddf2
Author: Timur Kristóf <timur.kristof@gmail.com>

drm/amd/display: Don't use tiling flags anymore

All supported GPU generations now support DRM format modifiers.
Remove all code from amdgpu_dm that dealt with tiling flags.

> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.h b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.h
> index 365e306a52e78..2b9b5f2507377 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.h
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_plane.h
> @@ -48,7 +48,6 @@ int amdgpu_dm_plane_fill_plane_buffer_attributes(struct amdgpu_device *adev,
>  				 const struct amdgpu_framebuffer *afb,
>  				 const enum surface_pixel_format format,
>  				 const enum dc_rotation_angle rotation,
> -				 const uint64_t tiling_flags,
>  				 struct dc_tiling_info *tiling_info,
>  				 struct plane_size *plane_size,

[Severity: Low]
Were the remaining KUnit tests in amdgpu_dm_plane_test.c updated to reflect
this signature change?

When compiling with CONFIG_DRM_AMD_DC_KUNIT_TEST=y, there appear to be build
failures because functions like dm_test_fill_plane_buffer_attributes_gfx8()
and dm_test_plane_attrs() still pass the extra tiling_flags (or 0) argument.

For example, in dm_test_fill_plane_buffer_attributes_gfx8():

	ret = amdgpu_dm_plane_fill_plane_buffer_attributes(adev, afb,
		SURFACE_PIXEL_FORMAT_GRPH_ARGB8888, ROTATION_ANGLE_0,
		tiling_flags, tiling_info, plane_size, dcc, address, true);

Additionally, does the test logic in
dm_test_fill_plane_buffer_attributes_gfx8() need to be updated to populate
afb->base.modifier instead of the removed tiling_flags so the test executes
correctly?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260720142440.22076-1-timur.kristof@gmail.com?part=4

  reply	other threads:[~2026-07-20 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 1/4] drm/fourcc: Add modifiers for AMD GFX6-8 Timur Kristóf
2026-07-20 14:28   ` sashiko-bot
2026-07-20 14:24 ` [PATCH 2/4] drm/amdgpu: Convert tiling flags to modifiers on GFX6-8 Timur Kristóf
2026-07-20 14:43   ` sashiko-bot
2026-07-20 14:24 ` [PATCH 3/4] drm/amd/display: Support DRM format " Timur Kristóf
2026-07-20 14:42   ` sashiko-bot
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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 4/4] drm/amd/display: Don't use tiling flags anymore Timur Kristóf
2026-07-22 17:34   ` sashiko-bot
2026-07-27 15:44     ` Alex Deucher
2026-07-27 16:04       ` Alex Deucher
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=20260720150029.5EA371F000E9@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