[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49d175ec16e3f65a18265063e51092ee8d0d79c1@lausen.nl>
Date: Tue, 23 May 2023 02:39:50 +0000
From: "Leonard Lausen" <leonard@...sen.nl>
To: "Abhinav Kumar" <quic_abhinavk@...cinc.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@...aro.org>,
"Bjorn Andersson" <andersson@...nel.org>
Cc: regressions@...ts.linux.dev,
"Bjorn Andersson" <quic_bjorande@...cinc.com>,
"Rob Clark" <robdclark@...il.com>,
"Stephen Boyd" <swboyd@...omium.org>,
"Kuogee Hsieh" <quic_khsieh@...cinc.com>,
"Johan Hovold" <johan+linaro@...nel.org>,
"Sankeerth Billakanti" <quic_sbillaka@...cinc.com>,
"Sean Paul" <sean@...rly.run>, "David Airlie" <airlied@...il.com>,
"Daniel Vetter" <daniel@...ll.ch>, linux-arm-msm@...r.kernel.org,
dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, "Nikita Travkin" <nikita@...n.ru>
Subject: Re: [PATCH] Revert "drm/msm/dp: Remove INIT_SETUP delay"
Abhinav Kumar <quic_abhinavk@...cinc.com> writes:
>>>> There is no need to add the 100ms delay back yet.
>>>>
>>>> thanks for posting this but NAK on this patch till we post the fix this
>>>> week.
>>>>
>>>> Appreciate a bit of patience till then.
>>>
>>> This regression is already part of the 6.3 stable release series. Will
>>> the new patch qualify for inclusion in 6.3.y? Or will it be part of 6.4
>>> and this revert should go into 6.3.y?
>>
>> This is a tough situation, as landing a revert will break x13s, as noted
>> by Bjorn. Given that the workaround is known at this moment, I would
>> like to wait for the patch from Abhinav to appear, then we can decide
>> which of the fixes should go to the stable kernel.
I wasn't able to find new patches, though may have missed them. Is there
a decision yet how to proceed with this regression? 6.2 now being EOL
may make this a good moment to decide on the next steps.
>>> [ 275.025497] [drm:dpu_encoder_phys_vid_wait_for_commit_done:488]
>>> [dpu error]vblank timeout
>>> [ 275.025514] [drm:dpu_kms_wait_for_commit_done:510] [dpu error]wait
>>> for commit done returned -110
>>> [ 275.064141] [drm:dpu_encoder_frame_done_timeout:2382] [dpu
>>> error]enc33 frame done timeout
>
> This is a different crash but the root-cause of both the issues is the
> bridge hpd_enable/disable series.
>
> https://patchwork.freedesktop.org/patch/514414/
>
> This is breaking the sequence and logic of internal hpd as per my
> discussion with kuogee.
>
> We are analyzing the issue and the fix internally first and once we
> figure out all the details will post it.
Thank you!
Powered by blists - more mailing lists