From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
David Airlie <airlied@linux.ie>,
Brian Starkey <brian.starkey@arm.com>,
Alexandru-Cosmin Gheorghe <alexandru-cosmin.gheorghe@arm.com>,
Eric Anholt <eric@anholt.net>,
Boris Brezillon <boris.brezillon@bootlin.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Daniel Stone <daniels@collabora.com>,
Rob Clark <robdclark@gmail.com>
Subject: [PATCH v10 0/3] drm: Introduce writeback connectors
Date: Tue, 12 Jun 2018 14:52:30 +0100 [thread overview]
Message-ID: <20180612135233.18575-1-Liviu.Dudau@arm.com> (raw)
Hi,
This is v10 of the writeback connector series. Compared to v9 I've
reverted to the v6 way of cleaning up the writeback job in the cleanup_work()
function, where we also drop the reference to the job's framebuffer. I was
trying to come up with a reference counted implementation for the job, but
Sean Paul pointed out to Brian that it seems to be safe to free work_struct
structures in the workqueue callback, so we are going back to the original
implementation.
While doing that, I've also updated the patcheset to use the latest
drm_framebuffer_{put,get,assign} functions for managing the framebuffer
reference that the wriback job holds.
I will ask Gustavo to pull this series into drm-misc if there are no further
comments.
Best regards,
Liviu
Brian Starkey (2):
drm: Add writeback connector type
drm: writeback: Add out-fences for writeback connectors
Liviu Dudau (1):
drm: writeback: Add client capability for exposing writeback
connectors
Documentation/gpu/drm-kms.rst | 9 +
drivers/gpu/drm/Makefile | 2 +-
drivers/gpu/drm/drm_atomic.c | 223 ++++++++++++++-
drivers/gpu/drm/drm_atomic_helper.c | 25 ++
drivers/gpu/drm/drm_connector.c | 4 +-
drivers/gpu/drm/drm_ioctl.c | 7 +
drivers/gpu/drm/drm_mode_config.c | 5 +
drivers/gpu/drm/drm_writeback.c | 350 +++++++++++++++++++++++
include/drm/drm_atomic.h | 11 +
include/drm/drm_connector.h | 13 +
include/drm/drm_file.h | 7 +
include/drm/drm_mode_config.h | 23 ++
include/drm/drm_modeset_helper_vtables.h | 11 +
include/drm/drm_writeback.h | 130 +++++++++
include/uapi/drm/drm.h | 9 +
include/uapi/drm/drm_mode.h | 1 +
16 files changed, 819 insertions(+), 11 deletions(-)
create mode 100644 drivers/gpu/drm/drm_writeback.c
create mode 100644 include/drm/drm_writeback.h
--
2.17.1
next reply other threads:[~2018-06-12 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 13:52 Liviu Dudau [this message]
2018-06-12 13:52 ` [PATCH v10 1/3] drm: Add writeback connector type Liviu Dudau
2018-06-12 13:52 ` [PATCH v10 2/3] drm: writeback: Add out-fences for writeback connectors Liviu Dudau
2018-06-12 13:52 ` [PATCH v10 3/3] drm: writeback: Add client capability for exposing " Liviu Dudau
2018-06-13 10:26 ` Brian Starkey
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=20180612135233.18575-1-Liviu.Dudau@arm.com \
--to=liviu.dudau@arm.com \
--cc=airlied@linux.ie \
--cc=alexandru-cosmin.gheorghe@arm.com \
--cc=boris.brezillon@bootlin.com \
--cc=brian.starkey@arm.com \
--cc=corbet@lwn.net \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.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
all inboxes | Powered by JetHome®