From: khsieh@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: robdclark@gmail.com, sean@poorly.run, tanmay@codeaurora.org,
abhinavk@codeaurora.org, aravindh@codeaurora.org,
airlied@linux.ie, daniel@ffwll.ch, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: skip checking LINK_STATUS_UPDATED bit
Date: Fri, 30 Oct 2020 15:06:33 -0700 [thread overview]
Message-ID: <546018237be3f05b4eb33c916ed1d939@codeaurora.org> (raw)
In-Reply-To: <160323215566.884498.14018580767640192186@swboyd.mtv.corp.google.com>
On 2020-10-20 15:15, Stephen Boyd wrote:
> Quoting Kuogee Hsieh (2020-10-20 09:59:59)
>> No need to check LINK_STATuS_UPDATED bit before
>
> LINK_STATUS_UPDATED?
>
>> return 6 bytes of link status during link training.
>
> Why?
>
>> This patch also fix phy compliance test link rate
>> conversion error.
>
> How?
>
>>
>> Signed-off-by: Kuogee Hsieh <khsieh@codeaurora.org>
>> ---
>
> Any Fixes: tag?
>
>> drivers/gpu/drm/msm/dp/dp_ctrl.c | 20 ++++++--------------
>> drivers/gpu/drm/msm/dp/dp_link.c | 24 +++++++++++-------------
>> 2 files changed, 17 insertions(+), 27 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> index 6bdaec778c4c..76e891c91c6e 100644
>> --- a/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> +++ b/drivers/gpu/drm/msm/dp/dp_ctrl.c
>> @@ -1061,23 +1061,15 @@ static bool dp_ctrl_train_pattern_set(struct
>> dp_ctrl_private *ctrl,
>> static int dp_ctrl_read_link_status(struct dp_ctrl_private *ctrl,
>> u8 *link_status)
>> {
>> - int len = 0;
>> - u32 const offset = DP_LANE_ALIGN_STATUS_UPDATED -
>> DP_LANE0_1_STATUS;
>> - u32 link_status_read_max_retries = 100;
>> -
>> - while (--link_status_read_max_retries) {
>> - len = drm_dp_dpcd_read_link_status(ctrl->aux,
>> - link_status);
>> - if (len != DP_LINK_STATUS_SIZE) {
>> - DRM_ERROR("DP link status read failed, err:
>> %d\n", len);
>> - return len;
>> - }
>> + int ret = 0, len;
>>
>> - if (!(link_status[offset] & DP_LINK_STATUS_UPDATED))
>> - return 0;
>> + len = drm_dp_dpcd_read_link_status(ctrl->aux, link_status);
>> + if (len != DP_LINK_STATUS_SIZE) {
>> + DRM_ERROR("DP link status read failed, err: %d\n",
>> len);
>> + ret = len;
>
> Could this be positive if the len is greater than 0 but not
> DP_LINK_STATUS_SIZE? Maybe the check should be len < 0? We certainly
> don't want to return some smaller size from this function, right?
>
no, it should be exactly the byte number requested to read.
otherwise, it should be failed and will re read at next run.
>> }
>>
>> - return -ETIMEDOUT;
>> + return ret;
>> }
>>
>> static int dp_ctrl_link_train_1(struct dp_ctrl_private *ctrl,
>> diff --git a/drivers/gpu/drm/msm/dp/dp_link.c
>> b/drivers/gpu/drm/msm/dp/dp_link.c
>> index c811da515fb3..58d65daae3b3 100644
>> --- a/drivers/gpu/drm/msm/dp/dp_link.c
>> +++ b/drivers/gpu/drm/msm/dp/dp_link.c
>> @@ -773,7 +773,8 @@ static int
>> dp_link_process_link_training_request(struct dp_link_private *link)
>> link->request.test_lane_count);
>>
>> link->dp_link.link_params.num_lanes =
>> link->request.test_lane_count;
>> - link->dp_link.link_params.rate = link->request.test_link_rate;
>> + link->dp_link.link_params.rate =
>> +
>> drm_dp_bw_code_to_link_rate(link->request.test_link_rate);
>
> Why are we storing bw_code in test_link_rate? This looks very
> confusing.
Test_link_rate contains link rate from dpcd read. it need to be convert
to real
rate by timing 2.7Mb before start phy compliance test.
>
>>
>> return 0;
>> }
prev parent reply other threads:[~2020-10-30 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 16:59 [PATCH] drm/msm/dp: skip checking LINK_STATUS_UPDATED bit Kuogee Hsieh
2020-10-20 22:15 ` Stephen Boyd
2020-10-30 22:06 ` khsieh [this message]
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=546018237be3f05b4eb33c916ed1d939@codeaurora.org \
--to=khsieh@codeaurora.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=aravindh@codeaurora.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 \
--cc=tanmay@codeaurora.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