From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Vinod Polimera <vpolimer@qti.qualcomm.com>,
"Vinod Polimera (QUIC)" <quic_vpolimer@quicinc.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"freedreno@lists.freedesktop.org"
<freedreno@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robdclark@gmail.com" <robdclark@gmail.com>,
"dianders@chromium.org" <dianders@chromium.org>,
"swboyd@chromium.org" <swboyd@chromium.org>,
"Kalyan Thota (QUIC)" <quic_kalyant@quicinc.com>,
"Kuogee Hsieh (QUIC)" <quic_khsieh@quicinc.com>,
"Vishnuvardhan Prodduturi (QUIC)" <quic_vproddut@quicinc.com>,
"Bjorn Andersson (QUIC)" <quic_bjorande@quicinc.com>,
"Aravind Venkateswaran (QUIC)" <quic_aravindh@quicinc.com>,
"Abhinav Kumar (QUIC)" <quic_abhinavk@quicinc.com>,
"Sankeerth Billakanti (QUIC)" <quic_sbillaka@quicinc.com>
Subject: Re: [PATCH v8 01/15] drm/msm/disp/dpu: clear dpu_assign_crtc and get crtc from connector state instead of dpu_enc
Date: Thu, 27 Oct 2022 20:40:35 +0300 [thread overview]
Message-ID: <780a3aeb-2e7f-b3ca-be58-ab24bd06d805@linaro.org> (raw)
In-Reply-To: <BN0PR02MB8173F084DD0DDAD2E312CA6DE4339@BN0PR02MB8173.namprd02.prod.outlook.com>
On 27/10/2022 16:34, Vinod Polimera wrote:
>> -----Original Message-----
>> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>> Sent: Monday, October 24, 2022 8:52 PM
>> To: Vinod Polimera (QUIC) <quic_vpolimer@quicinc.com>; dri-
>> devel@lists.freedesktop.org; linux-arm-msm@vger.kernel.org;
>> freedreno@lists.freedesktop.org; devicetree@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org; robdclark@gmail.com;
>> dianders@chromium.org; swboyd@chromium.org; Kalyan Thota (QUIC)
>> <quic_kalyant@quicinc.com>; Kuogee Hsieh (QUIC)
>> <quic_khsieh@quicinc.com>; Vishnuvardhan Prodduturi (QUIC)
>> <quic_vproddut@quicinc.com>; Bjorn Andersson (QUIC)
>> <quic_bjorande@quicinc.com>; Aravind Venkateswaran (QUIC)
>> <quic_aravindh@quicinc.com>; Abhinav Kumar (QUIC)
>> <quic_abhinavk@quicinc.com>; Sankeerth Billakanti (QUIC)
>> <quic_sbillaka@quicinc.com>
>> Subject: Re: [PATCH v8 01/15] drm/msm/disp/dpu: clear dpu_assign_crtc and
>> get crtc from connector state instead of dpu_enc
>>
>> WARNING: This email originated from outside of Qualcomm. Please be wary
>> of any links or attachments, and do not enable macros.
>>
>> On 12/10/2022 15:02, Vinod Polimera wrote:
>>> Update crtc retrieval from dpu_enc to dpu_enc connector state,
>>> since new links get set as part of the dpu enc virt mode set.
>>> The dpu_enc->crtc cache is no more needed, hence cleaning it as
>>> part of this change.
>>>
>>> Signed-off-by: Vinod Polimera <quic_vpolimer@quicinc.com>
>>> ---
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 4 ---
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 42 +++++++++---------
>> -----------
>>> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 8 ------
>>> 3 files changed, 13 insertions(+), 41 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
>> b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
>>> index 13ce321..8ec9a13 100644
>>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
>>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
>>> @@ -1029,7 +1029,6 @@ static void dpu_crtc_disable(struct drm_crtc *crtc,
>>> */
>>> if (dpu_encoder_get_intf_mode(encoder) == INTF_MODE_VIDEO)
>>> release_bandwidth = true;
>>> - dpu_encoder_assign_crtc(encoder, NULL);
>>> }
>>>
>>> /* wait for frame_event_done completion */
>>> @@ -1099,9 +1098,6 @@ static void dpu_crtc_enable(struct drm_crtc *crtc,
>>> trace_dpu_crtc_enable(DRMID(crtc), true, dpu_crtc);
>>> dpu_crtc->enabled = true;
>>>
>>> - drm_for_each_encoder_mask(encoder, crtc->dev, crtc->state-
>>> encoder_mask)
>>> - dpu_encoder_assign_crtc(encoder, crtc);
>>> -
>>> /* Enable/restore vblank irq handling */
>>> drm_crtc_vblank_on(crtc);
>>> }
>>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> index 9c6817b..d05b353 100644
>>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>>> @@ -132,11 +132,6 @@ enum dpu_enc_rc_states {
>>> * @intfs_swapped: Whether or not the phys_enc interfaces have been
>> swapped
>>> * for partial update right-only cases, such as pingpong
>>> * split where virtual pingpong does not generate IRQs
>>> - * @crtc: Pointer to the currently assigned crtc. Normally you
>>> - * would use crtc->state->encoder_mask to determine the
>>> - * link between encoder/crtc. However in this case we need
>>> - * to track crtc in the disable() hook which is called
>>> - * _after_ encoder_mask is cleared.
>>> * @connector: If a mode is set, cached pointer to the active
>> connector
>>> * @crtc_kickoff_cb: Callback into CRTC that will flush & start
>>> * all CTL paths
>>> @@ -181,7 +176,6 @@ struct dpu_encoder_virt {
>>>
>>> bool intfs_swapped;
>>>
>>> - struct drm_crtc *crtc;
>>> struct drm_connector *connector;
>>>
>>> struct dentry *debugfs_root;
>>> @@ -1288,7 +1282,7 @@ static void dpu_encoder_vblank_callback(struct
>> drm_encoder *drm_enc,
>>> struct dpu_encoder_phys *phy_enc)
>>> {
>>> struct dpu_encoder_virt *dpu_enc = NULL;
>>> - unsigned long lock_flags;
>>> + struct drm_crtc *crtc;
>>>
>>> if (!drm_enc || !phy_enc)
>>> return;
>>> @@ -1296,12 +1290,13 @@ static void dpu_encoder_vblank_callback(struct
>> drm_encoder *drm_enc,
>>> DPU_ATRACE_BEGIN("encoder_vblank_callback");
>>> dpu_enc = to_dpu_encoder_virt(drm_enc);
>>>
>>> - atomic_inc(&phy_enc->vsync_cnt);
>>> + if (!dpu_enc->connector || !dpu_enc->connector->state ||
>>> + !dpu_enc->connector->state->crtc)
>>> + return;
>>>
>>> - spin_lock_irqsave(&dpu_enc->enc_spinlock, lock_flags);
>>> - if (dpu_enc->crtc)
>>> - dpu_crtc_vblank_callback(dpu_enc->crtc);
>>> - spin_unlock_irqrestore(&dpu_enc->enc_spinlock, lock_flags);
>>> + atomic_inc(&phy_enc->vsync_cnt);
>>> + crtc = dpu_enc->connector->state->crtc;
>>> + dpu_crtc_vblank_callback(crtc);
>>
>> So, what if the user commits the mode setting change on another CPU,
>> while we are handling the vblank callback here? Can this happen?
>>
> If user issues a commit on another CPU, it will wait in the drm_atomic_helper_swap_state
> as drm_atomic_helper_commit_hw_done which does the complete_all(&commit->hw_done)
> for the current commit didn't finish yet.
Yes. But there is no interlock between commit->hw_done and vblank IRQ
processing, isn't it? This call happens when DPU processes the vblank
IRQ, so nobody stops other core from swapping the encode state on
another core.
>>>
>>> DPU_ATRACE_END("encoder_vblank_callback");
>>> }
>> --
>> With best wishes
>> Dmitry
>
> Thanks,
> Vinod P.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-10-27 17:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 12:02 [PATCH v8 00/15] Add PSR support for eDP Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 01/15] drm/msm/disp/dpu: clear dpu_assign_crtc and get crtc from connector state instead of dpu_enc Vinod Polimera
2022-10-24 15:22 ` Dmitry Baryshkov
2022-10-27 13:34 ` Vinod Polimera
2022-10-27 17:40 ` Dmitry Baryshkov [this message]
2022-11-01 11:16 ` Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 02/15] drm: add helper functions to retrieve old and new crtc Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 03/15] drm/msm/dp: use atomic callbacks for DP bridge ops Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 04/15] drm/msm/dp: Add basic PSR support for eDP Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 05/15] drm/msm/dp: use the eDP bridge ops to validate eDP modes Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 06/15] drm/msm/dp: disable self_refresh_aware after entering psr Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 07/15] drm/bridge: use atomic enable/disable callbacks for panel bridge Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 08/15] drm/bridge: add psr support for panel bridge callbacks Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 09/15] drm/msm/disp/dpu: use atomic enable/disable callbacks for encoder functions Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 10/15] drm/msm/disp/dpu: check for crtc enable rather than crtc active to release shared resources Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 11/15] drm/msm/disp/dpu: add PSR support for eDP interface in dpu driver Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 12/15] drm/msm/disp/dpu: get timing engine status from intf status register Vinod Polimera
2022-11-01 12:15 ` Marijn Suijten
2022-10-12 12:02 ` [PATCH v8 13/15] drm/msm/disp/dpu: wait for extra vsync till timing engine status is disabled Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 14/15] drm/msm/disp/dpu: reset the datapath after timing engine disable Vinod Polimera
2022-10-12 12:02 ` [PATCH v8 15/15] drm/msm/disp/dpu: clear active interface in the datapath cleanup Vinod Polimera
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=780a3aeb-2e7f-b3ca-be58-ab24bd06d805@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=devicetree@vger.kernel.org \
--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=quic_abhinavk@quicinc.com \
--cc=quic_aravindh@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_kalyant@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=quic_vproddut@quicinc.com \
--cc=robdclark@gmail.com \
--cc=swboyd@chromium.org \
--cc=vpolimer@qti.qualcomm.com \
/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®