From: Eric Anholt <eric@anholt.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Gustavo Padovan <gustavo.padovan@collabora.com>
Subject: Re: [PATCH 3/3] drm/vc4: Add support for dma-buf fencing.
Date: Wed, 12 Apr 2017 10:33:51 -0700 [thread overview]
Message-ID: <87wpap7cow.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20170412124818.gupwxi732srzeqh7@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
Daniel Vetter <daniel@ffwll.ch> writes:
> On Mon, Apr 10, 2017 at 06:44:14PM -0700, Eric Anholt wrote:
>> This is needed for proper synchronization with display on another DRM
>> device (pl111 or tinydrm) with buffers produced by vc4 V3D. Fixes the
>> new igt vc4_dmabuf_poll testcase, and rendering of one of the glmark2
>> desktop tests on pl111+vc4.
>>
>> This doesn't yet introduce waits on other device's fences before vc4's
>> rendering/display, because I don't have testcases for them.
>>
>> Signed-off-by: Eric Anholt <eric@anholt.net>
>> Cc: Gustavo Padovan <gustavo.padovan@collabora.com>
>
> So not sure I didn't look hard enough or why exactly, but I didn't find
> anything like ->prepare_fb as implemented in e.g. drm_fb_cma_prepare_fb().
> Where is that? Otherwise looks good to me.
Yeah, I need to sort that out for vc4 as a consumer of busy buffers
still. This patch just does vc4 as the producer.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-04-12 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 1:44 [PATCH 1/3] drm/msm: Expose our reservation object when exporting a dmabuf Eric Anholt
2017-04-11 1:44 ` [PATCH 2/3] drm/etnaviv: " Eric Anholt
2017-04-12 12:47 ` Daniel Vetter
2017-04-12 12:54 ` Lucas Stach
2017-04-12 17:32 ` Eric Anholt
2017-04-11 1:44 ` [PATCH 3/3] drm/vc4: Add support for dma-buf fencing Eric Anholt
2017-04-11 9:35 ` Chris Wilson
2017-04-11 17:43 ` Eric Anholt
2017-04-12 12:49 ` Daniel Vetter
2017-04-12 12:48 ` Daniel Vetter
2017-04-12 17:33 ` Eric Anholt [this message]
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=87wpap7cow.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.com \
--cc=linux-kernel@vger.kernel.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®