diff options
| author | Julian Parkin <julian.parkin@amd.com> | 2019-08-30 00:06:05 +0300 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2019-10-11 03:33:00 +0300 |
| commit | edb922b022c0c94805c4ffad202b3edff83d76f0 (patch) | |
| tree | e92881ff6fdd318579a6274ea14e95141bde9f4f /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 1503676caf09b3d60cc8d9de279dc1d743f49237 (diff) | |
| download | linux-edb922b022c0c94805c4ffad202b3edff83d76f0.tar.xz | |
drm/amd/display: Program DWB watermarks from correct state
[Why]
When diags adds a DWB via a stream update, we calculate MMHUBBUB
paramaters, but dc->current_state has not yet been updated
when the DWB programming happens. This leads to overflow on
high bandwidth tests since the incorrect MMHUBBUB arbitration
parameters are programmed.
[How]
Pass the updated context down to the (enable|update)_writeback functions
so that they can use the correct watermarks when programming MMHUBBUB.
Signed-off-by: Julian Parkin <julian.parkin@amd.com>
Reviewed-by: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions