All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Archit Taneja <architt@codeaurora.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org,
	Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
	Harry Wentland <Harry.wentland@amd.com>
Subject: [PATCH v5 0/5] Adding driver-private objects to atomic state
Date: Thu, 30 Mar 2017 01:42:05 -0700	[thread overview]
Message-ID: <1490863330-5359-1-git-send-email-dhinakaran.pandiyan@intel.com> (raw)

Changes in this version:
Included the 5 left over patches. Patches 1 and 5 have changed, so
I have removed Maarten's R-B for patch 5.

	1/5: Added NULL checks
	5/5: Fixed vcpi slot accounting when atomic_release() is called multiple
	times within an atomic_check()

This series introduces void * type driver-private objects in core and adds
helper functions that operate on these private objects. Drivers need to
implement object-specific functions to swap and clear object states. The
advantage of having void * for these objects in the core is objects of different
types can be managed in the same atomic state array. The series implements
DP-MST link bw tracking using the driver-private object infrastructure.

Pandiyan, Dhinakaran (5):
  drm: Add driver-private objects to atomic state
  drm/dp: Introduce MST topology state to track available link bandwidth
  drm/dp: Add DP MST helpers to atomically find and release vcpi slots
  drm: Connector helper function to release resources
  drm/dp: Track MST link bandwidth

 drivers/gpu/drm/drm_atomic.c             |  65 ++++++++++++++
 drivers/gpu/drm/drm_atomic_helper.c      |  24 +++++
 drivers/gpu/drm/drm_dp_mst_topology.c    | 150 +++++++++++++++++++++++++++++++
 drivers/gpu/drm/i915/intel_dp_mst.c      |  48 ++++++++--
 include/drm/drm_atomic.h                 |  92 +++++++++++++++++++
 include/drm/drm_dp_mst_helper.h          |  26 ++++++
 include/drm/drm_modeset_helper_vtables.h |  16 ++++
 7 files changed, 414 insertions(+), 7 deletions(-)

-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2017-03-30  8:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30  8:42 Dhinakaran Pandiyan [this message]
2017-03-30  8:42 ` [PATCH v5 1/5] drm: Add driver-private objects to atomic state Dhinakaran Pandiyan
2017-04-01  5:46   ` kbuild test robot
2017-03-30  8:42 ` [PATCH v5 2/5] drm/dp: Introduce MST topology state to track available link bandwidth Dhinakaran Pandiyan
2017-03-30  8:42 ` [PATCH v5 3/5] drm/dp: Add DP MST helpers to atomically find and release vcpi slots Dhinakaran Pandiyan
2017-04-04  1:46   ` Pandiyan, Dhinakaran
2017-03-30  8:42 ` [PATCH v5 4/5] drm: Connector helper function to release resources Dhinakaran Pandiyan
2017-03-30 10:36   ` Maarten Lankhorst
2017-04-01  2:37     ` Pandiyan, Dhinakaran
2017-04-04 19:30     ` [PATCH v6 1/5] drm: Add driver-private objects to atomic state Dhinakaran Pandiyan
2017-04-04 19:30       ` [PATCH v6 2/5] drm/dp: Introduce MST topology state to track available link bandwidth Dhinakaran Pandiyan
2017-04-04 19:30       ` [PATCH v6 3/5] drm/dp: Add DP MST helpers to atomically find and release vcpi slots Dhinakaran Pandiyan
2017-04-04 19:30       ` [PATCH v6 4/5] drm: Connector helper function to release resources Dhinakaran Pandiyan
2017-04-04 19:30       ` [PATCH v6 5/5] drm/dp: Track MST link bandwidth Dhinakaran Pandiyan
2017-03-30  8:42 ` [PATCH v5 " Dhinakaran Pandiyan
2017-03-30 11:17 ` ✗ Fi.CI.BAT: warning for Adding driver-private objects to atomic state Patchwork
2017-04-04 20:36 ` ✗ Fi.CI.BAT: failure for Adding driver-private objects to atomic state (rev6) Patchwork
2017-04-04 22:35   ` Pandiyan, Dhinakaran

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=1490863330-5359-1-git-send-email-dhinakaran.pandiyan@intel.com \
    --to=dhinakaran.pandiyan@intel.com \
    --cc=Harry.wentland@amd.com \
    --cc=architt@codeaurora.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.