From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Starkey <brian.starkey@arm.com>
Cc: linux-media@vger.kernel.org, liviu.dudau@arm.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
laurent.pinchart@ideasonboard.com
Subject: Re: [RFC PATCH v3 0/6] Introduce writeback connectors
Date: Fri, 14 Apr 2017 11:35:17 +0200 [thread overview]
Message-ID: <20170414113517.323ab297@bbrezillon> (raw)
In-Reply-To: <1480092544-1725-1-git-send-email-brian.starkey@arm.com>
Hi Brian,
On Fri, 25 Nov 2016 16:48:58 +0000
Brian Starkey <brian.starkey@arm.com> wrote:
> Hi,
>
> This is v3 of my series introducing a new connector type:
> DRM_MODE_CONNECTOR_WRITEBACK
> See v1 and v2 here: [1] [2]
>
> Writeback connectors are used to expose the memory writeback engines
> found in some display controllers, which can write a CRTC's
> composition result to a memory buffer.
> This is useful e.g. for testing, screen-recording, screenshots,
> wireless display, display cloning, memory-to-memory composition.
>
> Writeback connectors are given a WRITEBACK_FB_ID property (which acts
> slightly differently to FB_ID, so gets a new name), as well as
> a PIXEL_FORMATS blob to list the supported writeback formats, and
> OUT_FENCE_PTR to be used for out-fences.
>
> The changes since v2 are in the commit messages of each commit.
>
> The main differences are:
> - Subclass drm_connector as drm_writeback_connector
> - Slight relaxation of core checks, to allow
> (connector->crtc && !connector->fb)
> - Dropped PIXEL_FORMATS_SIZE, which was redundant
> - Reworked the event interface, drivers don't need to deal with the
> fence directly
> - Re-ordered the commits to introduce writeback out-fences up-front.
>
> I've kept RFC on this series because the event reporting (introduction
> of drm_writeback_job) is probably up for debate.
>
> v4 will be accompanied by igt tests.
I plan to add writeback support to the VC4 driver and wanted to know if
anything has changed since this v3 (IOW, do you have a v4 + igt tests
ready)?
>
> As always, I look forward to any comments.
I'll try to review these patches. Keep in mind that I didn't follow the
initial discussions and might suggest things or ask questions that have
already been answered in previous versions of this series or on IRC.
Regards,
Boris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-14 9:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 16:48 [RFC PATCH v3 0/6] Introduce writeback connectors Brian Starkey
2016-11-25 16:48 ` [PATCH 1/6] drm: Add writeback connector type Brian Starkey
2017-04-14 10:08 ` Boris Brezillon
2017-04-18 17:34 ` Brian Starkey
2017-04-18 19:57 ` Boris Brezillon
2017-04-19 9:51 ` Brian Starkey
2017-04-19 11:34 ` Boris Brezillon
2017-04-19 12:50 ` Brian Starkey
2017-05-05 8:22 ` Boris Brezillon
2017-05-05 12:47 ` Liviu Dudau
2016-11-25 16:49 ` [PATCH 2/6] drm: writeback: Add out-fences for writeback connectors Brian Starkey
2017-04-14 10:11 ` Boris Brezillon
2017-04-18 17:35 ` Brian Starkey
2016-11-25 16:49 ` [PATCH 3/6] drm: mali-dp: Rename malidp_input_format Brian Starkey
2016-11-25 16:49 ` [PATCH 4/6] drm: mali-dp: Add support for writeback on DP550/DP650 Brian Starkey
2016-11-25 16:49 ` [PATCH 5/6] drm: mali-dp: Add RGB writeback formats for DP550/DP650 Brian Starkey
2016-11-25 16:49 ` [PATCH 6/6] drm: mali-dp: Add writeback connector Brian Starkey
2017-04-14 9:47 ` Boris Brezillon
2017-04-18 17:35 ` Brian Starkey
2017-04-14 9:35 ` Boris Brezillon [this message]
2017-04-18 17:31 ` [RFC PATCH v3 0/6] Introduce writeback connectors 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=20170414113517.323ab297@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=brian.starkey@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=liviu.dudau@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).