From: Eric Anholt <eric@anholt.net>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
Gustavo Padovan <gustavo.padovan@collabora.com>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>
Subject: Re: [RFC 0/2] drm/vc4: Async page flip cleanup
Date: Mon, 09 Apr 2018 17:13:47 -0700 [thread overview]
Message-ID: <87r2nnapfo.fsf@anholt.net> (raw)
In-Reply-To: <20180330150904.30458-1-boris.brezillon@bootlin.com>
[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]
Boris Brezillon <boris.brezillon@bootlin.com> writes:
> Hello,
>
> This is an attempt at simplifying the async page flip handling in VC4
> in order to get rid of vc4_queue_seqno_cb() and its dependencies and
> rely on fences instead.
>
> The reason I'm sending this as an RFC is because I'm pretty sure we can
> put some of the code added in patch 1 in drm_atomic_helper.c. Also, I'd
> like to have feedback from Padovan, Daniel and maybe others who have
> already thought about handling async page flips generically.
> And the last reason is that it's not been extensively tested, so it may
> not work correctly :-).
I'm certainly eager to see our custom async code die. Any KMS core
folks want to comment on this proposal?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-10 0:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 15:09 [RFC 0/2] drm/vc4: Async page flip cleanup Boris Brezillon
2018-03-30 15:09 ` [RFC 1/2] drm/vc4: Handle async page flips in the atomic_commit() path Boris Brezillon
2018-03-30 15:20 ` Boris Brezillon
2018-03-30 15:09 ` [RFC 2/2] drm/vc4: Get rid of vc4_queue_seqno_cb() and its dependencies Boris Brezillon
2018-04-10 0:13 ` 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=87r2nnapfo.fsf@anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=boris.brezillon@bootlin.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.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