leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0410c5e514
linux/drivers/gpu/drm/amd/display
History
Michel Dänzer 38636603d8 drm/amd/display: Don't call dm_log_to_buffer directly in dc_conn_log 
dm_log_to_buffer logs unconditionally, so calling it directly resulted
in the main message being logged even when the event type isn't enabled
in the event mask.

To fix this, use the new dm_logger_append_va API.

Fixes spurious messages like

 [drm] {1920x1200, 2080x1235@154000Khz}

in dmesg when a mode is set.

v2:
* Use new dm_logger_append_va API, fixes incorrect va_list usage in v1
* Just use and decrease entry.buf_offset to get rid of the trailing
  newline

Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
2017-12-06 12:48:28 -05:00
..
amdgpu_dm drm/amd/display: remove usage of legacy_cursor_update 2017-12-06 12:48:26 -05:00
dc drm/amd/display: Don't call dm_log_to_buffer directly in dc_conn_log 2017-12-06 12:48:28 -05:00
include drm/amd/display: Add dm_logger_append_va API 2017-12-06 12:48:27 -05:00
modules drm/amd/display: Remove unnecessary dc_stream vtable 2017-12-06 12:47:45 -05:00
Kconfig
Makefile
TODO