dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Rob Clark <robdclark@gmail.com>, Mark Yao <mark.yao@rock-chips.com>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Zach Reizner" <zachr@google.com>,
	"ML dri-devel" <dri-devel@lists.freedesktop.org>,
	"Stéphane Marchesin" <marcheu@chromium.org>
Subject: Re: [PATCH] drm/rockchip: support prime fd import
Date: Fri, 22 Apr 2016 15:46:00 +0100	[thread overview]
Message-ID: <CACvgo52Lk60GMEENDKsCsUEtbbuNoR5v149FF5NQ103DWE-1bQ@mail.gmail.com> (raw)
In-Reply-To: <CACvgo5386QeW_u_9nmEY5WLPKpCukXdiGjMZUpwfepwCRHiSsA@mail.gmail.com>

On 4 March 2016 at 17:45, Emil Velikov <emil.l.velikov@gmail.com> wrote:
> On 23 February 2016 at 23:56, Rob Clark <robdclark@gmail.com> wrote:
>> On Tue, Feb 23, 2016 at 6:29 PM, Emil Velikov <emil.l.velikov@gmail.com> wrote:
>>> Hi Zach,
>>>
>>> On 2 February 2016 at 23:37, Zach Reizner <zachr@google.com> wrote:
>>>> The prime fd to handle ioctl was not used with rockchip before. Support
>>>> was added in order to support potential uses (e.g. zero-copy video
>>>> decode, camera).
>>>>
>>> Similar patch came around a few months ago and got this reply [1]. If
>>> the situation has changed (there is an open-source driver/user for
>>> this) it should be clearly mentioned in the commit message, as opposed
>>> to "in order to support potential uses".
>>
>> hmm, well it is not driver specific uabi, and we have let several
>> other mali/img users do prime..
>>
>> I'm not sure, maybe those platforms can do a basic v4l <-> display
>> thing w/ prime.  Although upstream tends to hurt a bit for camera
>> support..
>>
> Actually... one possible user is vgem. With the series from Tiago
> "Direct userspace dma-buf mmap" hitting upstream, we can actually
> reapply the problematic parts of vgem, and get this in as well.
>
> Hopefully echoing the slogan "upstream kernel needs users for
> interfaces", did not come too much for people.
> If it did, sorry but it's a rule which was set before I came along.
>
Gents, just realised that this hasn't landed yet.

As mentioned above, my earlier 'rant' is no longer applicable so feel
free to check with the Rockchip maintainer and get this upstream.

Regards,
Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2016-04-22 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 23:37 [PATCH] drm/rockchip: support prime fd import Zach Reizner
2016-02-23 22:05 ` Stéphane Marchesin
2016-02-23 23:29 ` Emil Velikov
2016-02-23 23:56   ` Rob Clark
2016-02-24  7:20     ` Stéphane Marchesin
2016-02-24 16:01     ` Emil Velikov
2016-02-24 17:20       ` Daniel Stone
2016-03-04 17:45     ` Emil Velikov
2016-04-22 14:46       ` Emil Velikov [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=CACvgo52Lk60GMEENDKsCsUEtbbuNoR5v149FF5NQ103DWE-1bQ@mail.gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=marcheu@chromium.org \
    --cc=mark.yao@rock-chips.com \
    --cc=robdclark@gmail.com \
    --cc=zachr@google.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;
as well as URLs for NNTP newsgroup(s).