drm/i915/display: Add meaningful traces for QGV point info error handling
authorStanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Fri, 5 Apr 2024 11:35:28 +0000 (14:35 +0300)
committerVinod Govindapillai <vinod.govindapillai@intel.com>
Fri, 19 Apr 2024 12:45:13 +0000 (15:45 +0300)
commit92363681945088d4813341b749d89d22a1e5592d
tree40268c96b3234e2d42e6ec8d7c18ed5f1b12a320
parent2a956ad8d10bc8d32f32aa2cafdbacbf408e9e3f
drm/i915/display: Add meaningful traces for QGV point info error handling

For debug purposes we need those - error path won't flood the log,
however there has been already numerous cases, when due to lack
of debugs, we couldn't immediately tell what was the problem on
customer machine, which slowed down the investigation, requiring
to get access to target device and adding those traces manually.

v2: - Make the debug more generic and move it to intel_dram_detect
      (Gustavo Sousa)
v3: - Use %u for unsigned variable in debug prints (Gustavo)

Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240405113533.338553-2-vinod.govindapillai@intel.com
drivers/gpu/drm/i915/display/intel_bw.c
drivers/gpu/drm/i915/soc/intel_dram.c