On Freitag, 6. Oktober 2023 15:38:51 CEST Dmitry Baryshkov wrote: > On 29/09/2023 23:52, Luca Weiss wrote: > > On Samstag, 23. September 2023 23:49:10 CEST Dmitry Baryshkov wrote: > >> Experimental support for MSM8953, which has MDP5 v1.16. It looks like > >> trimmed down version of MSM8996. Less SSPP, LM and PP blocks. No DSC, > >> etc. > > > > Hi Dmitry, > > > > As written on IRC, on sdm632-fairphone-fp3 with this DPU patches the > > screen is initializing and displaying stuff :) But there's some errors, > > which presumably are the reason that the screen is only updating a few > > times per second. > > > > [ 22.774205] [drm:dpu_kms_hw_init:1164] dpu hardware revision:0x10100000 > > [ 23.099806] [drm:_dpu_encoder_phys_cmd_wait_for_ctl_start:657] [dpu > > error]enc31 intf1 ctl start interrupt wait failed [ 23.099821] > > [drm:dpu_kms_wait_for_commit_done:495] [dpu error]wait for commit done > > returned -22 > > > > These messages appear about 13 times per second but as I mentioned, the > > screen *is* updating (slowly) there. > > For my understanding, does it work with the MDP5 driver? Not perfectly, but it does work. What I mean is that the panel is running at 30Hz (shown e.g. with kmscube) instead of the 60Hz it should run at. One of the comments I got is that mdp5 is essentially unmaintained so I should try DPU ;) Also I can ask someone with a video-mode panel to test, maybe it works better there. At least good to have more data points? Regards Luca > > > Also you for sure forgot to add "qcom,msm8953-mdp5" to the > > msm_mdp5_dpu_migration list, without this DPU is never even considered for > > 8953.
