[linux-next:master] BUILD REGRESSION ad5c60d66016e544c51ed98635a74073f761f45d

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: ad5c60d66016e544c51ed98635a74073f761f45d Add linux-next specific files for 20240119 Error/Warning reports: https://lore.kernel.org/oe-kbuild-all/202401192143.jldjbiy3-...@intel.com https

[PATCH] drm/amdkfd: Add cache line sizes to KFD topology

The KFD topology includes cache line size, but we have not been filling that information out unless we are parsing a CRAT table. Fill in this information for the devices where we have cache information structs, and pipe this information to the topology sysfs files. Signed-off-by: Joseph Greathouse

Re: [PATCH 1/2] drm/atomic: Allow drivers to write their own plane check for async flips

Hi André, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-misc/drm-misc-next] [also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-tip/drm-tip linus/master next-20240119] [cannot apply to drm-intel/for-linux

Re: [PATCH v2] drm/amdgpu: change vm->task_info handling

On 2024-01-18 14:21, Shashank Sharma wrote: This patch changes the handling and lifecycle of vm->task_info object. The major changes are: - vm->task_info is a dynamically allocated ptr now, and its uasge is reference counted. - introducing two new helper funcs for task_info lifecycle managem

Re: [PATCH] Revert "drm/amd/pm: fix the high voltage and temperature issue"

[AMD Official Use Only - General] Acked-by: Alex Deucher From: amd-gfx on behalf of Mario Limonciello Sent: Friday, January 19, 2024 4:16 AM To: amd-gfx@lists.freedesktop.org Cc: Feng, Kenneth ; Limonciello, Mario ; sta...@vger.kernel.org Subject: [PATCH] Re

[PATCH] Revert "drm/amd/pm: fix the high voltage and temperature issue"

This reverts commit 5f38ac54e60562323ea4abb1bfb37d043ee23357. This causes issues with rebooting and the 7800XT. Cc: Kenneth Feng Cc: sta...@vger.kernel.org Fixes: 5f38ac54e605 ("drm/amd/pm: fix the high voltage and temperature issue") Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3062 S

Re: [PATCH 1/2] drm/amdgpu: Reset IH OVERFLOW_CLEAR bit after writing rptr

On 2024-01-18 07:07, Christian König wrote: Am 18.01.24 um 00:44 schrieb Friedrich Vock: On 18.01.24 00:00, Alex Deucher wrote: [SNIP] Right now, IH overflows, even if they occur repeatedly, only get registered once. If not registering IH overflows can trivially lead to system crashes, it's

Re: [PATCH v2 2/2] drm/amdgpu: Implement check_async_props for planes

On Fri, Jan 19, 2024 at 03:12:35PM -0300, André Almeida wrote: > AMD GPUs can do async flips with changes on more properties than just > the FB ID, so implement a custom check_async_props for AMD planes. > > Allow amdgpu to do async flips with IN_FENCE_ID and FB_DAMAGE_CLIPS > properties. For user

[PATCH v2 2/2] drm/amdgpu: Implement check_async_props for planes

AMD GPUs can do async flips with changes on more properties than just the FB ID, so implement a custom check_async_props for AMD planes. Allow amdgpu to do async flips with IN_FENCE_ID and FB_DAMAGE_CLIPS properties. For userspace to check if a driver support this two properties, the strategy for

[PATCH v2 1/2] drm/atomic: Allow drivers to write their own plane check for async flips

Some hardware are more flexible on what they can flip asynchronously, so rework the plane check so drivers can implement their own check, lifting up some of the restrictions. Signed-off-by: André Almeida --- drivers/gpu/drm/drm_atomic_uapi.c | 62 ++- include/drm/drm_

[PATCH v2 0/2] drm/atomic: Allow drivers to write their own plane check for async

Hi, AMD hardware can do more on the async flip path than just the primary plane, so to lift up the current restrictions, this patchset allows drivers to write their own check for planes for async flips. For now this patchset only allow for async commits with IN_FENCE_ID and FB_DAMAGE_CLIPS. Users

RE: [PATCH 00/12] DC Patches January 18, 2024

[Public] Hi all, This week this patchset was tested on the following systems: * Lenovo ThinkBook T13s Gen4 with AMD Ryzen 5 6600U * MSI Gaming X Trio RX 6800 * Gigabyte Gaming OC RX 7900 XTX These systems were tested on the following display/connection types: * eD

Re: [PATCH v3 0/9] drm/amd/display: improve DTN color state log

On 2023-11-28 12:52, Melissa Wen wrote: > This series updates the color state section of the AMD DTN log to match > color resource differences between DCN versions. > > Currently, the DTN log considers the DCN10 color pipeline, which is > useless for newer DCN versions due to all the color capa

Re: [PATCH] drm/amd/pm: update the power cap setting

On Fri, Jan 19, 2024 at 3:47 AM Kenneth Feng wrote: > > update the power cap setting for smu_v13.0.0/smu_v13.0.7 > Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2356 Acked-by: Alex Deucher > Signed-off-by: Kenneth Feng > --- > .../drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c | 54 +++

Re: [PATCH v2 1/2] drm/amdgpu: Reset IH OVERFLOW_CLEAR bit

On Fri, Jan 19, 2024 at 3:11 AM Christian König wrote: > > > > Am 18.01.24 um 19:54 schrieb Friedrich Vock: > > Allows us to detect subsequent IH ring buffer overflows as well. > > > > Cc: Joshua Ashton > > Cc: Alex Deucher > > Cc: Christian König > > Cc: sta...@vger.kernel.org > > > > Signed-o

Re: [PATCH v2 2/4] drm/uAPI: Add "force color format" drm property as setting for userspace

On Wed, 17 Jan 2024 12:58:15 + Andri Yngvason wrote: > mið., 17. jan. 2024 kl. 09:21 skrifaði Pekka Paalanen : ... > > EDID and DisplayID standards also evolve. The kernel could be behind > > userspace in chasing them, which was the reason why the kernel does not > > validate HDR_OUTPUT_MET

[PATCH] drm/amd/pm: update the power cap setting

update the power cap setting for smu_v13.0.0/smu_v13.0.7 Signed-off-by: Kenneth Feng --- .../drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c | 54 ++- .../drm/amd/pm/swsmu/smu13/smu_v13_0_7_ppt.c | 54 ++- 2 files changed, 104 insertions(+), 4 deletions(-) diff --git