Re: [PATCH v2 2/2] drm/msm/dpu: Fix timeout issues on command mode panels

[AngeloGioacchino Del Regno]

Il 02/10/21 00:33, Dmitry Baryshkov ha scritto:
> On 11/09/2021 19:39, AngeloGioacchino Del Regno wrote:
> > In function dpu_encoder_phys_cmd_wait_for_commit_done we are always
> > checking if the relative CTL is started by waiting for an interrupt
> > to fire: it is fine to do that, but then sometimes we call this
> > function while the CTL is up and has never been put down, but that
> > interrupt gets raised only when the CTL gets a state change from
> > 0 to 1 (disabled to enabled), so we're going to wait for something
> > that will never happen on its own.
> >
> > Solving this while avoiding to restart the CTL is actually possible
> > and can be done by just checking if it is already up and running
> > when the wait_for_commit_done function is called: in this case, so,
> > if the CTL was already running, we can say that the commit is done
> > if the command transmission is complete (in other terms, if the
> > interface has been flushed).
>
> I've compared this with the MDP5 driver, where we always wait for PP_DONE 
> interrupt. Would it be enough to always wait for it (= always call 
> dpu_encoder_phys_cmd_wait_for_tx_complete())?

This sets my delay record to reply to two months. Great achievement!

Jokes apart, yes it would make sense to do that, it's something that works
at least... but we should verify that such a thing doesn't break new platforms
(like sm8150 and newer).