From: Hans Verkuil hans.verk...@cisco.com
Document that drivers can access/modify the buffer contents in buf_prepare
and buf_finish. That was not clearly stated before.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
include/media/videobuf2-core.h | 32 +---
1
Changes since v4:
- Rebased to latest media_tree master
Changes since v3:
- Dropped patch 02/10: succeeded by patch 10/15 in this series
- Added patches 11-15 to correctly handle syncing/mapping dmabuf
buffers for CPU access. This was never done correctly before.
Many thanks to Pawel Osciak
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/v4l2-core/videobuf2-dvb.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/media/v4l2-core/videobuf2-dvb.c
b/drivers/media/v4l2-core/videobuf2-dvb.c
From: Hans Verkuil hansv...@cisco.com
Add support for DMABUF exporting to the vb2-vmalloc implementation.
All memory models now have support for both importing and exporting of DMABUFs.
Signed-off-by: Hans Verkuil hansv...@cisco.com
---
drivers/media/v4l2-core/videobuf2-vmalloc.c | 174
From: Hans Verkuil hans.verk...@cisco.com
Require that dma-sg also uses an allocation context. This is in preparation
for adding prepare/finish memops to sync the memory between DMA and CPU.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/pci/cx23885/cx23885-417.c |
From: Hans Verkuil hans.verk...@cisco.com
The 'write' argument is very ambiguous. I first assumed that if it is 1,
then we're doing video output but instead it meant the reverse.
Since it is used to setup the dma_dir value anyway it is now replaced by
the correct dma_dir value which is
From: Hans Verkuil hans.verk...@cisco.com
Add support for dmabuf to vb2-dma-sg.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/v4l2-core/videobuf2-dma-sg.c | 126 +++--
1 file changed, 119 insertions(+), 7 deletions(-)
diff --git
From: Hans Verkuil hans.verk...@cisco.com
Now that vb2 supports DMABUF export for dma-sg and vmalloc memory
modes, we can enable the vb2_expbuf support in vivid.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/platform/vivid/vivid-core.c | 2 +-
1 file changed, 1
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/platform/vim2m.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c
index 87af47a..1105c11 100644
---
From: Hans Verkuil hansv...@cisco.com
Add DMABUF export support to vb2-dma-sg.
Signed-off-by: Hans Verkuil hansv...@cisco.com
---
drivers/media/v4l2-core/videobuf2-dma-sg.c | 170 +
1 file changed, 170 insertions(+)
diff --git
From: Hans Verkuil hans.verk...@cisco.com
The existing vb2_plane_vaddr function is not enough when dealing with
dmabuf. For dmabuf you need to be explicit when the cpu needs access to
the buffer and when that can be stopped.
So add vb2_plane_begin/end_cpu_access as a vaddr replacement. The old
From: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/dvb-frontends/rtl2832_sdr.c | 16 ++--
drivers/media/parport/bw-qcam.c| 5 ++-
drivers/media/pci/solo6x10/solo6x10-v4l2.c | 6 ++-
From: Hans Verkuil hans.verk...@cisco.com
This moves dma_(un)map_sg to the get_userptr/put_userptr and alloc/put
memops of videobuf2-dma-sg.c and adds dma_sync_sg_for_device/cpu to the
prepare/finish memops.
Now that vb2-dma-sg will sync the buffers for you in the prepare/finish
memops we can
From: Hans Verkuil hans.verk...@cisco.com
By default dma_map_sg syncs the mapped buffer to the device. But
buf_prepare expects a buffer syncs for the cpu and the buffer
will be synced to the device in the prepare memop.
The reverse is true for dma_unmap_sg, buf_finish and the finish
memop.
To
From: Hans Verkuil hans.verk...@cisco.com
Now that all drivers have been converted, this function can be dropped.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/v4l2-core/videobuf2-core.c | 8 +---
drivers/media/v4l2-core/videobuf2-dma-contig.c | 11 ---
From: Hans Verkuil hans.verk...@cisco.com
Document how the new vb2_plane_begin/end_cpu_access() functions should
be used in buf_prepare/finish.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
include/media/videobuf2-core.h | 35 ++-
1 file changed, 22
On 11/07/2014 09:50 AM, Hans Verkuil wrote:
Changes since v4:
- Rebased to latest media_tree master
Changes since v3:
- Dropped patch 02/10: succeeded by patch 10/15 in this series
- Added patches 11-15 to correctly handle syncing/mapping dmabuf
buffers for CPU access. This was never
On 2014-11-05 13:27, Mauro Carvalho Chehab wrote:
As reported by smatch:
drivers/media/rc/rc-main.c:1426 rc_register_device() warn: should '1
rc_map-rc_type' be a 64 bit type?
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/drivers/media/rc/rc-main.c
Hi Boris,
Thank you for the update.
On Thu, Nov 06, 2014 at 10:56:59AM +0100, Boris Brezillon wrote:
Rename mediabus formats and move the enum into a separate header file so
that it can be used by DRM/KMS subsystem without any reference to the V4L2
subsystem.
Old v4l2_mbus_pixelcode now
Em Fri, 07 Nov 2014 13:43:59 +0200
Sakari Ailus sakari.ai...@iki.fi escreveu:
+enum media_bus_format {
There's no really a need to keep the definitions inside the enum. It looks a
little bit confusing to me. That made me realise something I missed
yesterday.
There's a difference: the
Hi,
Thanks for the patch!
On Thu, Nov 6, 2014 at 1:04 PM, Sudip Mukherjee
sudipm.mukher...@gmail.com wrote:
we are getting struct clk using clk_get before calling
clk_prepare_enable. but if clk_prepare_enable fails, then we are
jumping to fail_mutex_unlock where we are just unlocking the
On Fri, 7 Nov 2014 13:43:59 +0200
Sakari Ailus sakari.ai...@iki.fi wrote:
Hi Boris,
Thank you for the update.
On Thu, Nov 06, 2014 at 10:56:59AM +0100, Boris Brezillon wrote:
Rename mediabus formats and move the enum into a separate header file so
that it can be used by DRM/KMS
From: Hans Verkuil hans.verk...@cisco.com
Make this pass the v4l2-compliance test.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/i2c/adv7842.c | 34 --
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git
From: Hans Verkuil hans.verk...@cisco.com
This fixes the v4l2-compliance failures.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
drivers/media/i2c/adv7511.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/drivers/media/i2c/adv7511.c
This patch series fixes the adv7604, adv7842 and adv7511 G/S_EDID behavior.
All three have been tested with v4l2-compliance and pass.
Jean-Michel, I based the adv7604 patch on your patch, but I reworked it a bit.
I hope you don't mind.
Regards,
Hans
--
To unsubscribe from this list:
From: Hans Verkuil hans.verk...@cisco.com
In order to have v4l2-compliance tool pass the G/S_EDID some modifications
where needed in the driver.
In particular, the edid.reserved zone must be blanked.
Based on a patch from Jean-Michel Hautbois jean-michel.hautb...@vodalys.com,
but reworked it a
On 10/21/14 17:06, Sebastian Reichel wrote:
Hi,
This is the RFCv2 patchset adding DT support to the si4713
radio transmitter i2c driver. The changes can be summarized
as follows:
* Move regulator information back into the driver. The
regulators needed are documented in the chip and
The following changes since commit 4895cc47a072dcb32d3300d0a46a251a8c6db5f1:
[media] s5p-mfc: fix sparse error (2014-11-05 08:29:27 -0200)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git for-v3.19e
for you to fetch changes up to
On 11/07/14 12:43, Sakari Ailus wrote:
Hi Boris,
Thank you for the update.
On Thu, Nov 06, 2014 at 10:56:59AM +0100, Boris Brezillon wrote:
Rename mediabus formats and move the enum into a separate header file so
that it can be used by DRM/KMS subsystem without any reference to the V4L2
2014-11-07 13:34 GMT+01:00 Hans Verkuil hverk...@xs4all.nl:
This patch series fixes the adv7604, adv7842 and adv7511 G/S_EDID behavior.
All three have been tested with v4l2-compliance and pass.
Jean-Michel, I based the adv7604 patch on your patch, but I reworked it a bit.
I hope you don't
Hello to everyone,
I'd like to know who have used the TVP5151 video decoder with the OMAP3
Overo module.
I'm trying to have the processor to capture the video from a TVP5151
boarda, but without success (both gstreamer and yavta wait forever the
data from the V4L2 subsystem).
Thanks in advance!
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed enum values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in all usb drivers.
Signed-off-by: Boris Brezillon
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in all media drivers residing in staging.
Signed-off-by: Boris
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in all platform drivers.
Signed-off-by: Boris Brezillon
Hello,
This patch series prepares the use of media bus formats outside of
the V4L2 subsytem (my final goal is to use it in the Atmel HLCDC DRM
driver where I have to configure my DPI/RGB bus according to the
connected display).
The series first defines MEDIA_BUS_FMT_ macros, and then replace all
Place v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel
users don't have access to these definitions.
We have to keep this definition for user-space users even though they're
encouraged to move to the new media_bus_format enum.
Signed-off-by: Boris Brezillon
Define MEDIA_BUS_FMT macros (re-using the values defined in the
v4l2_mbus_pixelcode enum) into a separate header file so that they can be
used from the DRM/KMS subsystem without any reference to the V4L2
subsystem.
Then set V4L2_MBUS_FMT definitions to the MEDIA_BUS_FMT values using the
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Replace all references to the old definitions in pci drivers.
Signed-off-by: Boris Brezillon
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed enum values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new definitions in the ipu-v3 driver.
Signed-off-by: Boris Brezillon
In order to have subsytem agnostic media bus format definitions we've
moved media bus definitions to include/uapi/linux/media-bus-format.h and
prefixed values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Replace all references to the old definitions in i2c drivers.
Signed-off-by: Boris Brezillon
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed them with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Update the v4l documentation accordingly.
Signed-off-by: Boris Brezillon
Replace references to the v4l2_mbus_pixelcode enum with the new
media_bus_format enum in all common headers.
Signed-off-by: Boris Brezillon boris.brezil...@free-electrons.com
Acked-by: Sakari Ailus sakari.ai...@linux.intel.com
---
include/media/v4l2-mediabus.h| 2 +-
Fix many sparse warnings:
drivers/media/pci/saa7164/saa7164-core.c:97:18: warning: cast removes address
space of expression
drivers/media/pci/saa7164/saa7164-core.c:122:31: warning: cast removes address
space of expression
drivers/media/pci/saa7164/saa7164-core.c:122:31: warning: incorrect type
Nitpicks:
On 11/07/14 15:07, Boris Brezillon wrote:
Place v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel
users don't have access to these definitions.
We have to keep this definition for user-space users even though they're
encouraged to move to the new media_bus_format
On 11/07/14 15:07, Boris Brezillon wrote:
Hello,
This patch series prepares the use of media bus formats outside of
the V4L2 subsytem (my final goal is to use it in the Atmel HLCDC DRM
driver where I have to configure my DPI/RGB bus according to the
connected display).
The series first
Am Freitag, den 07.11.2014, 15:07 +0100 schrieb Boris Brezillon:
In order to have subsytem agnostic media bus format definitions we've
moved media bus definition to include/uapi/linux/media-bus-format.h and
prefixed enum values with MEDIA_BUS_FMT instead of V4L2_MBUS_FMT.
Reference new
Hi Boris,
On Fri, Nov 07, 2014 at 03:07:40PM +0100, Boris Brezillon wrote:
Define MEDIA_BUS_FMT macros (re-using the values defined in the
v4l2_mbus_pixelcode enum) into a separate header file so that they can be
used from the DRM/KMS subsystem without any reference to the V4L2
subsystem.
On Fri, 07 Nov 2014 15:47:41 +0100
Hans Verkuil hverk...@xs4all.nl wrote:
Nitpicks:
On 11/07/14 15:07, Boris Brezillon wrote:
Place v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel
users don't have access to these definitions.
We have to keep this definition for
Hi Sakari,
On Fri, 7 Nov 2014 17:24:16 +0200
Sakari Ailus sakari.ai...@iki.fi wrote:
Hi Boris,
On Fri, Nov 07, 2014 at 03:07:40PM +0100, Boris Brezillon wrote:
Define MEDIA_BUS_FMT macros (re-using the values defined in the
v4l2_mbus_pixelcode enum) into a separate header file so that
Define MEDIA_BUS_FMT macros (re-using the values defined in the
v4l2_mbus_pixelcode enum) into a separate header file so that they can be
used from the DRM/KMS subsystem without any reference to the V4L2
subsystem.
Then set V4L2_MBUS_FMT definitions to the MEDIA_BUS_FMT values using the
Place v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel
users don't have access to these definitions.
We have to keep this definition for user-space users even though they're
encouraged to move to the new media_bus_format enum.
Signed-off-by: Boris Brezillon
From Wilson Michaels thebit...@earthlink.net
This patch fixes the KWorld UB435-Q V3 (ATSC) tuner functions:
1) The LED indicator now works.
2) Start up initialization is faster.
3) Add lgdt330x device name i2c_devs array used for debugging
4) Correct comments about the UB435-Q V3
Signed-off-by:
Hi Hans,
2014-11-07 13:34 GMT+01:00 Hans Verkuil hverk...@xs4all.nl:
From: Hans Verkuil hans.verk...@cisco.com
In order to have v4l2-compliance tool pass the G/S_EDID some modifications
where needed in the driver.
In particular, the edid.reserved zone must be blanked.
Based on a patch from
Hi Andrew,
On Fri, 7 Nov 2014, Andrew Chew wrote:
On Tue, 4 Nov 2014, Andrew Chew wrote:
Hello, Guennadi
I was wondering if you can provide some advice as to how focuser vcm
devices would fit into the soc-camera framework. We have a raw sensor
(an IMX219) with an AD5823 VCM
There's no such thing as list_struct.
Signed-off-by: Andrey Utkin andrey.krieger.ut...@gmail.com
---
drivers/gpu/drm/radeon/mkregtable.c | 24
drivers/media/pci/cx18/cx18-driver.h | 2 +-
include/linux/list.h | 34 +-
On Sat, Nov 08, 2014 at 01:18:48AM +0400, Andrey Utkin wrote:
There's no such thing as list_struct.
Signed-off-by: Andrey Utkin andrey.krieger.ut...@gmail.com
---
drivers/gpu/drm/radeon/mkregtable.c | 24
drivers/media/pci/cx18/cx18-driver.h | 2 +-
Hi Philipp,
Thanks for the patch and sorry for a late reply. I did look at your
patches earlier too, but maybe not attentively enough, or maybe I'm
misunderstanding something now. In the scan_of_host() function in
soc_camera.c as of current -next I see:
epn =
On Mon, Sep 22, 2014 at 8:21 AM, Jacek Anaszewski
j.anaszew...@samsung.com wrote:
This patch set is the follow-up of the LED / flash API integration
series [1]. For clarity reasons the patchset has been split into
four subsets:
- LED Flash Class
- V4L2 Flash
Hi Jacek,
For this series I
Hi Boris,
Boris Brezillon wrote:
@@ -102,6 +113,7 @@ enum v4l2_mbus_pixelcode {
V4L2_MBUS_FROM_MEDIA_BUS_FMT(AHSV_1X32),
};
+#endif /* __KERNEL__ */
/**
* struct v4l2_mbus_framefmt - frame format on the media bus
Was it intended to be this way, or did I miss something?
Hi Laurent,
On Thu, 2 Oct 2014, Laurent Pinchart wrote:
Hi Guennadi,
Ping ?
Uhm, yes, that's bad. 1 month and a week. Sorry. I'll try to test this on
Monday.
Thanks
Guennadi
On Wednesday 01 October 2014 00:42:51 Laurent Pinchart wrote:
Commit e93e7fd9f5a3fffec7792dbcc4c3574653effda7
On Sat, 08 Nov 2014 00:47:25 +0200
Sakari Ailus sakari.ai...@iki.fi wrote:
Hi Boris,
Boris Brezillon wrote:
@@ -102,6 +113,7 @@ enum v4l2_mbus_pixelcode {
V4L2_MBUS_FROM_MEDIA_BUS_FMT(AHSV_1X32),
};
+#endif /* __KERNEL__ */
/**
* struct v4l2_mbus_framefmt -
Hi Everyone,
I need suggestions with regard to adding controls to query camera read
only parameters (e.g maxZoom/maxExposureCompensation) as needed by
Android Camera API[1].
What is in my mind is to add a customized camera control ID for each
parameter I want to query and return EACCES when
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Sat Nov 8 04:00:18 CET 2014
git branch: test
git hash: 4895cc47a072dcb32d3300d0a46a251a8c6db5f1
gcc
63 matches
Mail list logo
