From: Philippe CORNU <philippe.cornu@st.com>
To: Yannick FERTRE <yannick.fertre@st.com>,
Vincent ABRIOU <vincent.abriou@st.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"Alexandre TORGUE" <alexandre.torgue@st.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/stm: ltdc: use DRM_WARN for fifo & transfer error messages
Date: Mon, 1 Apr 2019 09:20:19 +0000 [thread overview]
Message-ID: <ef8aa4e8-ebf9-ea01-d8db-fbf7740bc765@st.com> (raw)
In-Reply-To: <1553874548-31366-1-git-send-email-yannick.fertre@st.com>
Dear Yannick,
Fully agree with this approach,
Acked-by: Philippe Cornu <philippe.cornu@st.com>
Philippe :-)
On 3/29/19 4:49 PM, Yannick Fertré wrote:
> From: Philippe Cornu <philippe.cornu@st.com>
>
> Use DRM_WARN() instead of DRM_DEBUG_DRIVER() to better
> inform the user in case of fifo underruns or
> transfer errors.
>
> Signed-off-by: Philippe Cornu <philippe.cornu@st.com>
> ---
> drivers/gpu/drm/stm/ltdc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.c
> index b1741a9..15d8a02 100644
> --- a/drivers/gpu/drm/stm/ltdc.c
> +++ b/drivers/gpu/drm/stm/ltdc.c
> @@ -822,11 +822,11 @@ static void ltdc_plane_atomic_update(struct drm_plane *plane,
>
> mutex_lock(&ldev->err_lock);
> if (ldev->error_status & ISR_FUIF) {
> - DRM_DEBUG_DRIVER("Fifo underrun\n");
> + DRM_WARN("ltdc fifo underrun: please verify display mode\n");
> ldev->error_status &= ~ISR_FUIF;
> }
> if (ldev->error_status & ISR_TERRIF) {
> - DRM_DEBUG_DRIVER("Transfer error\n");
> + DRM_WARN("ltdc transfer error\n");
> ldev->error_status &= ~ISR_TERRIF;
> }
> mutex_unlock(&ldev->err_lock);
>
next prev parent reply other threads:[~2019-04-01 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 15:49 Yannick Fertré
2019-04-01 9:20 ` Philippe CORNU [this message]
2019-04-24 12:26 ` Benjamin Gaignard
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=ef8aa4e8-ebf9-ea01-d8db-fbf7740bc765@st.com \
--to=philippe.cornu@st.com \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.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: 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
all inboxes | Powered by JetHome®