From: Kuogee Hsieh <quic_khsieh@quicinc.com>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Leonard Lausen <leonard@lausen.nl>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>
Cc: <freedreno@lists.freedesktop.org>,
Sankeerth Billakanti <quic_sbillaka@quicinc.com>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
<regressions@lists.linux.dev>, David Airlie <airlied@gmail.com>,
"Nikita Travkin" <nikita@trvn.ru>, <linux-kernel@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
Rob Clark <robdclark@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
<linux-arm-msm@vger.kernel.org>,
Stephen Boyd <swboyd@chromium.org>, Sean Paul <sean@poorly.run>,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [Freedreno] [PATCH] Revert "drm/msm/dp: Remove INIT_SETUP delay"
Date: Tue, 23 May 2023 12:53:19 -0700 [thread overview]
Message-ID: <e547edf4-1b48-5d12-1600-45f78e7cab49@quicinc.com> (raw)
In-Reply-To: <f2d1bb37-ea83-4d5d-6ef5-ae84c26d6ac1@quicinc.com>
On 5/23/2023 11:56 AM, Abhinav Kumar wrote:
> Hi Leonard
>
> On 5/22/2023 7:39 PM, Leonard Lausen wrote:
>> 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 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.
>>
>
> Yes, the new patch to fix this issue is here
>
> https://patchwork.freedesktop.org/patch/538601/?series=118148&rev=3
>
> Apologies if you were not CCed on this, if a next version is CCed,
> will ask kuogee to cc you.
>
> Meanwhile, will be great if you can verify if it works for you and
> provide Tested-by tags.
Hi Leonard,
I had cc you with v5 patches.
Would you please verify it.
Thanks,
>
>>>>> [ 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!
next prev parent reply other threads:[~2023-05-23 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 1:06 Leonard Lausen
2023-05-08 2:15 ` Bjorn Andersson
2023-05-08 4:25 ` Abhinav Kumar
2023-05-08 11:02 ` Leonard Lausen
2023-05-08 11:30 ` Dmitry Baryshkov
2023-05-09 19:15 ` Abhinav Kumar
2023-05-23 2:39 ` Leonard Lausen
2023-05-23 18:56 ` [Freedreno] " Abhinav Kumar
2023-05-23 19:53 ` Kuogee Hsieh [this message]
2023-05-24 12:58 ` Leonard Lausen
2023-05-25 17:57 ` Kuogee Hsieh
2023-05-25 18:10 ` Abhinav Kumar
2023-06-01 19:20 ` Abhinav Kumar
2023-06-02 1:36 ` Leonard Lausen
2023-06-22 13:05 ` Leonard Lausen
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=e547edf4-1b48-5d12-1600-45f78e7cab49@quicinc.com \
--to=quic_khsieh@quicinc.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=johan+linaro@kernel.org \
--cc=leonard@lausen.nl \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=regressions@lists.linux.dev \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®