[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d91c5bf-68cc-84ad-5d78-53dd1926167c@quicinc.com>
Date: Mon, 11 Dec 2023 10:26:40 -0800
From: Abhinav Kumar <quic_abhinavk@...cinc.com>
To: Rob Clark <robdclark@...il.com>, <dri-devel@...ts.freedesktop.org>
CC: <freedreno@...ts.freedesktop.org>, <linux-arm-msm@...r.kernel.org>,
"Rob Clark" <robdclark@...omium.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Sean Paul <sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>,
"Daniel Vetter" <daniel@...ll.ch>,
Kuogee Hsieh <quic_khsieh@...cinc.com>,
"Jessica Zhang" <quic_jesszhan@...cinc.com>,
Vinod Polimera <quic_vpolimer@...cinc.com>,
Kalyan Thota <quic_kalyant@...cinc.com>,
"Dan Carpenter" <dan.carpenter@...aro.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/msm/dpu: Ratelimit framedone timeout msgs
On 12/11/2023 10:19 AM, Rob Clark wrote:
> From: Rob Clark <robdclark@...omium.org>
>
> When we start getting these, we get a *lot*. So ratelimit it to not
> flood dmesg.
>
> Signed-off-by: Rob Clark <robdclark@...omium.org>
> ---
>
> dpu should probably stop rolling it's own trace macros, but that would
> be a larger cleanup.
>
> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 5 ++++-
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 1 +
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
Reviewed-by: Abhinav Kumar <quic_abhinavk@...cinc.com>
Powered by blists - more mailing lists