All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Masney <masneyb@onstation.org>
To: Rob Clark <robdclark@chromium.org>
Cc: Sean Paul <sean@poorly.run>,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: drm/msm: 'pp done time out' errors after async commit changes
Date: Mon, 4 Nov 2019 19:01:29 -0500	[thread overview]
Message-ID: <20191105000129.GA6536@onstation.org> (raw)

Hey Rob,

Since commit 2d99ced787e3 ("drm/msm: async commit support"), the frame
buffer console on my Nexus 5 began throwing these errors:

msm fd900000.mdss: pp done time out, lm=0

The display still works.

I see that mdp5_flush_commit() was introduced in commit 9f6b65642bd2
("drm/msm: add kms->flush_commit()") with a TODO comment and the commit
description mentions flushing registers. I assume that this is the
proper fix. If so, can you point me to where these registers are
defined and I can work on the mdp5 implementation.

Thanks,

Brian

WARNING: multiple messages have this Message-ID (diff)
From: Brian Masney <masneyb@onstation.org>
To: Rob Clark <robdclark@chromium.org>
Cc: freedreno@lists.freedesktop.org, Sean Paul <sean@poorly.run>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-arm-msm@vger.kernel.org
Subject: drm/msm: 'pp done time out' errors after async commit changes
Date: Mon, 4 Nov 2019 19:01:29 -0500	[thread overview]
Message-ID: <20191105000129.GA6536@onstation.org> (raw)
Message-ID: <20191105000129.9wQiqnMqjCFEAGhNOjN1dYjtixiXj2J5h3AHXiHfJdA@z> (raw)

Hey Rob,

Since commit 2d99ced787e3 ("drm/msm: async commit support"), the frame
buffer console on my Nexus 5 began throwing these errors:

msm fd900000.mdss: pp done time out, lm=0

The display still works.

I see that mdp5_flush_commit() was introduced in commit 9f6b65642bd2
("drm/msm: add kms->flush_commit()") with a TODO comment and the commit
description mentions flushing registers. I assume that this is the
proper fix. If so, can you point me to where these registers are
defined and I can work on the mdp5 implementation.

Thanks,

Brian
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-11-05  0:01 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  0:01 Brian Masney [this message]
2019-11-05  0:01 ` drm/msm: 'pp done time out' errors after async commit changes Brian Masney
2019-11-05  0:19 ` [Freedreno] " Rob Clark
2019-11-05  0:19   ` Rob Clark
2019-11-05 10:08   ` Brian Masney
2019-11-05 10:08     ` Brian Masney
2019-11-05 16:23     ` Rob Clark
2019-11-05 16:23       ` Rob Clark
2019-11-06  9:13       ` Brian Masney
2019-11-06  9:13         ` Brian Masney
2019-11-06 16:29         ` Rob Clark
2019-11-06 16:29           ` Rob Clark
2019-11-06 16:29           ` Rob Clark
2019-11-06 16:47           ` [Freedreno] " Jeffrey Hugo
2019-11-06 16:47             ` Jeffrey Hugo
2019-11-06 16:58             ` Rob Clark
2019-11-06 16:58               ` Rob Clark
2019-11-06 16:58               ` Rob Clark
2019-11-07 11:10               ` [Freedreno] " Brian Masney
2019-11-07 11:10                 ` Brian Masney
2019-11-07 16:16                 ` Rob Clark
2019-11-07 16:16                   ` Rob Clark
2019-11-07 17:40                   ` Jeffrey Hugo
2019-11-07 17:40                     ` Jeffrey Hugo
2019-11-08  2:03                     ` Rob Clark
2019-11-08  2:03                       ` Rob Clark
2019-11-08  2:03                       ` Rob Clark
2019-11-08 14:56                       ` [Freedreno] " Jeffrey Hugo
2019-11-08 14:56                         ` Jeffrey Hugo
2019-11-08 14:56                         ` Jeffrey Hugo
2019-11-10 13:53                         ` [Freedreno] " Brian Masney
2019-11-10 13:53                           ` Brian Masney
2019-11-10 13:53                           ` Brian Masney
2019-11-10 17:37                           ` [Freedreno] " Jeffrey Hugo
2019-11-10 17:37                             ` Jeffrey Hugo
2019-11-10 17:37                             ` Jeffrey Hugo
2019-11-11 11:38                             ` [Freedreno] " Brian Masney
2019-11-11 11:38                               ` Brian Masney
2019-11-11 11:38                               ` Brian Masney
2019-11-11 14:51                               ` [Freedreno] " Jeffrey Hugo
2019-11-11 14:51                                 ` Jeffrey Hugo
2019-11-12 10:54                                 ` Brian Masney
2019-11-12 10:54                                   ` Brian Masney
2019-11-12 10:54                                   ` Brian Masney

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=20191105000129.GA6536@onstation.org \
    --to=masneyb@onstation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robdclark@chromium.org \
    --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 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.