From: Sasha Levin <sashal@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Bjorn Andersson <quic_bjorande@quicinc.com>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
robdclark@gmail.com, quic_abhinavk@quicinc.com,
airlied@gmail.com, daniel@ffwll.ch, swboyd@chromium.org,
johan+linaro@kernel.org, quic_sbillaka@quicinc.com,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org
Subject: Re: [PATCH AUTOSEL 6.2 18/60] drm/msm/dp: Remove INIT_SETUP delay
Date: Wed, 1 Mar 2023 09:15:53 -0500 [thread overview]
Message-ID: <Y/9eGRUEYyN8oroU@sashalap> (raw)
In-Reply-To: <Y/xz9IcSsc8mau9s@hovoldconsulting.com>
On Mon, Feb 27, 2023 at 10:12:20AM +0100, Johan Hovold wrote:
>On Sun, Feb 26, 2023 at 09:00:03PM -0500, Sasha Levin wrote:
>> From: Bjorn Andersson <quic_bjorande@quicinc.com>
>>
>> [ Upstream commit e17af1c9d861dc177e5b56009bd4f71ace688d97 ]
>>
>> During initalization of the DisplayPort controller an EV_HPD_INIT_SETUP
>> event is generated, but with a delay of 100 units. This delay existed to
>> circumvent bug in the QMP combo PHY driver, where if the DP part was
>> powered up before USB, the common properties would not be properly
>> initialized - and USB wouldn't work.
>>
>> This issue was resolved in the recent refactoring of the QMP driver,
>> so it's now possible to remove this delay.
>>
>> While there is still a timing dependency in the current implementation,
>> test indicates that it's now possible to boot with an external display
>> on USB Type-C and have the display power up, without disconnecting and
>> reconnecting the cable.
>>
>> Signed-off-by: Bjorn Andersson <quic_bjorande@quicinc.com>
>> Reviewed-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>> Patchwork: https://patchwork.freedesktop.org/patch/518729/
>> Link: https://lore.kernel.org/r/20230117172951.2748456-1-quic_bjorande@quicinc.com
>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>This is not a bug fix and should not be backported.
Ack, I'll drop all the INIT_SETUP patches. Thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-03-01 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230227020045.1045105-1-sashal@kernel.org>
2023-02-27 2:00 ` [PATCH AUTOSEL 6.2 18/60] drm/msm/dp: Remove INIT_SETUP delay Sasha Levin
2023-02-27 9:12 ` Johan Hovold
2023-03-01 14:15 ` Sasha Levin [this message]
2023-02-27 2:00 ` [PATCH AUTOSEL 6.2 24/60] drm/msm/dsi: Add missing check for alloc_ordered_workqueue Sasha Levin
2023-02-27 2:00 ` [PATCH AUTOSEL 6.2 33/60] drm/msm/dpu: Add DSC hardware blocks to register snapshot Sasha Levin
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=Y/9eGRUEYyN8oroU@sashalap \
--to=sashal@kernel.org \
--cc=airlied@gmail.com \
--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=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=stable@vger.kernel.org \
--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