From: John Stultz <john.stultz@linaro.org>
To: Kalyan Thota <kalyan_t@codeaurora.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
freedreno@lists.freedesktop.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
mkrishn@codeaurora.org, travitej@codeaurora.org,
Doug Anderson <dianders@chromium.org>,
lkml <linux-kernel@vger.kernel.org>,
Sean Paul <seanpaul@chromium.org>,
hoegsberg@chromium.org, Rob Clark <robdclark@gmail.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH 1/2] drm/msm/dpu: add support for color processing blocks in dpu driver
Date: Mon, 8 Jun 2020 15:25:48 -0700 [thread overview]
Message-ID: <CALAqxLViRrga-XW2o1J1JutFdS1d-qmmgOrEP2beNygw3A7H4A@mail.gmail.com> (raw)
In-Reply-To: <1585044079-358-1-git-send-email-kalyan_t@codeaurora.org>
On Wed, Mar 25, 2020 at 1:17 AM Kalyan Thota <kalyan_t@codeaurora.org> wrote:
>
> This change adds support to configure dspp blocks in
> the dpu driver.
>
> Macro description of the changes coming in this patch.
> 1) Add dspp definitions in the hw catalog.
> 2) Add capability to reserve dspp blocks in the display data path.
> 3) Attach the reserved block to the encoder.
>
> Signed-off-by: Kalyan Thota <kalyan_t@codeaurora.org>
Hey all,
With this patch now merged upstream, I'm seeing a regression on
db845c that I bisected down to it.
When I boot up I see:
[ 40.976737] [drm:_dpu_rm_check_lm_and_get_connected_blks] [dpu
error]failed to get dspp on lm 0
[ 40.985600] [drm:_dpu_rm_check_lm_and_get_connected_blks] [dpu
error]failed to get dspp on lm 0
[ 40.994587] [drm:_dpu_rm_check_lm_and_get_connected_blks] [dpu
error]failed to get dspp on lm 0
[ 41.003492] [drm:_dpu_rm_check_lm_and_get_connected_blks] [dpu
error]failed to get dspp on lm 0
[ 41.012283] [drm:_dpu_rm_make_reservation] [dpu error]unable to
find appropriate mixers
[ 41.020369] [drm:dpu_rm_reserve] [dpu error]failed to reserve hw
resources: -119
Over and over, and the display doesn't start up.
I suspect we're supposed to catch the following check before the failure:
+ if (!reqs->topology.num_dspp)
+ return true;
I suspect the issue is in dpu_encoder_get_topology() we don't fully
initialize the topology structure on the stack before returning it.
Does that sound plausible or is there likely some other cause?
thanks
-john
next prev parent reply other threads:[~2020-06-08 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 10:01 [PATCH 1/2] drm/msm/dpu: add support for color processing blocks in dpu driver Kalyan Thota
2020-03-24 10:01 ` [PATCH 2/2] drm/msm/dpu: add support for pcc color block " Kalyan Thota
2020-04-09 0:44 ` Fritz Koenig
2020-04-09 0:43 ` [PATCH 1/2] drm/msm/dpu: add support for color processing blocks " Fritz Koenig
2020-06-08 22:25 ` John Stultz [this message]
2020-06-08 22:36 ` John Stultz
2020-06-08 22:54 ` Rob Clark
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=CALAqxLViRrga-XW2o1J1JutFdS1d-qmmgOrEP2beNygw3A7H4A@mail.gmail.com \
--to=john.stultz@linaro.org \
--cc=amit.pundir@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hoegsberg@chromium.org \
--cc=kalyan_t@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrishn@codeaurora.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.org \
--cc=sumit.semwal@linaro.org \
--cc=travitej@codeaurora.org \
/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;
as well as URLs for NNTP newsgroup(s).