summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorWenjing Liu <wenjing.liu@amd.com>2023-08-23 13:19:27 -0400
committerAlex Deucher <alexander.deucher@amd.com>2023-09-11 17:17:03 -0400
commitc51d87202d1faef21e1eee37381b43c72bd231bc (patch)
tree5a243f155e28be01bb2ad3dbceed9cc31191ba20 /tools/perf/scripts/python/stackcollapse.py
parentc30406623422b9ddc77f55e94dcd5171bd5cc106 (diff)
downloadlinux-c51d87202d1faef21e1eee37381b43c72bd231bc.tar.gz
linux-c51d87202d1faef21e1eee37381b43c72bd231bc.zip
drm/amd/display: do not attempt ODM power optimization if minimal transition doesn't exist
[why] In some cases such as 8k desktop surface with 144Hz timing, we decide to enable ODM power optimization but this surface doesn't have a minimum transition state. Therefore we cannot switch off ODM power optimization seamlessly This creates path depedency on ODM power optimization decision. i.e whether or not we should switch off ODM power optimization is dependent on if the transition to switch off ODM power optimization from current state is seamless. We don't desire a path dependent power optimization policy as it is too dynamic and difficult to maintain. [how] Attempt ODM power optimization only after we can validate new state without using pipe combine. Reviewed-by: Dillon Varone <dillon.varone@amd.com> Acked-by: Stylon Wang <stylon.wang@amd.com> Signed-off-by: Wenjing Liu <wenjing.liu@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions