diff options
| author | Josip Pavic <Josip.Pavic@amd.com> | 2019-09-12 22:40:08 +0300 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2019-10-11 03:32:32 +0300 |
| commit | 15caeabc5787c15babad7ee444afe9c26df1c8b3 (patch) | |
| tree | b7beb47e1ab3960e1333f53bc9cc4874e7c4da0d /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 486cc0ee550e619660926e162f68e96a64702216 (diff) | |
| download | linux-15caeabc5787c15babad7ee444afe9c26df1c8b3.tar.xz | |
drm/amd/display: wait for set pipe mcp command completion
[Why]
When the driver sends a pipe set command to the DMCU FW, it does not wait
for the command to complete. This can lead to unpredictable behavior if,
for example, the driver were to request a pipe disable to the FW via MCP,
then power down some hardware before the firmware has completed processing
the command.
[How]
Wait for the DMCU FW to finish processing set pipe commands
Signed-off-by: Josip Pavic <Josip.Pavic@amd.com>
Reviewed-by: Anthony Koo <Anthony.Koo@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/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions