drm/amd/display: Fixed read/write pointer issue for get dmub trace

Browse source

[Why]
Driver get wrap around dmub trace data due to read pointer being
increased incorrectly when there are multiple interrupt
queues with very short interval

[How]
Check read/write pointer before copying data from ring buffer

Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
Signed-off-by: Yongqiang Sun <yongqiang.sun@amd.com>
Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
Acked-by: Eryk Brol <eryk.brol@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Yongqiang Sun 2021-02-26 11:07:37 -05:00 • committed by Alex Deucher

parent 61a74712c8

commit 6804287bd1

4 changed files with 13 additions and 18 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

8

drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c

View file

2

drivers/gpu/drm/amd/display/dc/dc_dmub_srv.h

View file

2

drivers/gpu/drm/amd/display/dmub/dmub_srv.h

View file

19

drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c

View file