From: John Stultz <john.stultz@linaro.org>
To: Maarten Lankhorst <maarten.lankhorst@canonical.com>,
Erik Gilling <konkers@android.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Rob Clark <robclark@gmail.com>,
Sumit Semwal <sumit.semwal@linaro.org>
Cc: linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
lkml <linux-kernel@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>,
Greg KH <gregkh@linuxfoundation.org>
Subject: [RFD] Proposal for merging Android sync driver in staging
Date: Wed, 27 Feb 2013 18:14:24 -0800 [thread overview]
Message-ID: <512EBD80.8070101@linaro.org> (raw)
I'd like to get a discussion going about submitting the Android sync
driver to staging.
I know there is currently some very similar work going on with the
dmabuf-fences, and rather then both approaches being worked out
individually on their own, I suspect there could be better collaboration
around this effort.
So my proposal is that we merge the Android sync driver into staging.
In my mind, this has the following benefits:
1) It allows other drivers that depend on the sync interface to also be
submitted to staging, rather then forcing those drivers to be hidden
away in various out of tree git repos, location unknown.
2) It would provide a baseline view to the upstream community of the
interface Android is using, providing a real-world, active use case of
the functionality.
Once the sync driver is in staging, if the dmabuf-fences work is fully
sufficient to replace the Android sync driver, we should be able to
whittle down the sync driver until its just a interface shim (and at
which point efforts can be made to convert Android userland over to
dmabuf-fences).
However, if the dmabuf-fences work is not fully sufficient to replace
the android sync driver, we should be able to at least to whittle down
the driver to those specific differences, which would provide a concrete
example of where the dmabuf-fences, or other work may need to be
expanded, or if maybe the sync driver is the better approach.
I've gone through the Android tree and reworked the sync driver to live
in staging, while still preserving the full patch history/authorship.
You can checkout the reworked patch queue here:
http://git.linaro.org/gitweb?p=people/jstultz/android-dev.git;a=shortlog;h=refs/heads/dev/sync-staging
If folks would take a look and let me know what they think of the
changes as well as what they think about pushing it to staging, or other
ideas for how to improve collaboration so we can have common interfaces
here, I'd appreciate it.
Also note: I've done this so far without any feedback from the Android
devs (despite my reaching out to Erik a few times recently), so if they
object to pushing it to staging, in deference to it being their code
I'll back off, even though I do think it would be good to have the code
get more visibility upstream in staging. I don't mean to step on
anyone's toes. :)
thanks
-john
next reply other threads:[~2013-02-28 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 2:14 John Stultz [this message]
2013-02-28 2:32 ` [RFD] Proposal for merging Android sync driver in staging Greg KH
2013-02-28 18:28 ` John Stultz
2013-02-28 3:03 ` Erik Gilling
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=512EBD80.8070101@linaro.org \
--to=john.stultz@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=konkers@android.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=robclark@gmail.com \
--cc=sumit.semwal@linaro.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;
as well as URLs for NNTP newsgroup(s).