From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jesse Barker <jesse.barker@linaro.org>
Cc: linux-fbdev@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
linux-media@vger.kernel.org
Subject: Re: [Linaro-mm-sig] [RFC/PATCH] fb: Add dma-buf support
Date: Thu, 21 Jun 2012 10:46:15 +0200 [thread overview]
Message-ID: <2493661.GRYQti1C6z@avalon> (raw)
In-Reply-To: <CAC57bwtvfYDGO91r3zRry+WENm7x=UZ6TdOkXpmHDbQWT0feRA@mail.gmail.com>
Hi Jesse,
Thank you for the review.
On Wednesday 20 June 2012 08:09:19 Jesse Barker wrote:
> Laurent,
>
> Your recent documentation efforts are extremely commendable. Just a
> couple of small nits below...
>
> On Wed, Jun 20, 2012 at 7:09 AM, Laurent Pinchart
>
> <laurent.pinchart@ideasonboard.com> wrote:
> > Add support for the dma-buf exporter role to the frame buffer API. The
> > importer role isn't meaningful for frame buffer devices, as the frame
> > buffer device model doesn't allow using externally allocated memory.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> > Documentation/fb/api.txt | 36 ++++++++++++++++++++++++++++++++++++
> > drivers/video/fbmem.c | 36 ++++++++++++++++++++++++++++++++++++
> > include/linux/fb.h | 12 ++++++++++++
> > 3 files changed, 84 insertions(+), 0 deletions(-)
> >
> > diff --git a/Documentation/fb/api.txt b/Documentation/fb/api.txt
> > index d4ff7de..f0b2173 100644
> > --- a/Documentation/fb/api.txt
> > +++ b/Documentation/fb/api.txt
> > @@ -304,3 +304,39 @@ extensions.
> > Upon successful format configuration, drivers update the
> > fb_fix_screeninfo
> > type, visual and line_length fields depending on the selected format. The
> > type and visual fields are set to FB_TYPE_FOURCC and FB_VISUAL_FOURCC
> > respectively. +
> > +
> > +5. DMA buffer sharing
> > +---------------------
> > +
> > +The dma-buf kernel framework allows DMA buffers to be shared across
> > devices +and applications. Sharing buffers across display devices and
> > video capture or +video decoding devices allow zero-copy operation when
> > displaying video content +produced by a hardware device such as a camera
> > or a hardware codec. This is +crucial to achieve optimal system
> > performances during video display. +
> > +While dma-buf supports both exporting internally allocated memory as a
> > dma-buf +object (known as the exporter role) and importing a dma-buf
> > object to be used +as device memory (known as the importer role), the
> > frame buffer API only +supports the exporter role, as the frame buffer
> > device model doesn't support +using externally-allocated memory.
> > +
> > +The export a frame buffer as a dma-buf file descriptors, applications
> > call the
> s/The/To
> s/descriptors/descriptor
Fixed, thanks.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-06-21 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:09 [RFC/PATCH] fb: Add dma-buf support Laurent Pinchart
2012-06-20 15:09 ` [Linaro-mm-sig] " Jesse Barker
2012-06-21 8:46 ` Laurent Pinchart [this message]
2012-06-20 15:41 ` Tomasz Stanislawski
2012-06-21 9:05 ` Laurent Pinchart
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=2493661.GRYQti1C6z@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=jesse.barker@linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.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