From: Brian Starkey <brian.starkey@arm.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
liviu.dudau@arm.com, laurent.pinchart@ideasonboard.com,
linux-media@vger.kernel.org
Subject: Re: [PATCH 2/6] drm: writeback: Add out-fences for writeback connectors
Date: Tue, 18 Apr 2017 18:35:07 +0100 [thread overview]
Message-ID: <20170418173507.GB325@e106950-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170414121114.6e6eee7a@bbrezillon>
On Fri, Apr 14, 2017 at 12:11:14PM +0200, Boris Brezillon wrote:
>On Fri, 25 Nov 2016 16:49:00 +0000
>Brian Starkey <brian.starkey@arm.com> wrote:
>
>> Add the OUT_FENCE_PTR property to writeback connectors, to enable
>> userspace to get a fence which will signal once the writeback is
>> complete. It is not allowed to request an out-fence without a
>> framebuffer attached to the connector.
>>
>> A timeline is added to drm_writeback_connector for use by the writeback
>> out-fences.
>>
>> In the case of a commit failure or DRM_MODE_ATOMIC_TEST_ONLY, the fence
>> is set to -1.
>>
>> Changes from v2:
>> - Rebase onto Gustavo Padovan's v9 explicit sync series
>> - Change out_fence_ptr type to s32 __user *
>
>Don't know what happened, but I still see s32 __user * types in this
>patch (I had to patch it to make in work on top of 4.11-rc1).
Yeah this really confused me too when rebasing. Given that this patch
predates Gustavo's change to s32 I can only assume I typo'd and meant
s64 in this commit message.
-Brian
next prev parent reply other threads:[~2017-04-18 17: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 [this message]
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 ` [RFC PATCH v3 0/6] Introduce writeback connectors Boris Brezillon
2017-04-18 17:31 ` 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=20170418173507.GB325@e106950-lin.cambridge.arm.com \
--to=brian.starkey@arm.com \
--cc=boris.brezillon@free-electrons.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).