dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wentland <harry.wentland@amd.com>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, architt@codeaurora.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v7 0/4] Adding driver-private objects to atomic state
Date: Mon, 24 Apr 2017 11:53:43 -0400	[thread overview]
Message-ID: <de1d02eb-cb74-6b74-7b8a-3a63ef159463@amd.com> (raw)
In-Reply-To: <1492753893-3748-1-git-send-email-dhinakaran.pandiyan@intel.com>

Patches 1-3: Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Patch 4: Acked-by: Harry Wentland <harry.wentland@amd.com>

Harry

On 2017-04-21 01:51 AM, Dhinakaran Pandiyan wrote:
> Changes in this version:
> Used connector->atomic_check() to release vcpi slots instead of the
> atomic_release() callback.
>
> 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 (4):
>   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/dp: Track MST link bandwidth
>
>  drivers/gpu/drm/drm_atomic.c          |  65 +++++++++++++++
>  drivers/gpu/drm/drm_atomic_helper.c   |   5 ++
>  drivers/gpu/drm/drm_dp_mst_topology.c | 150 ++++++++++++++++++++++++++++++++++
>  drivers/gpu/drm/i915/intel_dp_mst.c   |  57 +++++++++++--
>  include/drm/drm_atomic.h              | 101 +++++++++++++++++++++++
>  include/drm/drm_dp_mst_helper.h       |  26 ++++++
>  6 files changed, 398 insertions(+), 6 deletions(-)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-04-24 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  5:51 [PATCH v7 0/4] Adding driver-private objects to atomic state Dhinakaran Pandiyan
2017-04-21  5:51 ` [PATCH v7 1/4] drm: Add " Dhinakaran Pandiyan
2017-04-25  7:37   ` Maarten Lankhorst
2017-04-27  0:36     ` [PATCH v8 " Dhinakaran Pandiyan
2017-04-21  5:51 ` [PATCH v7 2/4] drm/dp: Introduce MST topology state to track available link bandwidth Dhinakaran Pandiyan
2017-04-21  5:51 ` [PATCH v7 3/4] drm/dp: Add DP MST helpers to atomically find and release vcpi slots Dhinakaran Pandiyan
2017-04-21  5:51 ` [PATCH v7 4/4] drm/dp: Track MST link bandwidth Dhinakaran Pandiyan
2017-04-25  7:51   ` Maarten Lankhorst
2017-04-26 23:48     ` Pandiyan, Dhinakaran
2017-04-28  0:32     ` Pandiyan, Dhinakaran
2017-04-28 23:14     ` [PATCH v8 " Dhinakaran Pandiyan
2017-05-01  8:24       ` Maarten Lankhorst
2017-05-01 16:58         ` Pandiyan, Dhinakaran
2017-04-24 15:53 ` Harry Wentland [this message]
2017-04-27  0:40   ` [PATCH v7 0/4] Adding driver-private objects to atomic state 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=de1d02eb-cb74-6b74-7b8a-3a63ef159463@amd.com \
    --to=harry.wentland@amd.com \
    --cc=architt@codeaurora.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dhinakaran.pandiyan@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox