From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] android: add sync_fence_create_dma
Date: Wed, 14 Jan 2015 17:04:29 +0100 [thread overview]
Message-ID: <54B6938D.2060801@canonical.com> (raw)
In-Reply-To: <54B678B4.4020401@linux.intel.com>
Hey,
On 14-01-15 15:09, Tvrtko Ursulin wrote:
>
> Hi,
>
> On 12/03/2014 07:49 PM, Jesse Barnes wrote:
>> From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
>>
>> This allows users of dma fences to create a android fence.
>
> I couldn't figure out the motivation here vs. just exporting sync_fence_create ?
Keeping the api compatible with android. They were the first users of sync_fence_create, the conversion of android userspace fences to use fences in kernelspace was done later.
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-14 16:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 19:49 [RFC] Updated Android sync patches Jesse Barnes
2014-12-03 19:49 ` [PATCH 1/3] android: add sync_fence_create_dma Jesse Barnes
2015-01-14 14:09 ` Tvrtko Ursulin
2015-01-14 16:04 ` Maarten Lankhorst [this message]
2014-12-03 19:49 ` [PATCH 2/3] drm/i915: Android sync points for i915 v3 Jesse Barnes
2014-12-03 21:29 ` Maarten Lankhorst
2014-12-04 8:10 ` Chris Wilson
2014-12-04 9:03 ` Chris Wilson
2014-12-04 11:21 ` Daniel Vetter
2014-12-04 14:57 ` Jesse Barnes
2014-12-03 19:49 ` [PATCH 3/3] drm/i915: add fences to the request struct Jesse Barnes
2014-12-04 9:13 ` Chris Wilson
2014-12-04 11:05 ` Daniel Vetter
2014-12-04 11:29 ` Chris Wilson
2014-12-04 12:58 ` Daniel Vetter
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=54B6938D.2060801@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=tvrtko.ursulin@linux.intel.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