diff options
| author | Hamza Mahfooz <hamza.mahfooz@amd.com> | 2023-08-15 16:13:37 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-09-19 13:28:08 +0300 |
| commit | cb30ff2adb10a660ded094b088aca763aaf74dea (patch) | |
| tree | b6e503ae6f0c4a1f2ebf84925a23054a566ed1a6 /io_uring | |
| parent | b53fee19ec5e07e5553f362cad8a3e00cf6d16ab (diff) | |
| download | linux-cb30ff2adb10a660ded094b088aca763aaf74dea.tar.xz | |
drm/amdgpu: register a dirty framebuffer callback for fbcon
commit 0a611560f53bfd489e33f4a718c915f1a6123d03 upstream.
fbcon requires that we implement &drm_framebuffer_funcs.dirty.
Otherwise, the framebuffer might take a while to flush (which would
manifest as noticeable lag). However, we can't enable this callback for
non-fbcon cases since it may cause too many atomic commits to be made at
once. So, implement amdgpu_dirtyfb() and only enable it for fbcon
framebuffers (we can use the "struct drm_file file" parameter in the
callback to check for this since it is only NULL when called by fbcon,
at least in the mainline kernel) on devices that support atomic KMS.
Cc: Aurabindo Pillai <aurabindo.pillai@amd.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>
Cc: stable@vger.kernel.org # 6.1+
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2519
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'io_uring')
0 files changed, 0 insertions, 0 deletions