From: Alexey Minnekhanov <alexeymin@postmarketos.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Paul Sajna <sajattack@postmarketos.org>,
barnabas.czeman@mainlining.org
Subject: Re: [PATCH] drm/msm/mdp5: drop support for MSM8998, SDM630 and SDM660
Date: Wed, 17 Dec 2025 18:05:31 +0300 [thread overview]
Message-ID: <8e1d33ff-d902-4ae9-9162-e00d17a5e6d1@postmarketos.org> (raw)
In-Reply-To: <20251211-mdp5-drop-dpu3-v1-1-0a0186d92757@oss.qualcomm.com>
On 11.12.2025 04:25, Dmitry Baryshkov wrote:
> Currently MDP5 3.x (MSM8998, SDM630 and SDM660) platforms are support
> by both DPU and MDP5 drivers. Support for them in the DPU driver is
> mature enough, so it's no longer sensible to keep them enabled in the
> MDP5 driver. Not to mention that MSM8998 never used an MDP5 compatible
> string. Drop support for the MDP5 3.x genration inside the MDP5
> driver and migrate those to the DPU driver only.
>
> Note: this will break if one uses the DT generated before v6.3 as they
> had only the generic, "qcom,mdp5" compatible string for SDM630 and
> SDM660. However granted that we had two LTS releases inbetween I don't
> think it is an issue.
>
I've retested DPU driver on our downstream release based on 6.18 (by
using msm.prefer_mdp5=false kernel cmdline parameter) on all devices
at my disposal, and I can confirm DPU driver working fine an all SDM660,
SDM636 ones, but not on SDM630. Some logs from sdm630-sony-nile-pioneer
(Sony Xperia XA2):
[ 2.356546] msm_dpu c901000.display-controller: bound c994000.dsi
(ops dsi_ops [msm])
[ 2.357328] adreno 5000000.gpu: GPU speedbin fuse 146 (0x92), mapped
to opp-supp-hw 0x4
[ 2.364802] msm_dpu c901000.display-controller: bound 5000000.gpu
(ops a3xx_ops [msm])
[ 2.444649] [drm:dpu_kms_hw_init:1173] dpu hardware revision:0x30030000
[ 2.449793] [drm] Initialized msm 1.13.0 for
c901000.display-controller on minor 1
...
[ 2.911900] [drm:_dpu_encoder_phys_cmd_wait_for_ctl_start:654] [dpu
error]enc33 intf1 ctl start interrupt wait failed
[ 2.911916] [drm:dpu_kms_wait_for_commit_done:525] [dpu error]wait
for commit done returned -22
...
[ 3.176171] [drm:_dpu_encoder_phys_cmd_wait_for_ctl_start:654] [dpu
error]enc33 intf1 ctl start interrupt wait failed
[ 3.176367] [drm:dpu_kms_wait_for_commit_done:525] [dpu error]wait
for commit done returned -22
Which results in horrendous ~3-5 fps in shell.
The block "enc33 intf1 ctl start interrupt wait failed" + "wait for
commit done returned -22" is repeated few times per second whenever
the display is turned on, and stops when it's turned off.
Meanwhile it is working fine using MDP5 driver (msm.prefer_mdp5=true).
Well, as fine as possible considering [1], using several FD_MESA_DEBUG
tricks to work around GPU issues.
P.S. I have not yet tested MSM8998, but I can try if required
[1] https://gitlab.freedesktop.org/mesa/mesa/-/issues/8442
--
Regards,
Alexey Minnekhanov
next prev parent reply other threads:[~2025-12-17 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 1:25 Dmitry Baryshkov
2025-12-16 12:22 ` Konrad Dybcio
2025-12-17 15:05 ` Alexey Minnekhanov [this message]
2025-12-17 16:34 ` Dmitry Baryshkov
2025-12-18 11:23 ` Konrad Dybcio
2025-12-18 13:49 ` Dmitry Baryshkov
2025-12-18 13:54 ` Konrad Dybcio
2025-12-18 14:26 ` Dmitry Baryshkov
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=8e1d33ff-d902-4ae9-9162-e00d17a5e6d1@postmarketos.org \
--to=alexeymin@postmarketos.org \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=barnabas.czeman@mainlining.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sajattack@postmarketos.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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®