summaryrefslogtreecommitdiff
path: root/io_uring
diff options
context:
space:
mode:
authorWenjing Liu <wenjing.liu@amd.com>2024-01-18 18:12:15 -0500
committerAlex Deucher <alexander.deucher@amd.com>2024-02-07 18:16:46 -0500
commit2103370afba74dda39ff5d2d69163c86644ce528 (patch)
tree036fe645cc6cc029941ded74b5f31b3e745f1aa4 /io_uring
parent66951d98d9bf45ba25acf37fe0747253fafdf298 (diff)
drm/amd/display: set odm_combine_policy based on context in dcn32 resource
[why] When populating dml pipes, odm combine policy should be assigned based on the pipe topology of the context passed in. DML pipes could be repopulated multiple times during single validate bandwidth attempt. We need to make sure that whenever we repopulate the dml pipes it is always aligned with the updated context. There is a case where DML pipes get repopulated during FPO optimization after ODM combine policy is changed. Since in the current code we reinitlaize ODM combine policy, even though the current context has ODM combine enabled, we overwrite it despite the pipes are already split. This causes DML to think that MPC combine is used so we mistakenly enable MPC combine because we apply pipe split with ODM combine policy reset. This issue doesn't impact non windowed MPO with ODM case because the legacy policy has restricted use cases. We don't encounter the case where both ODM and FPO optimizations are enabled together. So we decide to leave it as is because it is about to be replaced anyway. Cc: stable@vger.kernel.org # 6.6+ Reviewed-by: Chaitanya Dhere <chaitanya.dhere@amd.com> Reviewed-by: Alvin Lee <alvin.lee2@amd.com> Acked-by: Hamza Mahfooz <hamza.mahfooz@amd.com> Signed-off-by: Wenjing Liu <wenjing.liu@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'io_uring')
0 files changed, 0 insertions, 0 deletions