kernel/linux.git/drivers/gpu/drm/amd/display/include/logger_interface.h, branch v6.12.80

drm/amd/dc: Kill dc_conn_log_hex_linux()

2020-04-01T18:44:59+00:00

DRM already supports tracing DPCD transactions, there's no reason for the existence of this function. Also, it prints one byte per-line which is way too loud. So, just remove it. Reviewed-by: Nicholas Kazlauskas Signed-off-by: Lyude Paul Signed-off-by: Alex Deucher

drm/amd/display: Add Logging for Gamma Related information (1/2)

2019-08-15T15:55:55+00:00

[Why] A recent bug showed that logging would be useful in debugging various gamma issues. [How] Add new log types and logging code to the color module. Signed-off-by: Wyatt Wood Reviewed-by: Aric Cyr Acked-by: Leo Li Signed-off-by: Alex Deucher

drm/amd/display: Support reading hw state from debugfs file

2018-08-27T20:20:49+00:00

[Why] Logging hardware state can be done by triggering a write to the debugfs file. It would also be useful to be able to read the hardware state from the debugfs file to be able to generate a clean log without timestamps. [How] Usage: cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log Threading is an obvious concern when dealing with multiple debugfs operations and blocking on global state in dm or dc seems unfavorable. Adding an extra parameter for the debugfs log context state is the implementation done here. Existing code that made use of DTN_INFO and its associated macros needed to be refactored to support this. We don't know the size of the log in advance so it reallocates the log string dynamically. Once the log has been generated it's copied into the user supplied buffer for the debugfs. This allows for seeking support but it's worth nothing that unlike triggering output via dmesg the hardware state might change in-between reads if your buffer size is too small. Signed-off-by: Nicholas Kazlauskas Reviewed-by: Jordan Lazare Acked-by: Leo Li Signed-off-by: Alex Deucher

drm/amd/display: Convert remaining loggers off dc_logger

2018-07-13T19:48:42+00:00

- Removed dal/dm/dc loggers from linux, switched to kernel prints - Modified functions that used these directly to use macros - dc_logger support is completely dropped from Linux Signed-off-by: Nicholas Kazlauskas Reviewed-by: Harry Wentland Signed-off-by: Alex Deucher

drm/amd/display: Default log masks should include all connectivity events

2018-06-15T17:20:25+00:00

Signed-off-by: Aric Cyr Reviewed-by: Jun Lei Reviewed-by: Aric Cyr Acked-by: Harry Wentland Signed-off-by: Alex Deucher

drm/amd/display: use macro for logs

2018-05-18T21:08:27+00:00

Signed-off-by: Anthony Koo Reviewed-by: Tony Cheng Acked-by: Harry Wentland Signed-off-by: Alex Deucher

drm/amd/display: Add dm_logger_append_va API

2017-12-06T17:48:27+00:00

Same as dm_logger_append, except it takes a va_list instead of a variable number of arguments. dm_logger_append is now a minimal wrapper around dm_logger_append_va. Reviewed-by: Alex Deucher Signed-off-by: Michel Dänzer Signed-off-by: Alex Deucher

drm/amd/display: add performance trace macro to dc

2017-10-21T20:50:00+00:00

Signed-off-by: Dmytro Laktyushkin Reviewed-by: Tony Cheng Acked-by: Harry Wentland Signed-off-by: Alex Deucher

drm/amd/display: Pass log_mask from DM

2017-09-26T22:17:43+00:00

Linux and Windows often desire different log levels. Signed-off-by: Harry Wentland Signed-off-by: Alex Deucher

drm/amd/display: Rename dc validate_context and current_context

2017-09-26T22:17:14+00:00

Rename all the dc validate_context to dc_state and dc current_context to current_state. Signed-off-by: Jerry Zuo Reviewed-by: Harry Wentland Signed-off-by: Alex Deucher