From: Jeykumar Sankaran <jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Sean Paul <sean-p7yTbzM4H96eqtR555YLDQ@public.gmane.org>
Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jordan Crouse <jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/msm: dpu: Don't reset dpu_enc->cur_master on .disable()
Date: Tue, 02 Oct 2018 12:59:18 -0700 [thread overview]
Message-ID: <9a68ad97a1db25d7a7e37df0e43ad5f0@codeaurora.org> (raw)
In-Reply-To: <20181002191749.GD72545@art_vandelay>
On 2018-10-02 12:17, Sean Paul wrote:
> On Tue, Oct 02, 2018 at 11:09:47AM -0700, Jeykumar Sankaran wrote:
>> On 2018-09-17 13:49, Sean Paul wrote:
>> > From: Sean Paul <seanpaul@chromium.org>
>> >
>> > cur_master in dpu_encoder is assigned at modeset and cleared on
>> > .disable(). Unfortunately dpms (or enable/disable) does not guarantee
> a
>> > modeset, so cur_master is NULL when we try to re-enable it.
>> >
>> > This patch moves the NULL assignment to setup_display where it will be
>> > re-assigned later in the function.
>> >
>> The patch looks harmless to me. But the encoder->disable also calls
>> .disable() on
>> the physical encoders. If the DPMS is not invoking an enable, why does
>> it need to access cur_master when all the physical encoders are in the
>> disabled state?
>
> DPMS is invoking enable, but cur_master is currently only set on
> modeset
> which
> isn't invoked on DPMS.
>
> Sean
>
Got it! Misread the commit text.
Reviewed-by: Jeykumar Sankaran <jsanka@codeaurora.org>
>> Can we clean up the usage of cur_master if possible in the dpms path?
>>
>> Thanks,
>> Jeykumar S.
>>
>>
>> > Signed-off-by: Sean Paul <seanpaul@chromium.org>
>> > ---
>> > drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 4 ++--
>> > 1 file changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> > b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> > index c2e8985b4c54..ae03d8d43b27 100644
>> > --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> > +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
>> > @@ -1230,8 +1230,6 @@ static void dpu_encoder_virt_disable(struct
>> > drm_encoder *drm_enc)
>> > dpu_enc->phys_encs[i]->connector = NULL;
>> > }
>> >
>> > - dpu_enc->cur_master = NULL;
>> > -
>> > DPU_DEBUG_ENC(dpu_enc, "encoder disabled\n");
>> >
>> > dpu_rm_release(&dpu_kms->rm, drm_enc);
>> > @@ -2072,6 +2070,8 @@ static int dpu_encoder_setup_display(struct
>> > dpu_encoder_virt *dpu_enc,
>> > return -EINVAL;
>> > }
>> >
>> > + dpu_enc->cur_master = NULL;
>> > +
>> > memset(&phys_params, 0, sizeof(phys_params));
>> > phys_params.dpu_kms = dpu_kms;
>> > phys_params.parent = &dpu_enc->base;
>>
>> --
>> Jeykumar S
--
Jeykumar S
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
next prev parent reply other threads:[~2018-10-02 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 20:49 [PATCH] drm/msm: dpu: Don't reset dpu_enc->cur_master on .disable() Sean Paul
[not found] ` <20180917204959.205802-1-sean-p7yTbzM4H96eqtR555YLDQ@public.gmane.org>
2018-10-02 15:23 ` Bruce Wang
2018-10-02 18:09 ` Jeykumar Sankaran
[not found] ` <0238e2d56bb56f92a1a4ec9d861496bd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-02 19:17 ` Sean Paul
2018-10-02 19:59 ` Jeykumar Sankaran [this message]
[not found] ` <9a68ad97a1db25d7a7e37df0e43ad5f0-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-02 20:22 ` Sean Paul
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=9a68ad97a1db25d7a7e37df0e43ad5f0@codeaurora.org \
--to=jsanka-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=abhinavk-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sean-p7yTbzM4H96eqtR555YLDQ@public.gmane.org \
--cc=seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).