From: khsieh@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: dri-devel@lists.freedesktop.org, robdclark@gmail.com,
sean@poorly.run, abhinavk@codeaurora.org,
aravindh@codeaurora.org, airlied@linux.ie, daniel@ffwll.ch,
bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] drm/msm/dp: use dp_ctrl_off_link_stream during PHY compliance test run
Date: Thu, 08 Jul 2021 14:33:51 -0700 [thread overview]
Message-ID: <3492b578fdf4e59fe594fb9207782aa1@codeaurora.org> (raw)
In-Reply-To: <CAE-0n52SxJx8kOwQddWF096PsPy-0f8bDq_ss=u6i-hisD54Hg@mail.gmail.com>
On 2021-07-08 00:03, Stephen Boyd wrote:
> Quoting Kuogee Hsieh (2021-07-06 10:20:14)
>> DP cable should always connect to DPU during the entire PHY compliance
>> testing run. Since DP PHY compliance test is executed at irq_hpd event
>> context, dp_ctrl_off_link_stream() should be used instead of
>> dp_ctrl_off().
>> dp_ctrl_off() is used for unplug event which is triggered when DP
>> cable is
>> dis connected.
>>
>> Signed-off-by: Kuogee Hsieh <khsieh@codeaurora.org>
>> ---
>
> Is this
>
> Fixes: f21c8a276c2d ("drm/msm/dp: handle irq_hpd with sink_count = 0
> correctly")
>
> or
>
> Fixes: c943b4948b58 ("drm/msm/dp: add displayPort driver support")
should be fixes at f21c8a276c2d ("drm/msm/dp: handle irq_hpd with
sink_count = 0 correctly")
>
> ? It's not clear how dp_ctrl_off() was working for compliance tests
> before commit f21c8a276c2d.
both dp_ctrl_off() and dp_ctrl_off_link_strea() are work for
dp_ctrl_process_phy_test_request()
The problem is after dp_ctrl_off(), aux channel is down, hence next phy
test will failed due to dpcd read failed.
So that cable unplugged and replug back to required to run next test
case.
dp_ctrl_off_link_stream() will keep aux channel up and other phy test
case can be continued.
>> drivers/gpu/drm/msm/dp/dp_ctrl.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> index caf71fa..27fb0f0 100644
>> --- a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> +++ b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> @@ -1530,7 +1530,7 @@ static int
>> dp_ctrl_process_phy_test_request(struct dp_ctrl_private *ctrl)
>> * running. Add the global reset just before disabling the
>> * link clocks and core clocks.
>> */
>> - ret = dp_ctrl_off(&ctrl->dp_ctrl);
>> + ret = dp_ctrl_off_link_stream(&ctrl->dp_ctrl);
>> if (ret) {
>> DRM_ERROR("failed to disable DP controller\n");
>> return ret;
WARNING: multiple messages have this Message-ID (diff)
From: khsieh@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: freedreno@lists.freedesktop.org, airlied@linux.ie,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
abhinavk@codeaurora.org, bjorn.andersson@linaro.org,
dri-devel@lists.freedesktop.org, aravindh@codeaurora.org,
sean@poorly.run
Subject: Re: [PATCH 1/7] drm/msm/dp: use dp_ctrl_off_link_stream during PHY compliance test run
Date: Thu, 08 Jul 2021 14:33:51 -0700 [thread overview]
Message-ID: <3492b578fdf4e59fe594fb9207782aa1@codeaurora.org> (raw)
In-Reply-To: <CAE-0n52SxJx8kOwQddWF096PsPy-0f8bDq_ss=u6i-hisD54Hg@mail.gmail.com>
On 2021-07-08 00:03, Stephen Boyd wrote:
> Quoting Kuogee Hsieh (2021-07-06 10:20:14)
>> DP cable should always connect to DPU during the entire PHY compliance
>> testing run. Since DP PHY compliance test is executed at irq_hpd event
>> context, dp_ctrl_off_link_stream() should be used instead of
>> dp_ctrl_off().
>> dp_ctrl_off() is used for unplug event which is triggered when DP
>> cable is
>> dis connected.
>>
>> Signed-off-by: Kuogee Hsieh <khsieh@codeaurora.org>
>> ---
>
> Is this
>
> Fixes: f21c8a276c2d ("drm/msm/dp: handle irq_hpd with sink_count = 0
> correctly")
>
> or
>
> Fixes: c943b4948b58 ("drm/msm/dp: add displayPort driver support")
should be fixes at f21c8a276c2d ("drm/msm/dp: handle irq_hpd with
sink_count = 0 correctly")
>
> ? It's not clear how dp_ctrl_off() was working for compliance tests
> before commit f21c8a276c2d.
both dp_ctrl_off() and dp_ctrl_off_link_strea() are work for
dp_ctrl_process_phy_test_request()
The problem is after dp_ctrl_off(), aux channel is down, hence next phy
test will failed due to dpcd read failed.
So that cable unplugged and replug back to required to run next test
case.
dp_ctrl_off_link_stream() will keep aux channel up and other phy test
case can be continued.
>> drivers/gpu/drm/msm/dp/dp_ctrl.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> index caf71fa..27fb0f0 100644
>> --- a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> +++ b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> @@ -1530,7 +1530,7 @@ static int
>> dp_ctrl_process_phy_test_request(struct dp_ctrl_private *ctrl)
>> * running. Add the global reset just before disabling the
>> * link clocks and core clocks.
>> */
>> - ret = dp_ctrl_off(&ctrl->dp_ctrl);
>> + ret = dp_ctrl_off_link_stream(&ctrl->dp_ctrl);
>> if (ret) {
>> DRM_ERROR("failed to disable DP controller\n");
>> return ret;
next prev parent reply other threads:[~2021-07-08 21:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 17:20 [PATCH 0/7] add fixes to pass DP Link Layer compliance test cases Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-06 17:20 ` [PATCH 1/7] drm/msm/dp: use dp_ctrl_off_link_stream during PHY compliance test run Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-08 7:03 ` Stephen Boyd
2021-07-08 7:03 ` Stephen Boyd
2021-07-08 21:33 ` khsieh [this message]
2021-07-08 21:33 ` khsieh
2021-07-06 17:20 ` [PATCH 2/7] drm/msm/dp: reduce link rate if failed at link training 1 Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-08 7:33 ` Stephen Boyd
2021-07-08 7:33 ` Stephen Boyd
2021-07-09 17:46 ` khsieh
2021-07-09 17:46 ` khsieh
2021-07-15 18:59 ` Stephen Boyd
2021-07-15 18:59 ` Stephen Boyd
2021-07-06 17:20 ` [PATCH 3/7] drm/msm/dp: reset aux controller after dp_aux_cmd_fifo_tx() failed Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-08 7:34 ` Stephen Boyd
2021-07-08 7:34 ` Stephen Boyd
2021-07-08 21:59 ` khsieh
2021-07-08 21:59 ` khsieh
2021-07-06 17:20 ` [PATCH 4/7] drm/msm/dp: replug event is converted into an unplug followed by an plug events Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-08 20:56 ` Stephen Boyd
2021-07-08 20:56 ` Stephen Boyd
2021-07-06 17:20 ` [PATCH 5/7] drm/msm/dp: return correct edid checksum after corrupted edid checksum read Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-08 7:14 ` Stephen Boyd
2021-07-08 7:14 ` Stephen Boyd
2021-07-09 18:16 ` khsieh
2021-07-09 18:16 ` khsieh
2021-07-06 17:20 ` [PATCH 6/7] drm/msm/dp: do not end dp link training until video is ready Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-06 17:20 ` [PATCH 7/7] drm/msm/dp: retrain link when loss of symbol lock detected Kuogee Hsieh
2021-07-06 17:20 ` Kuogee Hsieh
2021-07-08 7:21 ` Stephen Boyd
2021-07-08 7:21 ` Stephen Boyd
2021-07-09 17:16 ` khsieh
2021-07-09 17:16 ` khsieh
2021-07-15 19:00 ` Stephen Boyd
2021-07-15 19:00 ` Stephen Boyd
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=3492b578fdf4e59fe594fb9207782aa1@codeaurora.org \
--to=khsieh@codeaurora.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=aravindh@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.