linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeykumar Sankaran <jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Sean Paul <seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Rajesh Yadav <ryadav-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	hoegsberg-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [DPU PATCH v3 5/6] drm/msm: hook up DPU with upstream DSI
Date: Fri, 01 Jun 2018 10:44:21 -0700	[thread overview]
Message-ID: <9511935cbe0911bef6622377acd3fa7c@codeaurora.org> (raw)
In-Reply-To: <20180601162113.GQ3373@art_vandelay>

On 2018-06-01 09:21, Sean Paul wrote:
> On Fri, May 25, 2018 at 02:26:06PM -0700, Jeykumar Sankaran wrote:
>> Switch DPU from dsi-staging to upstream dsi driver. To make
>> the switch atomic, this change includes:
>> - remove dpu connector layers
>> - clean up dpu connector dependencies in encoder/crtc
>> - compile out writeback and display port drivers
>> - compile out dsi-staging driver (separate patch submitted to
>>   remove the driver)
>> - adapt upstream device hierarchy
>> 
>> changes in v2:
>> 	- remove files not applicable upstream (Sean Paul)
>> 	- remove compiled out non-dsi display init (Sean Paul)
>> 	- split unrelated changes into separate patch set (Sean Paul)
>> changes in v3:
>> 	- fix compilation warning
>> 	- compile out dsi staging
>> 
>> Signed-off-by: Jeykumar Sankaran <jsanka@codeaurora.org>
>> Signed-off-by: Sean Paul <seanpaul@chromium.org>
>> Signed-off-by: Rajesh Yadav <ryadav@codeaurora.org>
>> ---
> 
> /snip
> 
>> @@ -1089,7 +1095,7 @@ void dpu_rm_release(struct dpu_rm *rm, struct
> drm_encoder *enc)
>>  {
>>  	struct dpu_rm_rsvp *rsvp;
>>  	struct drm_connector *conn;
>> -	uint64_t top_ctrl;
>> +	uint64_t top_ctrl = 0;
> 
> This will always just force the else path. Just remove it all.
> 
> Sean
> 
> /snip
Sure. Taking care of it in the next patch set. FYI, most of the RSVP 
handling and custom top_ctrl are stripped down in the next series of 
clean up's.
-- 
Jeykumar S
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno

  reply	other threads:[~2018-06-01 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 21:26 [DPU PATCH v3 0/6] Switch DPU to use upstream DSI driver for SDM845 Jeykumar Sankaran
2018-05-25 21:26 ` [DPU PATCH v3 2/6] drm/msm: remove support for ping pong split topology Jeykumar Sankaran
2018-05-25 21:26 ` [DPU PATCH v3 4/6] drm/msm: strip down custom event ioctl's Jeykumar Sankaran
     [not found] ` <1527283567-6546-1-git-send-email-jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-05-25 21:26   ` [DPU PATCH v3 1/6] drm/msm: remove display stream compression(DSC) support for SM845 Jeykumar Sankaran
2018-05-25 21:26   ` [DPU PATCH v3 3/6] drm/msm: remove panel autorefresh support for SDM845 Jeykumar Sankaran
2018-05-25 21:26   ` [DPU PATCH v3 5/6] drm/msm: hook up DPU with upstream DSI Jeykumar Sankaran
     [not found]     ` <1527283567-6546-6-git-send-email-jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-06-01 16:21       ` Sean Paul
2018-06-01 17:44         ` Jeykumar Sankaran [this message]
2018-05-25 21:26   ` [DPU PATCH v3 6/6] drm/msm: remove dsi-staging driver Jeykumar Sankaran

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=9511935cbe0911bef6622377acd3fa7c@codeaurora.org \
    --to=jsanka-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=hoegsberg-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ryadav-sgV2jX0FEOL9JmXXK+q4OQ@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).