From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>,
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
Cc: 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 v1 3/5] drm/msm/dp: delete EV_HPD_INIT_SETUP
Date: Mon, 10 Jul 2023 21:15:16 +0300 [thread overview]
Message-ID: <bd16c829-183c-9898-8890-e94c6039f4d9@linaro.org> (raw)
In-Reply-To: <c1a6f23d-17d9-6f4b-407a-142913e88a35@quicinc.com>
On 10/07/2023 19:52, Kuogee Hsieh wrote:
>
> On 7/7/2023 5:34 PM, Dmitry Baryshkov wrote:
>> On 08/07/2023 02:52, Kuogee Hsieh wrote:
>>> EV_HPD_INIT_SETUP flag is used to trigger the initialization of external
>>> DP host controller. Since external DP host controller initialization had
>>> been incorporated into pm_runtime_resume(), this flag become obsolete.
>>> Lets get rid of it.
>>
>> And another question. Between patches #2 and #3 we have both
>> INIT_SETUP event and the PM doing dp_display_host_init(). Will it work
>> correctly?
>
> yes, i had added if (!dp->core_initialized) into dp_display_host_init().
>
> should I merge this patch into patch #2?
You can remove a call to dp_display_host_init() in patch #2 and then
drop EV_HOST_INIT / msm_dp_irq_postinstall() here.
>
>>
>>>
>>> Signed-off-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>>> ---
>>> drivers/gpu/drm/msm/dp/dp_display.c | 12 ------------
>>> 1 file changed, 12 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/msm/dp/dp_display.c
>>> b/drivers/gpu/drm/msm/dp/dp_display.c
>>> index 2c5706a..44580c2 100644
>>> --- a/drivers/gpu/drm/msm/dp/dp_display.c
>>> +++ b/drivers/gpu/drm/msm/dp/dp_display.c
>>> @@ -55,7 +55,6 @@ enum {
>>> enum {
>>> EV_NO_EVENT,
>>> /* hpd events */
>>> - EV_HPD_INIT_SETUP,
>>> EV_HPD_PLUG_INT,
>>> EV_IRQ_HPD_INT,
>>> EV_HPD_UNPLUG_INT,
>>> @@ -1119,9 +1118,6 @@ static int hpd_event_thread(void *data)
>>> spin_unlock_irqrestore(&dp_priv->event_lock, flag);
>>> switch (todo->event_id) {
>>> - case EV_HPD_INIT_SETUP:
>>> - dp_display_host_init(dp_priv);
>>> - break;
>>> case EV_HPD_PLUG_INT:
>>> dp_hpd_plug_handle(dp_priv, todo->data);
>>> break;
>>> @@ -1483,15 +1479,7 @@ void __exit msm_dp_unregister(void)
>>> void msm_dp_irq_postinstall(struct msm_dp *dp_display)
>>> {
>>> - struct dp_display_private *dp;
>>> -
>>> - if (!dp_display)
>>> - return;
>>> -
>>> - dp = container_of(dp_display, struct dp_display_private,
>>> dp_display);
>>> - if (!dp_display->is_edp)
>>> - dp_add_event(dp, EV_HPD_INIT_SETUP, 0, 0);
>>> }
>>> bool msm_dp_wide_bus_available(const struct msm_dp *dp_display)
>>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-07-10 18:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 23:52 [PATCH v1 0/5] incorporate pm runtime framework and eDP clean up Kuogee Hsieh
2023-07-07 23:52 ` [PATCH v1 1/5] drm/msm/dp: remove pm_runtime_xxx() from dp_power.c Kuogee Hsieh
2023-07-08 0:06 ` Dmitry Baryshkov
2023-07-09 17:21 ` [Freedreno] " Abhinav Kumar
2023-07-09 18:00 ` Dmitry Baryshkov
2023-07-09 20:32 ` Abhinav Kumar
2023-07-10 17:25 ` Kuogee Hsieh
2023-07-10 18:00 ` Dmitry Baryshkov
2023-07-09 2:34 ` Bjorn Andersson
2023-07-09 17:26 ` Abhinav Kumar
2023-07-07 23:52 ` [PATCH v1 2/5] drm/msm/dp: incorporate pm_runtime framework into DP driver Kuogee Hsieh
2023-07-08 0:04 ` Dmitry Baryshkov
2023-07-10 16:18 ` Kuogee Hsieh
2023-07-10 18:09 ` Dmitry Baryshkov
2023-07-17 21:39 ` Kuogee Hsieh
2023-07-09 2:52 ` Bjorn Andersson
2023-07-10 16:22 ` Kuogee Hsieh
2023-07-25 22:25 ` [Freedreno] " Kuogee Hsieh
2023-07-25 22:33 ` Dmitry Baryshkov
2023-07-25 23:26 ` Kuogee Hsieh
2023-07-25 23:28 ` Dmitry Baryshkov
2023-07-07 23:52 ` [PATCH v1 3/5] drm/msm/dp: delete EV_HPD_INIT_SETUP Kuogee Hsieh
2023-07-08 0:07 ` Dmitry Baryshkov
2023-07-08 0:34 ` Dmitry Baryshkov
2023-07-10 16:52 ` Kuogee Hsieh
2023-07-10 18:15 ` Dmitry Baryshkov [this message]
2023-07-07 23:52 ` [PATCH v1 4/5] drm/msm/dp: move relevant dp initialization code from bind() to probe() Kuogee Hsieh
2023-07-08 0:11 ` Dmitry Baryshkov
2023-07-10 16:57 ` Kuogee Hsieh
2023-07-10 18:13 ` Dmitry Baryshkov
2023-07-17 17:16 ` Kuogee Hsieh
2023-07-17 17:22 ` Dmitry Baryshkov
2023-07-17 20:38 ` Kuogee Hsieh
2023-07-09 3:09 ` Bjorn Andersson
2023-07-07 23:52 ` [PATCH v1 5/5] drm/msm/dp: move of_dp_aux_populate_bus() to probe for eDP Kuogee Hsieh
2023-07-08 0:32 ` Dmitry Baryshkov
[not found] ` <2278c46c-cb2c-2842-ab20-e6a334fe002b@quicinc.com>
2023-07-10 18:24 ` Dmitry Baryshkov
2023-07-20 20:27 ` Kuogee Hsieh
2023-07-20 22:19 ` Dmitry Baryshkov
2023-07-08 0:38 ` [PATCH v1 0/5] 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=bd16c829-183c-9898-8890-e94c6039f4d9@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.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_khsieh@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
all inboxes | Powered by JetHome®