diff options
| author |   Dmitry Baryshkov <dmitry.baryshkov@linaro.org> | 2024-08-02 22:47:34 +0300 |
|---|---|---|
| committer |   Abhinav Kumar <quic_abhinavk@quicinc.com> | 2024-08-05 13:44:25 -0700 |
| commit | df24373435f5899a2a98b7d377479c8d4376613b (patch) | |
| tree | a395f626602627be23b56cae177108387f14f9ed /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | dt-bindings: display/msm: dsi-controller-main: Add SM7150 (diff) | |
| download | wireguard-linux-df24373435f5899a2a98b7d377479c8d4376613b.tar.xz wireguard-linux-df24373435f5899a2a98b7d377479c8d4376613b.zip | |
drm/msm/dpu: don't play tricks with debug macros
DPU debugging macros need to be converted to a proper drm_debug_*
macros, however this is a going an intrusive patch, not suitable for a
fix. Wire DPU_DEBUG and DPU_DEBUG_DRIVER to always use DRM_DEBUG_DRIVER
to make sure that DPU debugging messages always end up in the drm debug
messages and are controlled via the usual drm.debug mask.
I don't think that it is a good idea for a generic DPU_DEBUG macro to be
tied to DRM_UT_KMS. It is used to report a debug message from driver, so by
default it should go to the DRM_UT_DRIVER channel. While refactoring
debug macros later on we might end up with particular messages going to
ATOMIC or KMS, but DRIVER should be the default.
Fixes: 25fdd5933e4c ("drm/msm: Add SDM845 DPU support")
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Patchwork: https://patchwork.freedesktop.org/patch/606932/
Link: https://lore.kernel.org/r/20240802-dpu-fix-wb-v2-2-7eac9eb8e895@linaro.org
Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions