public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeykumar Sankaran <jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: hoegsberg-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	Jeykumar Sankaran
	<jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	seanpaul-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
	robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: [PATCH v2 0/4] reserve RM resources in private obj state
Date: Wed, 13 Feb 2019 17:52:18 -0800	[thread overview]
Message-ID: <1550109142-28303-1-git-send-email-jsanka@codeaurora.org> (raw)

v2 patches for [1]. 

changes in v2:
	- Reserve and track hw resources allocated per
	  display in subclassed drm private object states. 
	- Private objects are created per CRTC.

[1] https://patchwork.freedesktop.org/series/50722/

Follow up series will be submitted to clean up RM iterator
API's.

Thanks and Regards,
Jeykumar S.

Jeykumar Sankaran (4):
  drm/msm/dpu: add atomic private object to dpu crtc
  drm/msm/dpu: track HW resources using private object state
  drm/msm/dpu: remove reserve in encoder mode_set
  drm/msm/dpu: remove mode_set_complete

 drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h    |  10 +-
 drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 163 ++++++++++------------------
 drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c     |  73 ++++++++++++-
 drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h     |  32 ++++++
 drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c      | 131 +++++++++++++++-------
 drivers/gpu/drm/msm/disp/dpu1/dpu_rm.h      |   8 +-
 6 files changed, 257 insertions(+), 160 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno

             reply	other threads:[~2019-02-14  1:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  1:52 Jeykumar Sankaran [this message]
     [not found] ` <1550109142-28303-1-git-send-email-jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2019-02-14  1:52   ` [PATCH v2 1/4] drm/msm/dpu: add atomic private object to dpu crtc Jeykumar Sankaran
     [not found]     ` <1550109142-28303-2-git-send-email-jsanka-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2019-03-04 21:32       ` Sean Paul
2019-03-05 19:34         ` Jeykumar Sankaran
2019-03-05 20:18           ` [Freedreno] " Sean Paul
2019-02-14  1:52   ` [PATCH v2 2/4] drm/msm/dpu: track HW resources using private object state Jeykumar Sankaran
2019-02-14  1:52   ` [PATCH v2 3/4] drm/msm/dpu: remove reserve in encoder mode_set Jeykumar Sankaran
2019-02-14  1:52   ` [PATCH v2 4/4] drm/msm/dpu: remove mode_set_complete 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=1550109142-28303-1-git-send-email-jsanka@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=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