From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
Jeykumar Sankaran <jsanka@codeaurora.org>
Subject: Re: [PATCH v2 2/2] drm/msm/dpu: don't play tricks with debug macros
Date: Mon, 5 Aug 2024 12:25:22 -0700 [thread overview]
Message-ID: <531b68a0-e2e5-4f39-a586-5aaf73bb376c@quicinc.com> (raw)
In-Reply-To: <20240802-dpu-fix-wb-v2-2-7eac9eb8e895@linaro.org>
On 8/2/2024 12:47 PM, Dmitry Baryshkov wrote:
> 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>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 14 ++------------
> 1 file changed, 2 insertions(+), 12 deletions(-)
>
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
next prev parent reply other threads:[~2024-08-05 19:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 19:47 [PATCH v2 0/2] drm/msm/dpu: two fixes targeting 6.11 Dmitry Baryshkov
2024-08-02 19:47 ` [PATCH v2 1/2] drm/msm/dpu1: don't choke on disabling the writeback connector Dmitry Baryshkov
2024-08-05 2:27 ` Leonard Lausen
2024-08-07 10:44 ` Dmitry Baryshkov
2024-08-07 15:41 ` Leonard Lausen
2024-08-05 19:19 ` Abhinav Kumar
2024-08-07 10:46 ` Dmitry Baryshkov
2024-08-30 17:36 ` [v2,1/2] " György Kurucz
2024-08-31 14:53 ` Leonard Lausen
2024-08-31 15:47 ` Leonard Lausen
2024-08-31 18:46 ` György Kurucz
2024-08-31 19:00 ` Leonard Lausen
2024-08-31 21:50 ` György Kurucz
2024-11-19 13:52 ` Johan Hovold
2024-11-19 14:33 ` Leonard Lausen
2024-11-19 15:11 ` Johan Hovold
2024-11-20 3:02 ` Leonard Lausen
2024-11-20 8:32 ` Johan Hovold
2024-11-20 8:39 ` [PATCH v2 1/2] " Johan Hovold
2024-12-06 10:40 ` Johan Hovold
2024-08-02 19:47 ` [PATCH v2 2/2] drm/msm/dpu: don't play tricks with debug macros Dmitry Baryshkov
2024-08-05 19:25 ` Abhinav Kumar [this message]
2024-08-27 9:39 ` Konrad Dybcio
2024-08-28 19:38 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=531b68a0-e2e5-4f39-a586-5aaf73bb376c@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jsanka@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox