linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Sean Paul <seanpaul@chromium.org>
Cc: Laura Abbott <labbott@redhat.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Sumit Semwal <sumit.semwal@linaro.org>
Subject: [RFC PATCH 0/2] dmabuf import interfaces for vgem
Date: Thu,  6 Apr 2017 16:18:31 -0700	[thread overview]
Message-ID: <1491520713-14277-1-git-send-email-labbott@redhat.com> (raw)

Hi,

Ion[1] is making progress towards moving out of staging. I'd like to take
advantage of the vgem driver for development of unit tests for Ion. To
do this properly, vgem needs to support importing of foreign handles. This
is an RFC to add that support. This passes the existing vgem_basic unit
test. I plan to extend that test with support for testing import as well.
RFC is for general direction and feedback since I'm not that familiar with
DRM internals.

Thanks,
Laura

[1] lkml.kernel.org/r/<1491245884-15852-1-git-send-email-labbott@redhat.com>

Laura Abbott (2):
  drm/vgem: Add a dummy platform device
  drm/vgem: Enable dmabuf import interfaces

 drivers/gpu/drm/vgem/vgem_drv.c | 147 ++++++++++++++++++++++++++++++++--------
 drivers/gpu/drm/vgem/vgem_drv.h |   3 +
 2 files changed, 122 insertions(+), 28 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-06 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 23:18 Laura Abbott [this message]
2017-04-06 23:18 ` [RFC PATCH 1/2] drm/vgem: Add a dummy platform device Laura Abbott
2017-04-06 23:18 ` [RFC PATCH 2/2] drm/vgem: Enable dmabuf import interfaces Laura Abbott
2017-04-07  7:39   ` Chris Wilson
2017-04-07 16:18     ` Laura Abbott
2017-04-07 16:58       ` Chris Wilson
2017-04-07 17:58         ` Laura Abbott
2017-04-07 21:22           ` 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=1491520713-14277-1-git-send-email-labbott@redhat.com \
    --to=labbott@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --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).