Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
Date:   Tue, 23 May 2023 02:39:50 +0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From:   "Leonard Lausen" <leonard@lausen.nl>
Message-ID: <49d175ec16e3f65a18265063e51092ee8d0d79c1@lausen.nl>
TLS-Required: No
Subject: Re: [PATCH] Revert "drm/msm/dp: Remove INIT_SETUP delay"
To:     "Abhinav Kumar" <quic_abhinavk@quicinc.com>,
        "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
        "Bjorn Andersson" <andersson@kernel.org>
Cc:     regressions@lists.linux.dev,
        "Bjorn Andersson" <quic_bjorande@quicinc.com>,
        "Rob Clark" <robdclark@gmail.com>,
        "Stephen Boyd" <swboyd@chromium.org>,
        "Kuogee Hsieh" <quic_khsieh@quicinc.com>,
        "Johan Hovold" <johan+linaro@kernel.org>,
        "Sankeerth Billakanti" <quic_sbillaka@quicinc.com>,
        "Sean Paul" <sean@poorly.run>, "David Airlie" <airlied@gmail.com>,
        "Daniel Vetter" <daniel@ffwll.ch>, linux-arm-msm@vger.kernel.org,
        dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
        linux-kernel@vger.kernel.org, "Nikita Travkin" <nikita@trvn.ru>
In-Reply-To: <1345a125-f745-4fe3-0f5e-bfe84225958d@quicinc.com>
References: <1345a125-f745-4fe3-0f5e-bfe84225958d@quicinc.com>
 <b0cc40d5-6de1-91cc-e2cd-f47cc53551e4@quicinc.com>
 <ebbcd56ac883d3c3d3024d368fab63d26e02637a@lausen.nl>
 <20230508021536.txtamifw2vkfncnx@ripper>
 <3802269cd54ce105ef6dece03b1b9af575b4fa06@lausen.nl>
 <ad351c02-1c29-3601-53e8-f8cdeca2ac63@linaro.org>
Precedence: bulk

Abhinav Kumar <quic_abhinavk@quicinc.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 t=
his
>>>> week.
>>>>
>>>> Appreciate a bit of patience till then.
>>>
>>> This regression is already part of the 6.3 stable release series. Wil=
l
>>> 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?
>>=20
>>=20This is a tough situation, as landing a revert will break x13s, as n=
oted=20
>>=20by Bjorn. Given that the workaround is known at this moment, I would=
=20
>>=20like to wait for the patch from Abhinav to appear, then we can decid=
e=20
>>=20which 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.

>>> [=C2=A0 275.025497] [drm:dpu_encoder_phys_vid_wait_for_commit_done:48=
8]=20
>>>=20[dpu error]vblank timeout
>>> [=C2=A0 275.025514] [drm:dpu_kms_wait_for_commit_done:510] [dpu error=
]wait=20
>>>=20for commit done returned -110
>>> [=C2=A0 275.064141] [drm:dpu_encoder_frame_done_timeout:2382] [dpu=20
>>>=20error]enc33 frame done timeout
>
> This is a different crash but the root-cause of both the issues is the=
=20
>=20bridge hpd_enable/disable series.
>
> https://patchwork.freedesktop.org/patch/514414/
>
> This is breaking the sequence and logic of internal hpd as per my=20
>=20discussion with kuogee.
>
> We are analyzing the issue and the fix internally first and once we=20
>=20figure out all the details will post it.

Thank you!