From: abhinavk@codeaurora.org To: Rob Clark <robdclark@gmail.com> Cc: dri-devel@lists.freedesktop.org, Rob Clark <robdclark@chromium.org>, Sean Paul <sean@poorly.run>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Drew Davenport <ddavenport@chromium.org>, Sam Ravnborg <sam@ravnborg.org>, Hongbo Yao <yaohongbo@huawei.com>, Kalyan Thota <kalyan_t@codeaurora.org>, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-msm-owner@vger.kernel.org Subject: Re: [PATCH] drm/msm: ratelimit crtc event overflow error Date: Wed, 01 Jul 2020 15:51:21 -0700 [thread overview] Message-ID: <d49731c0ecc5b2337f26597decbf82e4@codeaurora.org> (raw) In-Reply-To: <20200701203602.1272157-1-robdclark@gmail.com> On 2020-07-01 13:36, Rob Clark wrote: > From: Rob Clark <robdclark@chromium.org> > > This can happen a lot when things go pear shaped. Lets not flood dmesg > when this happens. > > Signed-off-by: Rob Clark <robdclark@chromium.org> Reviewed-by: Abhinav Kumar <abhinavk@codeaurora.org> > --- > drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > index e15b42a780e0..969d95aa873c 100644 > --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > @@ -389,7 +389,7 @@ static void dpu_crtc_frame_event_cb(void *data, u32 > event) > spin_unlock_irqrestore(&dpu_crtc->spin_lock, flags); > > if (!fevent) { > - DRM_ERROR("crtc%d event %d overflow\n", crtc->base.id, event); > + DRM_ERROR_RATELIMITED("crtc%d event %d overflow\n", crtc->base.id, > event); > return; > }
WARNING: multiple messages have this Message-ID (diff)
From: abhinavk@codeaurora.org To: Rob Clark <robdclark@gmail.com> Cc: Rob Clark <robdclark@chromium.org>, freedreno@lists.freedesktop.org, David Airlie <airlied@linux.ie>, Sam Ravnborg <sam@ravnborg.org>, linux-arm-msm@vger.kernel.org, Hongbo Yao <yaohongbo@huawei.com>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Kalyan Thota <kalyan_t@codeaurora.org>, Drew Davenport <ddavenport@chromium.org>, Sean Paul <sean@poorly.run>, linux-arm-msm-owner@vger.kernel.org Subject: Re: [PATCH] drm/msm: ratelimit crtc event overflow error Date: Wed, 01 Jul 2020 15:51:21 -0700 [thread overview] Message-ID: <d49731c0ecc5b2337f26597decbf82e4@codeaurora.org> (raw) In-Reply-To: <20200701203602.1272157-1-robdclark@gmail.com> On 2020-07-01 13:36, Rob Clark wrote: > From: Rob Clark <robdclark@chromium.org> > > This can happen a lot when things go pear shaped. Lets not flood dmesg > when this happens. > > Signed-off-by: Rob Clark <robdclark@chromium.org> Reviewed-by: Abhinav Kumar <abhinavk@codeaurora.org> > --- > drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > index e15b42a780e0..969d95aa873c 100644 > --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c > @@ -389,7 +389,7 @@ static void dpu_crtc_frame_event_cb(void *data, u32 > event) > spin_unlock_irqrestore(&dpu_crtc->spin_lock, flags); > > if (!fevent) { > - DRM_ERROR("crtc%d event %d overflow\n", crtc->base.id, event); > + DRM_ERROR_RATELIMITED("crtc%d event %d overflow\n", crtc->base.id, > event); > return; > } _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-07-01 22:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 20:36 [PATCH] drm/msm: ratelimit crtc event overflow error Rob Clark 2020-07-01 20:36 ` Rob Clark 2020-07-01 22:51 ` abhinavk [this message] 2020-07-01 22:51 ` abhinavk
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=d49731c0ecc5b2337f26597decbf82e4@codeaurora.org \ --to=abhinavk@codeaurora.org \ --cc=airlied@linux.ie \ --cc=daniel@ffwll.ch \ --cc=ddavenport@chromium.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=freedreno@lists.freedesktop.org \ --cc=kalyan_t@codeaurora.org \ --cc=linux-arm-msm-owner@vger.kernel.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robdclark@chromium.org \ --cc=robdclark@gmail.com \ --cc=sam@ravnborg.org \ --cc=sean@poorly.run \ --cc=yaohongbo@huawei.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.