(0) 79 365 57 48 - http://blog.ffwll.ch
Best regards,
Sumit Semwal
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
On 17 December 2012 14:25, Sumit Semwal sumit.sem...@linaro.org wrote:
Apologies for re-sending, since the gmail ui 'decided' to set some
formatting options by default!
Hi Maarten,
On 14 December 2012 17:27, Maarten Lankhorst m.b.lankho...@gmail.com
wrote:
Op 14-12-12 10:36, sumit.sem
we
>> always know which buffers are being scanned out at any given time, and
>> so on.
>>
>> As an added bonus, we no longer leave the last overlay buffer pinned
>> when the display is disabled, and have been able to add the previously
>> missing vblank event handlin
On Friday 28 September 2012 01:09 PM, Maarten Lankhorst wrote:
Op 28-09-12 09:29, Rob Clark schreef:
From: Rob Clark r...@ti.com
We never really clarified if unmap could be done in atomic context.
But since mapping might require sleeping, this implies mutex in use
to synchronize
On Friday 28 September 2012 01:09 PM, Maarten Lankhorst wrote:
> Op 28-09-12 09:29, Rob Clark schreef:
>> From: Rob Clark
>>
>> We never really clarified if unmap could be done in atomic context.
>> But since mapping might require sleeping, this implies mutex in use
>> to synchronize
t;> >>if (WARN_ON(!priv || !ops
>> >> +|| !ops->owner
>>
>> Thank you for spotting this.
>> I didn'y know that try_get_module returned true is module was NULL.
>>
>> BTW. Is it worth to add ".owner = THIS_MODULE," to all dma_buf
>> exporters in this patch?
>
> Yeah, I think that makes sense. Otherwise it might get lost somewhere,
> i.e. you can smash my Ack on this.
> -Daniel
> --
> Daniel Vetter
> Mail: daniel at ffwll.ch
> Mobile: +41 (0)79 365 57 48
--
Thanks and regards,
Sumit Semwal.
--
Daniel Vetter
Mail: dan...@ffwll.ch
Mobile: +41 (0)79 365 57 48
--
Thanks and regards,
Sumit Semwal.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
gt; keeping everything stable. As such, aborting requests should only be done
> in exceptional circumstances, in this case hardware died and things are
> already locked up anyhow..
>
> ~Maarten
>
--
Thanks and best regards,
Sumit Semwal
hardware died and things are
already locked up anyhow..
~Maarten
--
Thanks and best regards,
Sumit Semwal
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Maarten,
On 27 July 2012 19:09, Maarten Lankhorst
wrote:
> A dma-fence can be attached to a buffer which is being filled or consumed
> by hw, to allow userspace to pass the buffer without waiting to another
> device. For example, userspace can call page_flip ioctl to display the
> next frame
Hi Maarten,
On 27 July 2012 19:09, Maarten Lankhorst
maarten.lankho...@canonical.com wrote:
A dma-fence can be attached to a buffer which is being filled or consumed
by hw, to allow userspace to pass the buffer without waiting to another
device. For example, userspace can call page_flip ioctl
Hi Linus,
On 25 May 2012 22:14, Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, May 25, 2012 at 2:17 AM, Sumit Semwal sumit.sem...@linaro.org wrote:
I am really sorry - I goofed up in the git URL (sent the ssh URL
instead).
I was going to send you an acerbic email asking
Hi Linus,
On 25 May 2012 22:14, Linus Torvalds wrote:
> On Fri, May 25, 2012 at 2:17 AM, Sumit Semwal
> wrote:
>>
>> I am really sorry - I goofed up in the git URL (sent the ssh URL
>> instead).
>
> I was going to send you an acerbic email asking for your priva
Hi Dave,
On 25 May 2012 14:34, Dave Airlie wrote:
> From: Dave Airlie
>
> include/linux/dma-buf.h: In function ?dma_buf_vmap?:
> include/linux/dma-buf.h:260:1: warning: no return statement in function
> returning non-void [-Wreturn-type]
>
> Reported-by: wfg at linux.intel.com
> Signed-off-by:
Hi Linus,
On 25 May 2012 13:25, Sumit Semwal wrote:
> Hi Linus,
>
> Here's the first signed-tag pull request for dma-buf framework.
>
> Could you please pull the dma-buf updates for 3.5? This includes the
> following key items:
> - mmap support
> - vmap support
> - re
for 3.5
Daniel Vetter (1):
dma-buf: mmap support
Dave Airlie (2):
dma-buf: add vmap interface
dma-buf: add initial vmap documentation
Sumit Semwal (1):
dma-buf: minor documentation fixes.
Documentation/dma
for 3.5
Daniel Vetter (1):
dma-buf: mmap support
Dave Airlie (2):
dma-buf: add vmap interface
dma-buf: add initial vmap documentation
Sumit Semwal (1):
dma-buf: minor documentation fixes.
Documentation/dma-buf
Hi Linus,
On 25 May 2012 13:25, Sumit Semwal sumit.sem...@linaro.org wrote:
Hi Linus,
Here's the first signed-tag pull request for dma-buf framework.
Could you please pull the dma-buf updates for 3.5? This includes the
following key items:
- mmap support
- vmap support
- related
Hi Dave,
On 25 May 2012 14:34, Dave Airlie airl...@gmail.com wrote:
From: Dave Airlie airl...@redhat.com
include/linux/dma-buf.h: In function ‘dma_buf_vmap’:
include/linux/dma-buf.h:260:1: warning: no return statement in function
returning non-void [-Wreturn-type]
Reported-by:
Some minor inline documentation fixes for gaps resulting from new patches.
Signed-off-by: Sumit Semwal
---
drivers/base/dma-buf.c |9 +
include/linux/dma-buf.h |3 +++
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c
Some minor inline documentation fixes for gaps resulting from new patches.
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
drivers/base/dma-buf.c |9 +
include/linux/dma-buf.h |3 +++
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/base/dma-buf.c b
Hi Dave,
On 19 May 2012 12:48, Rob Clark wrote:
> On Fri, May 18, 2012 at 12:44 PM, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> The main requirement I have for this interface is for scanning out
>> using the USB gpu devices. Since these devices have to read the
>> framebuffer on updates and
Hi Dave,
On 19 May 2012 12:48, Rob Clark rob.cl...@linaro.org wrote:
On Fri, May 18, 2012 at 12:44 PM, Dave Airlie airl...@gmail.com wrote:
From: Dave Airlie airl...@redhat.com
The main requirement I have for this interface is for scanning out
using the USB gpu devices. Since these devices
Hi Daniel, Rob,
On 11 May 2012 21:00, Rob Clark wrote:
> On Tue, Apr 24, 2012 at 4:08 AM, Daniel Vetter
> wrote:
>> Compared to Rob Clark's RFC I've ditched the prepare/finish hooks
>>
>> Cc: Rob Clark
>> Cc: Rebecca Schultz Zavin
>> Signed-Off-by: Daniel Vetter
>
> Acked-by: Rob Clark
Hi Dave,
On 17 May 2012 16:01, Dave Airlie wrote:
> From: Dave Airlie
>
> The main requirement I have for this interface is for scanning out
> using the USB gpu devices. Since these devices have to read the
> framebuffer on updates and linearly compress it, using kmaps
> is a major overhead for
Hi Dave,
On 17 May 2012 16:01, Dave Airlie airl...@gmail.com wrote:
From: Dave Airlie airl...@redhat.com
The main requirement I have for this interface is for scanning out
using the USB gpu devices. Since these devices have to read the
framebuffer on updates and linearly compress it, using
Hi Daniel, Rob,
On 11 May 2012 21:00, Rob Clark rob.cl...@linaro.org wrote:
On Tue, Apr 24, 2012 at 4:08 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
Compared to Rob Clark's RFC I've ditched the prepare/finish hooks
snip
Cc: Rob Clark rob.cl...@linaro.org
Cc: Rebecca Schultz Zavin
; IS_ERR
> >> v3: Fix Ville pointed out using buffer + kmalloc
> >> v4: add locking as per ickle review
> >> v5: allow re-exporting the original dma-buf (Daniel)
> >>
> >> Signed-off-by: Dave Airlie
> >
> > With the little comment about self-importing we'v
get_dma_buf()
dma-buf: document fd flags and O_CLOEXEC requirement
Sumit Semwal (2):
dma-buf: add dma_data_direction to unmap dma_buf_op
dma-buf: correct dummy function declarations.
Documentation/dma-buf-sharing.txt | 120 ++-
drivers/base/dma-buf.c
Airlie airl...@redhat.com
With the little comment about self-importing we've discussed on irc
added,
this is:
Reviewed-by: Daniel Vetter daniel.vet...@ffwll.ch
Reviewed-by: Rob Clark rob.cl...@linaro.org
Fwiw: Reviewed-by: Sumit Semwal sumit.sem...@linaro.org
--
Daniel Vetter
get_dma_buf()
dma-buf: document fd flags and O_CLOEXEC requirement
Sumit Semwal (2):
dma-buf: add dma_data_direction to unmap dma_buf_op
dma-buf: correct dummy function declarations.
Documentation/dma-buf-sharing.txt | 120 ++-
drivers/base/dma-buf.c
are needed for compilation
when dma-buf framework is not compiled-in.
Also, the introduction of flags in dma_buf_fd needs to be added to dummy
functions as well.
Signed-off-by: Sumit Semwal
---
include/linux/dma-buf.h | 26 +-
1 files changed, 13 insertions(+), 13
are needed for compilation
when dma-buf framework is not compiled-in.
Also, the introduction of flags in dma_buf_fd needs to be added to dummy
functions as well.
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
---
include/linux/dma-buf.h | 26 +-
1 files changed
On 20 March 2012 03:12, Rob Clark wrote:
> From: Rob Clark
>
> Otherwise subsystems will get this wrong and end up with a second
> export ioctl with the flag and O_CLOEXEC support added.
>
> Signed-off-by: Rob Clark
> Reviewed-by: Daniel Vetter
> ---
> Updated version of Daniel's original
On 19 March 2012 07:24, Rob Clark wrote:
> On Sun, Mar 18, 2012 at 6:34 PM, Daniel Vetter
> wrote:
>> v2: Fix spelling issues noticed by Rob Clark.
>>
>> Signed-off-by: Daniel Vetter
>
> Signed-off-by: Rob Clark
Thanks; applied to for-next.
>
BR,
~me.
d do everything required so that
> the kmap calls can succeed (like swapin/backing storage allocation,
> flushing, ...).
>
> More in-depth explanations will follow in the follow-up documentation
> patch.
>
> Changes in v2:
>
> - Clear up begin_cpu_access confusion notice
On 19 March 2012 05:04, Daniel Vetter wrote:
> The mutex protects the attachment list and hence needs to be held
> around the callbakc to the exporters (optional) attach/detach
> functions.
>
> Holding the mutex around the map/unmap calls doesn't protect any
> dma_buf state. Exporters need to
On 19 March 2012 05:04, Daniel Vetter daniel.vet...@ffwll.ch wrote:
The mutex protects the attachment list and hence needs to be held
around the callbakc to the exporters (optional) attach/detach
functions.
Holding the mutex around the map/unmap calls doesn't protect any
dma_buf state.
do everything required so that
the kmap calls can succeed (like swapin/backing storage allocation,
flushing, ...).
More in-depth explanations will follow in the follow-up documentation
patch.
Changes in v2:
- Clear up begin_cpu_access confusion noticed by Sumit Semwal.
- Don't
On 19 March 2012 07:24, Rob Clark rob.cl...@linaro.org wrote:
On Sun, Mar 18, 2012 at 6:34 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
v2: Fix spelling issues noticed by Rob Clark.
Signed-off-by: Daniel Vetter daniel.vet...@ffwll.ch
Signed-off-by: Rob Clark r...@ti.com
Thanks; applied to
On 20 March 2012 03:12, Rob Clark rob.cl...@linaro.org wrote:
From: Rob Clark r...@ti.com
Otherwise subsystems will get this wrong and end up with a second
export ioctl with the flag and O_CLOEXEC support added.
Signed-off-by: Rob Clark r...@ti.com
Reviewed-by: Daniel Vetter
On 16 March 2012 20:21, Rob Clark wrote:
> On Fri, Mar 16, 2012 at 5:34 AM, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> We need to pass the flags into dma_buf_fd at this point,
>> so the flags end up doing the right thing for O_CLOEXEC.
>>
>> Signed-off-by: Dave Airlie
>
> Signed-off-by: Rob
On 16 March 2012 23:23, Dave Airlie wrote:
> On Fri, Mar 16, 2012 at 4:04 PM, Rob Clark wrote:
>> From: Rob Clark
>>
>> Works in a similar way to get_file(), and is needed in cases such as
>> when the exporter needs to also keep a reference to the dmabuf (that
>> is later released with a
On 16 March 2012 23:23, Dave Airlie airl...@gmail.com wrote:
On Fri, Mar 16, 2012 at 4:04 PM, Rob Clark rob.cl...@linaro.org wrote:
From: Rob Clark r...@ti.com
Works in a similar way to get_file(), and is needed in cases such as
when the exporter needs to also keep a reference to the dmabuf
On 16 March 2012 20:21, Rob Clark rob.cl...@linaro.org wrote:
On Fri, Mar 16, 2012 at 5:34 AM, Dave Airlie airl...@gmail.com wrote:
From: Dave Airlie airl...@redhat.com
We need to pass the flags into dma_buf_fd at this point,
so the flags end up doing the right thing for O_CLOEXEC.
Hi Stephen,
May I request you to please add the dma-buf buffer sharing framework
tree to linux-next?
It is hosted here
git://git.linaro.org/people/sumitsemwal/linux-dma-buf.git
branch: for-next
--
Thanks and nest regards,
Sumit Semwal.
Hi all,
Since the inclusion of dma-buf buffer sharing framework in 3.3 (thanks
to Dave Airlie primarily), I have been volunteered to be its
maintainer.
Obviously there is a need for some simple rules about the dma-buf
feature tree, so here we are:
- there will be a 'for-next' branch for (N+1),
Hi all,
Since the inclusion of dma-buf buffer sharing framework in 3.3 (thanks
to Dave Airlie primarily), I have been volunteered to be its
maintainer.
Obviously there is a need for some simple rules about the dma-buf
feature tree, so here we are:
- there will be a 'for-next' branch for (N+1),
Some exporters may use DMA map/unmap APIs in dma-buf ops, which require
enum dma_data_direction for both map and unmap operations.
Thus, the unmap dma_buf_op also needs to have enum dma_data_direction as
a parameter.
Reported-by: Tomasz Stanislawski
Signed-off-by: Sumit Semwal
---
drivers
Some exporters may use DMA map/unmap APIs in dma-buf ops, which require
enum dma_data_direction while unmapping.
Thus, the unmap dma_buf_op also needs to have enum dma_data_direction as
a parameter.
Reported-by: Tomasz Stanislawski
Signed-off-by: Sumit Semwal
---
drivers/base/Kconfig
Some exporters may use DMA map/unmap APIs in dma-buf ops, which require
enum dma_data_direction while unmapping.
Thus, the unmap dma_buf_op also needs to have enum dma_data_direction as
a parameter.
Reported-by: Tomasz Stanislawski t.stanisl...@samsung.com
Signed-off-by: Sumit Semwal sumit.sem
Some exporters may use DMA map/unmap APIs in dma-buf ops, which require
enum dma_data_direction for both map and unmap operations.
Thus, the unmap dma_buf_op also needs to have enum dma_data_direction as
a parameter.
Reported-by: Tomasz Stanislawski t.stanisl...@samsung.com
Signed-off-by: Sumit
On Jan 20, 2012 4:33 PM, Dave Airlie airl...@gmail.com wrote:
On Thu, Jan 19, 2012 at 10:39 AM, Daniel Vetter dan...@ffwll.ch wrote:
On Thu, Jan 19, 2012 at 03:04:25PM +0530, Sumit Semwal wrote:
Adding maintainer info for dma-buf buffer sharing framework;
some mailing lists interested
On Jan 20, 2012 4:33 PM, "Dave Airlie" wrote:
>
> On Thu, Jan 19, 2012 at 10:39 AM, Daniel Vetter wrote:
> > On Thu, Jan 19, 2012 at 03:04:25PM +0530, Sumit Semwal wrote:
> >> Adding maintainer info for dma-buf buffer sharing framework;
> >> some mailin
Adding maintainer info for dma-buf buffer sharing framework;
some mailing lists interested in this work are also added.
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
Acked-by: Arnd Bergmann
---
MAINTAINERS | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff
On 18 January 2012 17:16, Daniel Vetter wrote:
> On Wed, Jan 18, 2012 at 03:46:59PM +0530, Sumit Semwal wrote:
>> Adding maintainer info for dma-buf DMA buffer sharing framework.
>>
>> Signed-off-by: Sumit Semwal
>> ---
>> ?MAINTAINERS | ? ?8
>&g
Adding maintainer info for dma-buf DMA buffer sharing framework.
Signed-off-by: Sumit Semwal
---
MAINTAINERS |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index fa3f5e6..620119e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2246,6
Adding maintainer info for dma-buf DMA buffer sharing framework.
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
MAINTAINERS |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index fa3f5e6..620119e 100644
--- a/MAINTAINERS
+++ b
On 18 January 2012 17:16, Daniel Vetter dan...@ffwll.ch wrote:
On Wed, Jan 18, 2012 at 03:46:59PM +0530, Sumit Semwal wrote:
Adding maintainer info for dma-buf DMA buffer sharing framework.
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
MAINTAINERS | 8
1 files changed, 8
Hi Dave,
On 13 January 2012 14:38, Dave Airlie airl...@gmail.com wrote:
On Mon, Jan 9, 2012 at 6:44 AM, Sumit Semwal sumit.sem...@linaro.org wrote:
On 9 January 2012 03:38, Linus Torvalds torva...@linux-foundation.org
wrote:
snip
However, I ask myself whether it's ever sane to ask the user
As per Linus' comment, dma-buf Kconfig entry shouldn't have an option
text, but should be selected by the subsystems that use it.
Add this information in the documentation as well.
Signed-off-by: Sumit Semwal
---
Documentation/dma-buf-sharing.txt |4
1 files changed, 4 insertions
Hi Dave,
On 13 January 2012 14:38, Dave Airlie wrote:
> On Mon, Jan 9, 2012 at 6:44 AM, Sumit Semwal
> wrote:
>> On 9 January 2012 03:38, Linus Torvalds
>> wrote:
>>> However, I ask myself whether it's ever sane to ask the user to enable
>>> this? Isn'
As per Linus' comment, dma-buf Kconfig entry shouldn't have an option
text, but should be selected by the subsystems that use it.
Add this information in the documentation as well.
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
Documentation/dma-buf-sharing.txt |4
1 files changed
On 9 January 2012 03:38, Linus Torvalds
wrote:
> On Fri, Jan 6, 2012 at 7:06 AM, Dave Airlie wrote:
>>
>> Now we've all agreed that the initial implementation is a good baseline
>> for us to move forward on, but its messy working with others when the core
>> code is out of tree. So we'd like to
On 9 January 2012 03:38, Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jan 6, 2012 at 7:06 AM, Dave Airlie airl...@linux.ie wrote:
Now we've all agreed that the initial implementation is a good baseline
for us to move forward on, but its messy working with others when the core
Mark dma-buf buffer sharing API as EXPERIMENTAL for first release.
We will remove this in later versions, once it gets smoothed out
and has more users.
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
---
drivers/base/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
Reviewed-by: Daniel Vetter
---
Documentation/dma-buf-sharing.txt | 224
between two v4l2 devices. [2]
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
Reviewed-by: Daniel Vetter
Reviewed-by: Dave Airlie
Reviewed-and-Tested-by: Rob Clark
---
drivers/base/Kconfig
and a very happy, joyous and prosperous new year
2012 :)
Best regards,
~Sumit Semwal
History:
v4:
- Review comments incorporated:
- from Konrad Rzeszutek Wilk [https://lkml.org/lkml/2011/12/20/209]
- corrected language in some comments
- re-ordered struct definitions for readability
/lkml/2011/10/11/92
Wish you all happy vacations and a very happy, joyous and prosperous new year
2012 :)
Best regards,
~Sumit Semwal
History:
v4:
- Review comments incorporated:
- from Konrad Rzeszutek Wilk [https://lkml.org/lkml/2011/12/20/209]
- corrected language in some comments
t.stanisl...@samsung.com, who demonstrated buffer sharing
between two v4l2 devices. [2]
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
Reviewed
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
Reviewed-by: Daniel Vetter daniel.vet...@ffwll.ch
Mark dma-buf buffer sharing API as EXPERIMENTAL for first release.
We will remove this in later versions, once it gets smoothed out
and has more users.
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
drivers/base/Kconfig |1 +
1 files
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
---
Documentation/dma-buf-sharing.txt | 222 +
1 files
://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
---
drivers/base/Kconfig| 10 ++
drivers/base/Makefile |1 +
drivers/base/dma-buf.c | 289 +++
include/linux
Patchset based on top of 3.2-rc3, the current version can be found at
http://git.linaro.org/gitweb?p=people/sumitsemwal/linux-3.x.git
Branch: dma-buf-upstr-v3
Earlier versions:
v2 at: https://lkml.org/lkml/2011/12/2/53
v1 at: https://lkml.org/lkml/2011/10/11/92
Best regards,
~Sumit Semwal
History:
v3
at
http://git.linaro.org/gitweb?p=people/sumitsemwal/linux-3.x.git
Branch: dma-buf-upstr-v2
Earlier versions:
v2 at: https://lkml.org/lkml/2011/12/2/53
v1 at: https://lkml.org/lkml/2011/10/11/92
Best regards,
~Sumit Semwal
History:
v3:
- Review comments incorporated:
- from Konrad Rzeszutek
based on top of 3.2-rc3, the current version can be found at
http://git.linaro.org/gitweb?p=people/sumitsemwal/linux-3.x.git
Branch: dma-buf-upstr-v2
Earlier versions:
v2 at: https://lkml.org/lkml/2011/12/2/53
v1 at: https://lkml.org/lkml/2011/10/11/92
Best regards,
~Sumit Semwal
History:
v3
/lkml/2011/10/11/92
Best regards,
~Sumit Semwal
History:
v3:
- Review comments incorporated:
- from Konrad Rzeszutek Wilk [https://lkml.org/lkml/2011/12/3/45]
- replaced BUG_ON with WARN_ON - various places
- added some error-checks
- replaced EXPORT_SYMBOL with EXPORT_SYMBOL_GPL
sharing
between two v4l2 devices. [2]
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
drivers/base/Kconfig| 10 ++
drivers/base/Makefile
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
Documentation/dma-buf-sharing.txt | 222
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
---
Documentation/dma-buf-sharing.txt | 223 +
1 files
.
The implementation is inspired from proof-of-concept patch-set from
Tomasz Stanislawski , who demonstrated buffer
sharing
between two v4l2 devices. [2]
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit
at
http://git.linaro.org/gitweb?p=people/sumitsemwal/linux-3.x.git
Branch: dma-buf-upstr-v2
Earlier version at: https://lkml.org/lkml/2011/10/11/92
Best regards,
~Sumit Semwal
History:
v2:
- Review comments incorporated:
- from Tomasz Stanislawski [https://lkml.org/lkml/2011/10/14/136
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
Documentation/dma-buf-sharing.txt | 223
/454389
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
drivers/base/Kconfig| 10 ++
drivers/base/Makefile |1 +
drivers/base/dma-buf.c | 290 +++
include/linux/dma-buf.h | 176
based on top of 3.2-rc3, the current version can be found at
http://git.linaro.org/gitweb?p=people/sumitsemwal/linux-3.x.git
Branch: dma-buf-upstr-v2
Earlier version at: https://lkml.org/lkml/2011/10/11/92
Best regards,
~Sumit Semwal
History:
v2:
- Review comments incorporated:
- from Tomasz
On 14 October 2011 15:30, Tomasz Stanislawski
wrote:
> Hi Mr. Sumit Semwal,
Hello Mr. Tomasz Stanislawski :),
> Thank you for taking care of the framework for buffer sharing.
> The support of buffer sharing in V4L2, both exporting and importing was
> posted in shrbuf proof-of-c
On 14 October 2011 15:30, Tomasz Stanislawski t.stanisl...@samsung.com wrote:
Hi Mr. Sumit Semwal,
Hello Mr. Tomasz Stanislawski :),
Thank you for taking care of the framework for buffer sharing.
The support of buffer sharing in V4L2, both exporting and importing was
posted in shrbuf proof
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
---
Documentation/dma-buf-sharing.txt | 210 +
1 files
Signed-off-by: Sumit Semwal
Signed-off-by: Sumit Semwal
---
drivers/base/Kconfig| 10 ++
drivers/base/Makefile |1 +
drivers/base/dma-buf.c | 242 +++
include/linux/dma-buf.h | 162 +++
4 files changed, 415
buffer
sharing
between two v4l2 devices. [2]
References:
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Sumit Semwal (2):
dma-buf: Introduce dma buffer sharing mechanism
dma-buf: Documentation for buffer sharing framework
Documentation/dma-buf
/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
drivers/base/Kconfig| 10 ++
drivers/base/Makefile |1 +
drivers/base/dma-buf.c | 242
Add documentation for dma buffer sharing framework, explaining the
various operations, members and API of the dma buffer sharing
framework.
Signed-off-by: Sumit Semwal sumit.sem...@linaro.org
Signed-off-by: Sumit Semwal sumit.sem...@ti.com
---
Documentation/dma-buf-sharing.txt | 210
Tomasz Stanislawski t.stanisl...@samsung.com, who demonstrated buffer sharing
between two v4l2 devices. [2]
References:
[1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
[2]: http://lwn.net/Articles/454389
Sumit Semwal (2):
dma-buf: Introduce dma buffer sharing mechanism
dma-buf
301 - 395 of 395 matches
Mail list logo
