diff options
author | Hamza Mahfooz <hamza.mahfooz@amd.com> | 2022-08-08 16:22:42 -0400 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2022-08-16 18:17:31 -0400 |
commit | 0a8c91d7b694d122afe513e95908e8497cddc195 (patch) | |
tree | 29b9f0f8007fd6694b9e10d77704a8e8bfd1c328 /drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | |
parent | a4d3230353e493d98263c5d7f03ee6403ed82d71 (diff) | |
download | linux-0a8c91d7b694d122afe513e95908e8497cddc195.tar.gz linux-0a8c91d7b694d122afe513e95908e8497cddc195.tar.bz2 linux-0a8c91d7b694d122afe513e95908e8497cddc195.zip |
drm/amd/display: include soc._clock_tmp[] into DC's scratch region
Currently, we are using soc._clock_tmp[] to temporarily store and modify
data from soc.clock_limits[] before copying it back into
soc.clock_limits[] (because modifying data directly in
soc.clock_limits[] causes unintended behavior). However, this approach
has a number of downsides, such as:
1. struct _vcs_dpi_soc_bounding_box_st's creation/destruction
aren't well defined (which could mean more unintended
behavior).
2. Throwing "temp" varibles in structs everywhere doesn't make
for a particularly readable codebase.
For these reasons, we should get rid of soc._clock_tmp[] by defining a
struct scratch within struct dc that, contains within it all of the
temporary variables (including _clock_tmp[]) such that it is obvious how
they are intended to be used.
Co-authored-by: Leo Li <sunpeng.li@amd.com>
Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c')
0 files changed, 0 insertions, 0 deletions