Lines Matching +full:firmware +full:- +full:initialized

18 ---------------------------
52   dmesg | grep -i 'display core'
56   [    4.655828] [drm] Display Core v3.2.285 initialized on DCN 3.2
63   version of the display code. Remember from page :ref:`Display Core <amdgpu-display-core>`,
78   dmesg  | grep -i 'ATOM BIOS'
82   [    4.274534] amdgpu: ATOM BIOS: 113-D7020100-102
87 --------------------------
127 ------------------
133    bash -c "echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level"
145 -----------------
164 DC has a struct named `dc_debug_options`, which is statically initialized by
166 structure usually facilitates the bring-up phase since developers can start
173 indication of Sub-Viewport issues; after the users identified the target DCN,
175 initialized version of `dc_debug_options` to see if the issue gets fixed. Along
194 ---------------------
196 If you want to enable or debug multiple planes in a specific user-space
206 * The color indicates the format - For example, red is AR24 and green is NV12
224 ----------------
247 change in real-time by using something like::
249   sudo watch -d cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log
254 Collect Firmware information
257 When reporting issues, it is important to have the firmware information since
258 it can be helpful for debugging purposes. To get all the firmware information,
263 From the display perspective, pay attention to the firmware of the DMCU and
266 DMUB Firmware Debug
270 implemented primarily in DMUB firmware. In such cases, all we see in dmesg when
278 ------------
280 .. csv-table::
281    :header-rows: 1
283    :file: ./trace-groups-table.csv