From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Kuogee Hsieh <quic_khsieh@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: Thu, 25 May 2023 11:10:24 -0700 [thread overview]
Message-ID: <208f05b3-ed92-5b22-6200-8bb28d62fd77@quicinc.com> (raw)
In-Reply-To: <7deff127-4c6d-1f59-33a8-f44eea86bacd@quicinc.com>
On 5/25/2023 10:57 AM, Kuogee Hsieh wrote:
>
> On 5/24/2023 5:58 AM, Leonard Lausen wrote:
>>>>>>>> [ 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/
>>>> 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.
>> Hi Kuogee,
>>
>> thank you. Verified the v6 patch fixes the regression when ported to
>> 6.3.3. One non-fatal issue remains: Suspending and resuming the system
>> while USB-C DP monitor is connected triggers an error, though the system
>> recovers within a second without the need to unplug the cable.
>>
>> [drm:drm_mode_config_helper_resume] *ERROR* Failed to resume (-107)
>>
>>
>> dmesg snippet related to the suspend below
>>
>>
>> [ 197.845110] usb 2-1.4.4: reset SuperSpeed USB device number 12
>> using xhci-hcd
>> [ 198.235191] [drm:drm_mode_config_helper_resume] *ERROR* Failed to
>> resume (-107)
>
> Hi Leonard,
>
> I did not see this problem at my setup (Kodiak) during suspend/resume.
>
> Will investigate more on Trogdor device.
>
> Thanks,
>
Hi Leonard
Feel free to open a bug for this and assign to me, we can check this and
ask more info if needed on that bug.
Thanks
Abhinav
>
>> [ 198.528638] OOM killer enabled.
>> [ 198.531866] Restarting tasks ...
>> [ 198.531994] usb 1-1.4.4.1: USB disconnect, device number 27
>> [ 198.532223] usb 1-1.4.3: USB disconnect, device number 23
>> [ 198.532509] usb 1-1.4.2.1: USB disconnect, device number 29
>> [ 198.534805] r8152-cfgselector 2-1.4.4.2: USB disconnect, device
>> number 13
>> [ 198.535444] done.
>> [ 198.535536] usb 1-1.1: USB disconnect, device number 15
>> [ 198.567811] random: crng reseeded on system resumption
>> [ 198.583431] PM: suspend exit
next prev parent reply other threads:[~2023-05-25 18:11 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
2023-05-24 12:58 ` Leonard Lausen
2023-05-25 17:57 ` Kuogee Hsieh
2023-05-25 18:10 ` Abhinav Kumar [this message]
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=208f05b3-ed92-5b22-6200-8bb28d62fd77@quicinc.com \
--to=quic_abhinavk@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_bjorande@quicinc.com \
--cc=quic_khsieh@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®