From: Kuogee Hsieh <quic_khsieh@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <dri-devel@lists.freedesktop.org>, <robdclark@gmail.com>,
<sean@poorly.run>, <swboyd@chromium.org>, <dianders@chromium.org>,
<vkoul@kernel.org>, <daniel@ffwll.ch>, <airlied@gmail.com>,
<agross@kernel.org>, <andersson@kernel.org>,
<quic_abhinavk@quicinc.com>, <quic_jesszhan@quicinc.com>,
<quic_sbillaka@quicinc.com>, <marijn.suijten@somainline.org>,
<freedreno@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 7/8] drm/msm/dp: add pm_runtime_force_suspend()/resume()
Date: Tue, 3 Oct 2023 09:43:56 -0700 [thread overview]
Message-ID: <e72ae247-459d-9f23-0583-ce6da1a30336@quicinc.com> (raw)
In-Reply-To: <CAA8EJpor3WEYmN=hQJQPFyjZGdr4j8F-XAB=2BDVRFCTNioEiA@mail.gmail.com>
On 9/27/2023 3:00 PM, Dmitry Baryshkov wrote:
> On Wed, 27 Sept 2023 at 23:54, Kuogee Hsieh <quic_khsieh@quicinc.com> wrote:
>> After incorporated pm_runtime framework into eDP/DP driver, the
> incorporating
>
>
>> original dp_pm_suspend() to handle power off both DP phy and
>> controller during suspend and dp_pm_resume() to handle power on
>> both DP phy and controller during resume are not necessary since
>> those function are replaced by dp_pm_runtime_suspend() and
>> dp_pm_runtime_resume() through pm runtime framework.
>> Therefore add pm framework provides functions,
>> pm_runtime_force_suspend()/resume() to complete incorporating pm
>> runtime framework into DP driver.
>>
>> Changes in v4:
>> -- drop both dp_pm_prepare() and dp_pm_compete() from this change
>> -- delete ST_SUSPENDED state
>> -- rewording commit text to add more details regrading the purpose
>> of this change
>>
>> Changes in v3:
>> -- replace dp_pm_suspend() with pm_runtime_force_suspend()
>> -- replace dp_pm_resume() with pm_runtime_force_resume()
>>
>> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>> ---
>> drivers/gpu/drm/msm/dp/dp_display.c | 113 ++----------------------------------
>> 1 file changed, 5 insertions(+), 108 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c b/drivers/gpu/drm/msm/dp/dp_display.c
>> index 9158a2c..711d262 100644
>> --- a/drivers/gpu/drm/msm/dp/dp_display.c
>> +++ b/drivers/gpu/drm/msm/dp/dp_display.c
>> @@ -49,7 +49,6 @@ enum {
>> ST_CONNECTED,
>> ST_DISCONNECT_PENDING,
>> ST_DISPLAY_OFF,
>> - ST_SUSPENDED,
>> };
>>
>> enum {
>> @@ -560,7 +559,7 @@ static int dp_hpd_plug_handle(struct dp_display_private *dp, u32 data)
>> drm_dbg_dp(dp->drm_dev, "Before, type=%d hpd_state=%d\n",
>> dp->dp_display.connector_type, state);
>>
>> - if (state == ST_DISPLAY_OFF || state == ST_SUSPENDED) {
>> + if (state == ST_DISPLAY_OFF) {
>> mutex_unlock(&dp->event_mutex);
>> return 0;
>> }
>> @@ -674,7 +673,7 @@ static int dp_irq_hpd_handle(struct dp_display_private *dp, u32 data)
>> drm_dbg_dp(dp->drm_dev, "Before, type=%d hpd_state=%d\n",
>> dp->dp_display.connector_type, state);
>>
>> - if (state == ST_DISPLAY_OFF || state == ST_SUSPENDED) {
>> + if (state == ST_DISPLAY_OFF) {
>> mutex_unlock(&dp->event_mutex);
>> return 0;
>> }
>> @@ -1321,110 +1320,10 @@ static int dp_pm_runtime_resume(struct device *dev)
>> return 0;
>> }
>>
>> -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;
>> - int sink_count = 0;
>> -
>> - dp = container_of(dp_display, struct dp_display_private, dp_display);
>> -
>> - mutex_lock(&dp->event_mutex);
>> -
>> - drm_dbg_dp(dp->drm_dev,
>> - "Before, type=%d core_inited=%d phy_inited=%d power_on=%d\n",
>> - dp->dp_display.connector_type, dp->core_initialized,
>> - dp->phy_initialized, dp_display->power_on);
>> -
>> - /* start from disconnected state */
>> - dp->hpd_state = ST_DISCONNECTED;
>> -
>> - /* turn on dp ctrl/phy */
>> - dp_display_host_init(dp);
>> -
>> - if (dp_display->is_edp)
>> - dp_catalog_ctrl_hpd_enable(dp->catalog);
>> -
>> - if (dp_catalog_link_is_connected(dp->catalog)) {
>> - /*
>> - * set sink to normal operation mode -- D0
>> - * before dpcd read
>> - */
>> - dp_display_host_phy_init(dp);
>> - dp_link_psm_config(dp->link, &dp->panel->link_info, false);
>> - sink_count = drm_dp_read_sink_count(dp->aux);
>> - if (sink_count < 0)
>> - sink_count = 0;
>> -
>> - dp_display_host_phy_exit(dp);
>> - }
>> -
>> - 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
>> - * also only signal audio when disconnected
>> - */
>> - if (dp->link->sink_count) {
>> - dp->dp_display.link_ready = true;
>> - } else {
>> - dp->dp_display.link_ready = false;
>> - dp_display_handle_plugged_change(dp_display, false);
>> - }
>> -
>> - drm_dbg_dp(dp->drm_dev,
>> - "After, type=%d sink=%d conn=%d core_init=%d phy_init=%d power=%d\n",
>> - dp->dp_display.connector_type, dp->link->sink_count,
>> - dp->dp_display.link_ready, dp->core_initialized,
>> - dp->phy_initialized, dp_display->power_on);
>> -
>> - mutex_unlock(&dp->event_mutex);
>> -
>> - return 0;
>> -}
>> -
>> -static int dp_pm_suspend(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;
>> -
>> - dp = container_of(dp_display, struct dp_display_private, dp_display);
>> -
>> - mutex_lock(&dp->event_mutex);
>> -
>> - drm_dbg_dp(dp->drm_dev,
>> - "Before, type=%d core_inited=%d phy_inited=%d power_on=%d\n",
>> - dp->dp_display.connector_type, dp->core_initialized,
>> - dp->phy_initialized, dp_display->power_on);
>> -
>> - /* mainlink enabled */
>> - if (dp_power_clk_status(dp->power, DP_CTRL_PM))
>> - dp_ctrl_off_link_stream(dp->ctrl);
>> -
>> - dp_display_host_phy_exit(dp);
> I was under the impression that dp_pm_runtime_suspend / _resume
> functions perform phy init/exit only in eDP cases. Can we really drop
> the main suspend/resume functions?
yes on eDP case since it is embedded.
for external DP case, there are two steps
step 1: enable DP controller's hpd block and start waiting for hpd
interrupts at dp_display_hpd_enable()
step 2: at plugin interrupts, dp_display_host_phy_init()
step 3: at unplug interrupt: dp_bridge_atomic_post_disable()
dp_display_host_phy_exi()
at runtime, there is loop between step 2 and step 3
step 4: disable DP controller's hpd block
>
>> -
>> - /* host_init will be called at pm_resume */
>> - dp_display_host_deinit(dp);
>> -
>> - dp->hpd_state = ST_SUSPENDED;
>> -
>> - drm_dbg_dp(dp->drm_dev,
>> - "After, type=%d core_inited=%d phy_inited=%d power_on=%d\n",
>> - dp->dp_display.connector_type, dp->core_initialized,
>> - dp->phy_initialized, dp_display->power_on);
>> -
>> - mutex_unlock(&dp->event_mutex);
>> -
>> - return 0;
>> -}
>> -
>> static const struct dev_pm_ops dp_pm_ops = {
>> SET_RUNTIME_PM_OPS(dp_pm_runtime_suspend, dp_pm_runtime_resume, NULL)
>> - .suspend = dp_pm_suspend,
>> - .resume = dp_pm_resume,
>> + SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend,
>> + pm_runtime_force_resume)
>> };
>>
>> static struct platform_driver dp_display_driver = {
>> @@ -1658,9 +1557,6 @@ void dp_bridge_atomic_post_disable(struct drm_bridge *drm_bridge,
>>
>> dp_display = container_of(dp, struct dp_display_private, dp_display);
>>
>> - if (dp->is_edp)
>> - dp_hpd_unplug_handle(dp_display, 0);
> Why?
dp_hpd_unplug_handle() does not tear down phy.
Therefore eDP does not need to call unplug handle.
>> -
>> mutex_lock(&dp_display->event_mutex);
>>
>> state = dp_display->hpd_state;
>> @@ -1748,6 +1644,7 @@ void dp_bridge_hpd_disable(struct drm_bridge *bridge)
>> dp_catalog_ctrl_hpd_disable(dp->catalog);
>>
>> dp_display->internal_hpd = false;
>> + dp->hpd_state = ST_DISCONNECTED;
> Why? We have only disabled sending of the HPD events. The dongle might
> still be connected.
dp_bridge_hpd_disable() disable dp controller hpd block (no more hpd
interrupt will be received).
dp_bridge_hpd_disable() should happen after DP main link had been teared
down already.
Therefore hpd_state need to be in default state so that next plugin
handle will be start with correct state.
>
>> pm_runtime_mark_last_busy(&dp->pdev->dev);
>> pm_runtime_put_autosuspend(&dp->pdev->dev);
>> --
>> 2.7.4
>>
>
> --
> With best wishes
>
> Dmitry
next prev parent reply other threads:[~2023-10-03 16:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 20:53 [PATCH v4 0/8] incorporate pm runtime framework and eDP clean up Kuogee Hsieh
2023-09-27 20:53 ` [PATCH v4 1/8] drm/msm/dp: tie dp_display_irq_handler() with dp driver Kuogee Hsieh
2023-09-27 21:04 ` Dmitry Baryshkov
2023-09-27 20:53 ` [PATCH v4 2/8] drm/msm/dp: rename is_connected with link_ready Kuogee Hsieh
2023-09-27 21:10 ` Dmitry Baryshkov
2023-09-27 20:53 ` [PATCH v4 3/8] drm/msm/dp: use drm_bridge_hpd_notify() to report HPD status changes Kuogee Hsieh
2023-09-27 20:53 ` [PATCH v4 4/8] drm/msm/dp: move parser->parse() and dp_power_client_init() to probe Kuogee Hsieh
2023-09-27 21:15 ` Dmitry Baryshkov
2023-09-27 21:17 ` Dmitry Baryshkov
2023-09-27 20:53 ` [PATCH v4 5/8] drm/msm/dp: incorporate pm_runtime framework into DP driver Kuogee Hsieh
2023-09-27 21:41 ` Dmitry Baryshkov
2023-10-02 22:24 ` Kuogee Hsieh
2023-10-02 22:48 ` Kuogee Hsieh
2023-10-03 8:05 ` Dmitry Baryshkov
2023-09-27 20:53 ` [PATCH v4 6/8] drm/msm/dp: delete EV_HPD_INIT_SETUP Kuogee Hsieh
2023-09-27 20:53 ` [PATCH v4 7/8] drm/msm/dp: add pm_runtime_force_suspend()/resume() Kuogee Hsieh
2023-09-27 22:00 ` Dmitry Baryshkov
2023-10-03 16:43 ` Kuogee Hsieh [this message]
2023-10-03 17:53 ` Dmitry Baryshkov
2023-10-03 22:12 ` Kuogee Hsieh
2023-10-03 22:36 ` Dmitry Baryshkov
2023-10-03 22:54 ` Kuogee Hsieh
2023-09-27 20:53 ` [PATCH v4 8/8] drm/msm/dp: move of_dp_aux_populate_bus() to eDP probe() Kuogee Hsieh
2023-09-27 21:57 ` Dmitry Baryshkov
2023-10-03 17:15 ` Kuogee Hsieh
2023-10-03 17:24 ` Dmitry Baryshkov
2023-10-03 17:25 ` Kuogee Hsieh
2023-10-03 17:56 ` Dmitry Baryshkov
2023-10-03 20:18 ` Kuogee Hsieh
2023-10-03 21:11 ` Dmitry Baryshkov
2023-09-27 21:10 ` [PATCH v4 0/8] incorporate pm runtime framework and eDP clean up Dmitry Baryshkov
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=e72ae247-459d-9f23-0583-ce6da1a30336@quicinc.com \
--to=quic_khsieh@quicinc.com \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@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=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--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: 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