A mem-to-mem device is a device that uses memory buffers passed by
userspace applications for both source and destination data. This is
different from existing drivers, which use memory buffers for only one
of those at once.
In terms of V4L2 such a device would be both of OUTPUT and CAPTURE type.
This is a virtual device driver for testing the mem-to-mem V4L2 framework.
It simulates a device that uses memory buffers for both source and
destination, processes the data and issues an IRQ (simulated by a timer).
The device is capable of multi-instance, multi-buffer-per-transaction
operation
Add S3C/S5P rotator platform device.
Signed-off-by: Pawel Osciak p.osc...@samsung.com
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Reviewed-by: Marek Szyprowski m.szyprow...@samsung.com
Reviewed-by: Kyungmin Park kyungmin.p...@samsung.com
---
arch/arm/mach-s3c6400/include/mach/map.h
Hello,
this is the second version of the proposed implementation for mem-to-mem memory
device framework. Your comments are very welcome.
Changes since v1:
- v4l2_m2m_buf_queue() now requires m2m_ctx as its argument
- video_queue private data stores driver private data
- a new submenu in kconfig
This is an example application for testing mem-to-mem framework using
mem2mem-testdev device.
It is intended to be executed multiple times in parallel to test multi-instance
operation and scheduling. Each process can be configured differently using
command-line arguments.
The application opens
Hello,
this is a driver for Samsung S3C/S5P series image rotator device driver.
This driver utilizes the proposed memory-to-memory V4L2 framework, just posted
by me in the previous patch series.
An example application for testing the device is also included.
This series contains:
[PATCH 1/2]
The rotator device present on Samsung S3C and S5P series SoCs allows image
rotation and flipping. It requires contiguous memory buffers to operate,
as it does not have scatter-gather support. It is also an example of
a memory-to-memory device, and so uses the mem-2-mem device V4L2 framework.
Hello,
this is the second version of the proposed implementation for mem-to-mem memory
device framework. Your comments are very welcome.
In v2.1:
I am very sorry for the resend, but somehow an orphaned endif found its way to
Kconfig during the rebase.
Changes since v1:
- v4l2_m2m_buf_queue()
This is a virtual device driver for testing the mem-to-mem V4L2 framework.
It simulates a device that uses memory buffers for both source and
destination, processes the data and issues an IRQ (simulated by a timer).
The device is capable of multi-instance, multi-buffer-per-transaction
operation
A mem-to-mem device is a device that uses memory buffers passed by
userspace applications for both source and destination data. This is
different from existing drivers, which use memory buffers for only one
of those at once.
In terms of V4L2 such a device would be both of OUTPUT and CAPTURE type.
This is an example application for testing mem-to-mem framework using
mem2mem-testdev device.
It is intended to be executed multiple times in parallel to test multi-instance
operation and scheduling. Each process can be configured differently using
command-line arguments.
The application opens
On Wednesday 23 December 2009 14:17:32 Pawel Osciak wrote:
Hello,
this is the second version of the proposed implementation for mem-to-mem
memory
device framework. Your comments are very welcome.
Hi Pawel,
Thank you for working on this! It's much appreciated. Now I've noticed that
patches
Hello,
On Wed, Dec 23, 2009 at 1:08 PM, Pawel Osciak p.osc...@samsung.com wrote:
The rotator device present on Samsung S3C and S5P series SoCs allows image
rotation and flipping. It requires contiguous memory buffers to operate,
as it does not have scatter-gather support. It is also an example
Sorry for this rather belated pull request for the last of the
samsung updates, but some of these ended up requiring to be
based on stuff that got merged via other trees and whilst this
was happening I was ill and thus have only just had the chance
to put this together.
So, please pull these
On Wed, 2009-12-23 at 14:17 +0100, Pawel Osciak wrote:
A mem-to-mem device is a device that uses memory buffers passed by
userspace applications for both source and destination data. This is
different from existing drivers, which use memory buffers for only one
of those at once.
In terms of
15 matches
Mail list logo