From: abhinavk@codeaurora.org
To: Sean Paul <seanpaul@chromium.org>
Cc: jeykumar@quicinc.com, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, hoegsberg@google.com,
freedreno@lists.freedesktop.org, chandanu@codeaurora.org
Subject: Re: [DPU PATCH v3 1/2] drm/msm/dsi: check video mode engine status before waiting
Date: Tue, 17 Apr 2018 13:41:07 -0700 [thread overview]
Message-ID: <d51faf004b73d610fe166250c40d4407@codeaurora.org> (raw)
In-Reply-To: <20180417202520.GN73214@art_vandelay>
On 2018-04-17 13:25, Sean Paul wrote:
> On Mon, Apr 16, 2018 at 06:56:45PM -0700, Abhinav Kumar wrote:
>> Make sure the video mode engine is on before waiting
>> for the video done interrupt.
>>
>> Changes in v2:
>> - Replace pr_err with dev_err
>> - Changed error message
>>
>> Changes in v3:
>> - Move the return value check to another
>> patch
>>
>> Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
>> ---
>> drivers/gpu/drm/msm/dsi/dsi_host.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c
>> b/drivers/gpu/drm/msm/dsi/dsi_host.c
>> index 7a03a94..8df0d44 100644
>> --- a/drivers/gpu/drm/msm/dsi/dsi_host.c
>> +++ b/drivers/gpu/drm/msm/dsi/dsi_host.c
>> @@ -173,6 +173,7 @@ struct msm_dsi_host {
>>
>> bool registered;
>> bool power_on;
>> + bool enabled;
>> int irq;
>> };
>>
>> @@ -1001,7 +1002,7 @@ static void dsi_wait4video_eng_busy(struct
>> msm_dsi_host *msm_host)
>> if (!(msm_host->mode_flags & MIPI_DSI_MODE_VIDEO))
>> return;
>>
>> - if (msm_host->power_on) {
>> + if (msm_host->power_on && msm_host->enabled) {
>> dsi_wait4video_done(msm_host);
>> /* delay 4 ms to skip BLLP */
>> usleep_range(2000, 4000);
>> @@ -2203,7 +2204,7 @@ int msm_dsi_host_enable(struct mipi_dsi_host
>> *host)
>> * pm_runtime_put_autosuspend(&msm_host->pdev->dev);
>> * }
>> */
>> -
>> + msm_host->enabled = true;
>> return 0;
>> }
>>
>> @@ -2219,7 +2220,7 @@ int msm_dsi_host_disable(struct mipi_dsi_host
>> *host)
>> * Reset to disable video engine so that we can send off cmd.
>> */
>> dsi_sw_reset(msm_host);
>> -
>> + msm_host->enabled = false;
>
> I thought this was moving to the start of the function?
>
[Abhinav] Yes, my bad. While rebasing that review comment was left out.
Uploading v4 right now
>> return 0;
>> }
>>
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>> Forum,
>> a Linux Foundation Collaborative Project
>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-17 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 1:56 [DPU PATCH v3 1/2] drm/msm/dsi: check video mode engine status before waiting Abhinav Kumar
[not found] ` <1523930206-6304-1-git-send-email-abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-17 1:56 ` [DPU PATCH v3 2/2] drm/msm/dsi: implement auto PHY timing calculator for 10nm PHY Abhinav Kumar
2018-04-17 20:25 ` [DPU PATCH v3 1/2] drm/msm/dsi: check video mode engine status before waiting Sean Paul
2018-04-17 20:41 ` abhinavk [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=d51faf004b73d610fe166250c40d4407@codeaurora.org \
--to=abhinavk@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hoegsberg@google.com \
--cc=jeykumar@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=seanpaul@chromium.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