dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v8 4/4] drm/dp: Track MST link bandwidth
Date: Mon, 1 May 2017 10:24:52 +0200	[thread overview]
Message-ID: <0fb430d1-2b5a-3891-e668-9ede083e7d52@linux.intel.com> (raw)
In-Reply-To: <1493421260-3146-1-git-send-email-dhinakaran.pandiyan@intel.com>

Op 29-04-17 om 01:14 schreef Dhinakaran Pandiyan:
> From: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
>
> Use the added helpers to track MST link bandwidth for atomic modesets.
> Link bw is acquired in the ->atomic_check() phase when CRTCs are being
> enabled with drm_atomic_find_vcpi_slots(). Similarly, link bw is released
> during ->atomic_check() with the connector helper callback ->atomic_check()
> when CRTCs are disabled.
>
> v6: active_changed does not alter vcpi allocations (Maarten)
> v5: Implement connector->atomic_check() in place of atomic_release()
> v4: Return an int from intel_dp_mst_atomic_release() (Maarten)
> v3:
>  Handled the case where ->atomic_release() is called more than once
>  during an atomic_check() for the same state.
> v2:
>  Squashed atomic_release() implementation and caller (Daniel)
>  Fixed logic for connector-crtc switching case (Daniel)
>  Fixed logic for suspend-resume case.
>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Archit Taneja <architt@codeaurora.org>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Harry Wentland <Harry.wentland@amd.com>
> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Missing changes since v7. ;)
Otherwise this looks good, if testbot is happy too then for the whole series:

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-05-01  8:24 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 [this message]
2017-05-01 16:58         ` Pandiyan, Dhinakaran
2017-04-24 15:53 ` [PATCH v7 0/4] Adding driver-private objects to atomic state Harry Wentland
2017-04-27  0:40   ` 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=0fb430d1-2b5a-3891-e668-9ede083e7d52@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --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