LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: khsieh@codeaurora.org To: Stephen Boyd <swboyd@chromium.org> Cc: agross@kernel.org, bjorn.andersson@linaro.org, robdclark@gmail.com, sean@poorly.run, vkoul@kernel.org, abhinavk@codeaurora.org, aravindh@codeaurora.org, freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] drm/msm/dp: update is_connected status base on sink count at dp_pm_resume() Date: Wed, 04 Aug 2021 08:48:04 -0700 [thread overview] Message-ID: <ab2a7aadb6ada58246ec972c4938c627@codeaurora.org> (raw) In-Reply-To: <CAE-0n51yNrmrqgDrkj2+c2Bx-bYxNs1m2pQBxvVkSpBH2hxzoA@mail.gmail.com> On 2021-08-03 12:05, Stephen Boyd wrote: > Quoting Kuogee Hsieh (2021-08-03 09:25:13) >> Currently at dp_pm_resume() is_connected state is decided base on hpd >> connection >> status only. This will put is_connected in wrongly "true" state at the >> scenario >> that dongle attached to DUT but without hmdi cable connecting to it. >> Fix this >> problem by adding read sink count from dongle and decided is_connected >> state base >> on both sink count and hpd connection status. >> >> Changes in v2: >> -- remove dp_get_sink_count() cand call drm_dp_read_sink_count() >> >> Changes in v3: >> -- delete status local variable from dp_pm_resume() >> >> Fixes: d9aa6571b28ba ("drm/msm/dp: check sink_count before update >> is_connected status") >> Signed-off-by: Kuogee Hsieh <khsieh@codeaurora.org> >> --- >> drivers/gpu/drm/msm/dp/dp_display.c | 18 +++++++++++++++--- >> 1 file changed, 15 insertions(+), 3 deletions(-) >> >> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c >> b/drivers/gpu/drm/msm/dp/dp_display.c >> index 78c5301..0f39256 100644 >> --- a/drivers/gpu/drm/msm/dp/dp_display.c >> +++ b/drivers/gpu/drm/msm/dp/dp_display.c >> @@ -1313,7 +1313,7 @@ static int dp_pm_resume(struct device *dev) >> struct platform_device *pdev = to_platform_device(dev); >> struct msm_dp *dp_display = platform_get_drvdata(pdev); >> struct dp_display_private *dp; >> - u32 status; >> + int sink_count = 0; >> >> dp = container_of(dp_display, struct dp_display_private, >> dp_display); >> >> @@ -1327,14 +1327,26 @@ static int dp_pm_resume(struct device *dev) >> >> dp_catalog_ctrl_hpd_config(dp->catalog); >> >> - status = dp_catalog_link_is_connected(dp->catalog); >> + /* >> + * set sink to normal operation mode -- D0 >> + * before dpcd read >> + */ >> + dp_link_psm_config(dp->link, &dp->panel->link_info, false); >> + >> + /* if sink conencted, do dpcd read sink count */ > > s/conencted/connected/ > > This also just says what the code is doing. Why do we only read the > sink > count if the link is connected? Can we read the sink count even if the > link isn't connected and then consider sink count as 0 if trying to > read > fails? > yes, we can do that. But it will suffer aux time out and retry. i think it is better to avoid this overhead by check connection first. >> + if (dp_catalog_link_is_connected(dp->catalog)) { >> + sink_count = drm_dp_read_sink_count(dp->aux); >> + if (sink_count < 0) >> + sink_count = 0; >> + } >> >> + dp->link->sink_count = sink_count; >> /* >> * can not declared display is connected unless >> * HDMI cable is plugged in and sink_count of >> * dongle become 1 >> */ >> - if (status && dp->link->sink_count) >> + if (dp->link->sink_count) >> dp->dp_display.is_connected = true; >> else >> dp->dp_display.is_connected = false;
next prev parent reply other threads:[~2021-08-04 15:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 16:25 [PATCH v3] drm/msm/dp: update is_connected status base on sink count at dp_pm_resume() Kuogee Hsieh 2021-08-03 19:05 ` Stephen Boyd 2021-08-04 15:48 ` khsieh [this message] 2021-08-04 16:24 ` 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=ab2a7aadb6ada58246ec972c4938c627@codeaurora.org \ --to=khsieh@codeaurora.org \ --cc=abhinavk@codeaurora.org \ --cc=agross@kernel.org \ --cc=aravindh@codeaurora.org \ --cc=bjorn.andersson@linaro.org \ --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=vkoul@kernel.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: linkBe 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; as well as URLs for NNTP newsgroup(s).