summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/display/dmub/inc
diff options
context:
space:
mode:
authorAlvin Lee <alvin.lee2@amd.com>2024-01-26 16:47:20 -0500
committerAlex Deucher <alexander.deucher@amd.com>2024-02-07 12:26:23 -0500
commit6a068e64fb25dbc81256fc03db0d4579d222bccd (patch)
tree013ece548217742b20baf8439ab99e6c3efca3bc /drivers/gpu/drm/amd/display/dmub/inc
parent0701117efd1ed97c8547228ff597ed25d34296c5 (diff)
drm/amd/display: Update phantom pipe enable / disable sequence
Previously we would call apply_ctx_to_hw to enable and disable phantom pipes. However, apply_ctx_to_hw can potentially update non-phantom pipes as well which is undesired. Instead of calling apply_ctx_to_hw as a whole, call the relevant helpers for each phantom pipe when enabling / disabling which will avoid us modifying hardware state for non-phantom pipes unknowingly. The use case is for an FRL display where FRL_Update is requested by the display. In this case link_state_valid flag is cleared in a passive callback thread and should be handled in the next stream / link update. However, due to the call to apply_ctx_to_hw for the phantom pipes during a flip, the main pipes were modified outside of the desired sequence (driver does not handle link_state_valid = 0 on flips). Cc: stable@vger.kernel.org # 6.6+ Reviewed-by: Samson Tam <samson.tam@amd.com> Acked-by: Hamza Mahfooz <hamza.mahfooz@amd.com> Signed-off-by: Alvin Lee <alvin.lee2@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/display/dmub/inc')
0 files changed, 0 insertions, 0 deletions