cron job: media_tree daily build: ERRORS

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 May 26 05:00:17 CEST 2018 media-tree git hash:e646e17713eeb3b6484b6d7a24ce34854123fa39 media_build

Re: [PATCH 3/6] media: videodev2.h: Add macro V4L2_FIELD_IS_SEQUENTIAL

Le vendredi 25 mai 2018 à 21:14 -0400, Nicolas Dufresne a écrit : > Le vendredi 25 mai 2018 à 17:19 -0700, Steve Longerbeam a écrit : > > > > On 05/25/2018 05:10 PM, Nicolas Dufresne wrote: > > > (in text this time, sorry) > > > > > > Le vendredi 25 mai 2018 à 16:53 -0700, Steve Longerbeam a

Re: [PATCH 3/6] media: videodev2.h: Add macro V4L2_FIELD_IS_SEQUENTIAL

Le vendredi 25 mai 2018 à 17:19 -0700, Steve Longerbeam a écrit : > > On 05/25/2018 05:10 PM, Nicolas Dufresne wrote: > > (in text this time, sorry) > > > > Le vendredi 25 mai 2018 à 16:53 -0700, Steve Longerbeam a écrit : > > > Add a macro that returns true if the given field type is > > >

Re: [GIT PULL FOR v4.18] R-Car VSP1 TLB optimisation

Hi Mauro, On Saturday, 26 May 2018 02:39:16 EEST Laurent Pinchart wrote: > On Saturday, 26 May 2018 02:10:27 EEST Mauro Carvalho Chehab wrote: > > Em Sun, 20 May 2018 15:10:50 +0300 Laurent Pinchart escreveu: > >> Hi Mauro, > >> > >> The following changes since commit > >> > >>

Re: [PATCH 3/6] media: videodev2.h: Add macro V4L2_FIELD_IS_SEQUENTIAL

On 05/25/2018 05:10 PM, Nicolas Dufresne wrote: (in text this time, sorry) Le vendredi 25 mai 2018 à 16:53 -0700, Steve Longerbeam a écrit : Add a macro that returns true if the given field type is 'sequential', that is, the data is transmitted, or exists in memory, as all top field lines

Re: [PATCH 3/6] media: videodev2.h: Add macro V4L2_FIELD_IS_SEQUENTIAL

(in text this time, sorry) Le vendredi 25 mai 2018 à 16:53 -0700, Steve Longerbeam a écrit : > Add a macro that returns true if the given field type is > 'sequential', > that is, the data is transmitted, or exists in memory, as all top > field > lines followed by all bottom field lines, or

[PATCH 3/6] media: videodev2.h: Add macro V4L2_FIELD_IS_SEQUENTIAL

Add a macro that returns true if the given field type is 'sequential', that is, the data is transmitted, or exists in memory, as all top field lines followed by all bottom field lines, or vice-versa. Signed-off-by: Steve Longerbeam --- include/uapi/linux/videodev2.h

[PATCH 6/6] media: staging/imx: interweave and odd-chroma-row skip are incompatible

If IDMAC interweaving is enabled in a write channel, the channel must write the odd chroma rows for 4:2:0 formats. Skipping writing the odd chroma rows produces corrupted captured 4:2:0 images when interweave is enabled. Signed-off-by: Steve Longerbeam ---

[PATCH 5/6] media: imx-csi: Allow skipping odd chroma rows for YVU420

Skip writing U/V components to odd rows for YVU420 in addition to YUV420 and NV12. Signed-off-by: Steve Longerbeam --- drivers/staging/media/imx/imx-media-csi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/media/imx/imx-media-csi.c

[PATCH 2/6] gpu: ipu-csi: Check for field type alternate

When the CSI is receiving from a bt.656 bus, include a check for field type 'alternate' when determining whether to set CSI clock mode to CCIR656_INTERLACED or CCIR656_PROGRESSIVE. Signed-off-by: Steve Longerbeam --- drivers/gpu/ipu-v3/ipu-csi.c | 3 ++- 1 file

[PATCH 0/6] imx-media: Fixes for bt.656 interlaced capture

A set of patches that fixes some bugs with capturing from a bt.656 interlaced source, and incompatibilites between IDMAC interlace interweaving and 4:2:0 data write reduction. Steve Longerbeam (6): media: imx-csi: Fix interlaced bt.656 gpu: ipu-csi: Check for field type alternate media:

[PATCH 4/6] media: imx-csi: Enable interlaced scan for field type alternate

Interlaced scan, a.k.a. interweave, should be enabled at the CSI IDMAC output pad if the input field type is 'alternate' (in addition to field types 'seq-tb' and 'seq-bt'). Which brings up whether V4L2_FIELD_HAS_BOTH() macro should be used to determine enabling interlaced/interweave scan. That

[PATCH 1/6] media: imx-csi: Fix interlaced bt.656

The output pad's field type was being passed to ipu_csi_init_interface(), in order to deal with field type 'alternate' at the sink pad, which must be translated to either 'seq-tb' or 'seq-bt' to be understood by ipu_csi_init_interface(). Doing so breaks the CSI interface setup if the output pad

Re: i.MX6 IPU CSI analog video input on Ventana

Hi Krzysztof, Philipp, On 05/25/2018 12:18 AM, Krzysztof Hałasa wrote: Philipp Zabel writes: Maybe scanline interlave and double write reduction can't be used at the same time? Well, if it works in non-interlaced modes - it may be the case. Perhaps the data

Re: [GIT PULL FOR v4.18] R-Car VSP1 TLB optimisation

Hi Mauro, (CC'ing Kieran) On Saturday, 26 May 2018 02:10:27 EEST Mauro Carvalho Chehab wrote: > Em Sun, 20 May 2018 15:10:50 +0300 Laurent Pinchart escreveu: > > Hi Mauro, > > > > The following changes since commit > > 8ed8bba70b4355b1ba029b151ade84475dd12991: > > media: imx274: remove

Re: i.MX6 IPU CSI analog video input on Ventana

Hi Philipp, On 05/24/2018 11:32 PM, Philipp Zabel wrote: On Thu, 2018-05-24 at 11:12 -0700, Steve Longerbeam wrote: [...] The following is required as well. Now the question is why we can't skip writing those odd UV rows. Anyway, with these 2 changes, I get a stable NTSC (and probably PAL)

Re: [GIT PULL FOR v4.18] R-Car VSP1 TLB optimisation

Em Sun, 20 May 2018 15:10:50 +0300 Laurent Pinchart escreveu: > Hi Mauro, > > The following changes since commit 8ed8bba70b4355b1ba029b151ade84475dd12991: > > media: imx274: remove non-indexed pointers from mode_table (2018-05-17 > 06:22:08 -0400) > > are

[PATCH] media: tc358743: release device_node in tc358743_probe_of()

of_graph_get_next_endpoint() returns device_node with refcnt increased, but these is no of_node_put() for it. The patch adds one on error and normal paths. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov ---

Re: [PATCH v4 2/3] media: rc: introduce BPF_PROG_LIRC_MODE2

On Fri, May 18, 2018 at 03:07:29PM +0100, Sean Young wrote: > Add support for BPF_PROG_LIRC_MODE2. This type of BPF program can call > rc_keydown() to reported decoded IR scancodes, or rc_repeat() to report > that the last key should be repeated. > > The bpf program can be attached to using the

Re: [PATCH 3/3] media: rc: nuvoton: Keep device enabled during reg init

On Fri, May 25, 2018 at 04:42:02PM +0200, Michał Winiarski wrote: > On Fri, May 25, 2018 at 02:59:41PM +0100, Sean Young wrote: > > On Fri, May 25, 2018 at 03:35:23PM +0200, Michał Winiarski wrote: > > > On Thu, May 24, 2018 at 12:31:40PM +0100, Sean Young wrote: > > > > On Mon, May 21, 2018 at

Re: [PATCH v10 13/16] vb2: add out-fence support to QBUF

Hi Ezequiel, Not sure if this patch series is still relevant, but I spotted a couple more things below. On Mon, May 21, 2018 at 01:59:43PM -0300, Ezequiel Garcia wrote: From: Gustavo Padovan If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create

[GIT PULL FOR v4.18] RC fixes

Hi Mauro, Fixes for a regression in v4.16, and broken open/close handling in the nuvoton driver. Thanks Sean The following changes since commit 8ed8bba70b4355b1ba029b151ade84475dd12991: media: imx274: remove non-indexed pointers from mode_table (2018-05-17 06:22:08 -0400) are available in

[PATCH 0/8] xen: dma-buf support for grant device

From: Oleksandr Andrushchenko This work is in response to my previous attempt to introduce Xen/DRM zero-copy driver [1] to enable Linux dma-buf API [2] for Xen based frontends/backends. There is also an existing hyper_dmabuf approach available [3] which, if

[PATCH 3/8] xen/grant-table: Allow allocating buffers suitable for DMA

From: Oleksandr Andrushchenko Extend grant table module API to allow allocating buffers that can be used for DMA operations and mapping foreign grant references on top of those. The resulting buffer is similar to the one allocated by the balloon driver in terms

[PATCH 1/8] xen/grant-table: Make set/clear page private code shared

From: Oleksandr Andrushchenko Make set/clear page private code shared and accessible to other kernel modules which can re-use these instead of open-coding. Signed-off-by: Oleksandr Andrushchenko --- drivers/xen/grant-table.c

[PATCH 2/8] xen/balloon: Move common memory reservation routines to a module

From: Oleksandr Andrushchenko Memory {increase|decrease}_reservation and VA mappings update/reset code used in balloon driver can be made common, so other drivers can also re-use the same functionality without open-coding. Create a dedicated module for the

[PATCH 4/8] xen/gntdev: Allow mappings for DMA buffers

From: Oleksandr Andrushchenko Allow mappings for DMA backed buffers if grant table module supports such: this extends grant device to not only map buffers made of balloon pages, but also from buffers allocated with dma_alloc_xxx. Signed-off-by: Oleksandr

[PATCH 6/8] xen/gntdev: Implement dma-buf export functionality

From: Oleksandr Andrushchenko 1. Create a dma-buf from grant references provided by the foreign domain. By default dma-buf is backed by system memory pages, but by providing GNTDEV_DMA_FLAG_XXX flags it can also be created as a DMA

[PATCH 5/8] xen/gntdev: Add initial support for dma-buf UAPI

From: Oleksandr Andrushchenko Add UAPI and IOCTLs for dma-buf grant device driver extension: the extension allows userspace processes and kernel modules to use Xen backed dma-buf implementation. With this extension grant references to the pages of an imported

[PATCH 7/8] xen/gntdev: Implement dma-buf import functionality

From: Oleksandr Andrushchenko 1. Import a dma-buf with the file descriptor provided and export granted references to the pages of that dma-buf into the array of grant references. 2. Add API to close all references to an imported buffer, so it can be

[PATCH 8/8] xen/gntdev: Expose gntdev's dma-buf API for in-kernel use

From: Oleksandr Andrushchenko Allow creating grant device context for use by kernel modules which require functionality, provided by gntdev. Export symbols for dma-buf API provided by the module. Signed-off-by: Oleksandr Andrushchenko

[PATCH 5/5] media: omap2: fix compile-testing with FB_OMAP2=m

Compile-testing with FB_OMAP2=m results in a link error: drivers/media/platform/omap/omap_vout.o: In function `vidioc_streamoff': omap_vout.c:(.text+0x1028): undefined reference to `omap_dispc_unregister_isr' drivers/media/platform/omap/omap_vout.o: In function `omap_vout_release':

[PATCH 4/5] media: marvel-ccic: allow ccic and mmp drivers to coexist

Randconfig builds fail when one of the two is a built-in driver and the other one is a loadable module: drivers/media/platform/marvell-ccic/mcam-core.o: In function `mccic_register': mcam-core.c:(.text+0x2594): undefined reference to `__this_module'

Re: RFC: Request API and memory-to-memory devices

On 25/05/18 16:16, Sakari Ailus wrote: > Hi Hans, > > On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: >> Memory-to-memory devices have one video node, one internal control handler >> but two vb2_queues (DMA engines). While often there is one buffer produced >> for every buffer

[PATCH 3/5] media: cx231xx: fix RC_CORE dependency

With CONFIG_RC_CORE=m and VIDEO_CX231XX=y, we get a link failure: drivers/media/usb/cx231xx/cx231xx-input.o: In function `cx231xx_ir_init': cx231xx-input.c:(.text+0xd4): undefined reference to `rc_allocate_device' This narrows down the dependency so that only valid configurations are allowed.

[PATCH 2/5] media: v4l: cadence: include linux/slab.h

I ran into a randconfig build error with the new driver: drivers/media/platform/cadence/cdns-csi2tx.c: In function 'csi2tx_probe': drivers/media/platform/cadence/cdns-csi2tx.c:477:11: error: implicit declaration of function 'kzalloc'; did you mean 'd_alloc'?

[PATCH 1/5] media: omap3isp: fix warning for !CONFIG_PM

The final version of the COMPILE_TEST patch for this driver missed one warning about suspend/resume functions that can now appear on platforms that don't always set CONFIG_PM: drivers/media/platform/omap3isp/isp.c:1008:13: error: 'isp_resume_modules' defined but not used

Re: [PATCH 3/3] media: rc: nuvoton: Keep device enabled during reg init

On Fri, May 25, 2018 at 02:59:41PM +0100, Sean Young wrote: > On Fri, May 25, 2018 at 03:35:23PM +0200, Michał Winiarski wrote: > > On Thu, May 24, 2018 at 12:31:40PM +0100, Sean Young wrote: > > > On Mon, May 21, 2018 at 04:38:03PM +0200, Michał Winiarski wrote: > > > > Doing writes when the

Re: RFC: Request API and memory-to-memory devices

On Fri, May 25, 2018 at 11:17 PM Sakari Ailus wrote: > Hi Hans, > On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: > > Memory-to-memory devices have one video node, one internal control handler > > but two vb2_queues (DMA engines). While often there is

[PATCH] udmabuf: fix odd_ptr_err.cocci warnings

From: kbuild test robot drivers/dma-buf/udmabuf.c:167:6-12: inconsistent IS_ERR and PTR_ERR on line 168. PTR_ERR should access the value just tested by IS_ERR Semantic patch information: There can be false positives in the patch case, where it is the call to IS_ERR

[PATCH v2 3/3] media: rc: nuvoton: Keep device enabled during reg init

Doing writes when the device is disabled seems to be a NOOP. For CIR device, we should enable it, intialize it, and then disable it until it's opened. CIR_WAKE should always be enabled. Signed-off-by: Michał Winiarski Cc: Jarod Wilson Cc: Sean Young

Re: [PATCH v2.2 2/2] smiapp: Support the "rotation" property

On Fri, May 25, 2018 at 04:09:55PM +0200, Sebastian Reichel wrote: > Hi, > > On Fri, May 25, 2018 at 04:52:35PM +0300, Sakari Ailus wrote: > > Use the "rotation" property to tell that the sensor is mounted upside > > down. This reverses the behaviour of the VFLIP and HFLIP controls as well > > as

Re: RFC: Request API and memory-to-memory devices

Hi Hans, On Thu, May 24, 2018 at 10:44:13AM +0200, Hans Verkuil wrote: > Memory-to-memory devices have one video node, one internal control handler > but two vb2_queues (DMA engines). While often there is one buffer produced > for every buffer consumed, but this is by no means standard. E.g. >

Re: [PATCH v2.2 2/2] smiapp: Support the "rotation" property

Hi, On Fri, May 25, 2018 at 04:52:35PM +0300, Sakari Ailus wrote: > Use the "rotation" property to tell that the sensor is mounted upside > down. This reverses the behaviour of the VFLIP and HFLIP controls as well > as the pixel order. > > Signed-off-by: Sakari Ailus

[PATCH v3] Add udmabuf misc device

A driver to let userspace turn memfd regions into dma-bufs. Use case: Allows qemu create dmabufs for the vga framebuffer or virtio-gpu ressources. Then they can be passed around to display those guest things on the host. To spice client for classic full framebuffer display, and hopefully some

Re: [PATCH v2 1/2] dt-bindings: media: Define "rotation" property for sensors

Hi, On Fri, May 25, 2018 at 03:27:25PM +0300, Sakari Ailus wrote: > Sensors are occasionally mounted upside down to systems such as mobile > phones or tablets. In order to use such a sensor without having to turn > every image upside down, most camera sensors support reversing the readout > order

Re: [PATCH 3/3] media: rc: nuvoton: Keep device enabled during reg init

On Fri, May 25, 2018 at 03:35:23PM +0200, Michał Winiarski wrote: > On Thu, May 24, 2018 at 12:31:40PM +0100, Sean Young wrote: > > On Mon, May 21, 2018 at 04:38:03PM +0200, Michał Winiarski wrote: > > > Doing writes when the device is disabled seems to be a NOOP. > > > Let's enable the device,

[PATCH v2.2 2/2] smiapp: Support the "rotation" property

Use the "rotation" property to tell that the sensor is mounted upside down. This reverses the behaviour of the VFLIP and HFLIP controls as well as the pixel order. Signed-off-by: Sakari Ailus --- since v2.2: - Fix property name in code.

Re: [PATCH v2 2/2] smiapp: Support the "upside-down" property

On Fri, May 25, 2018 at 03:41:59PM +0200, Sebastian Reichel wrote: > Hi, > > On Fri, May 25, 2018 at 03:27:26PM +0300, Sakari Ailus wrote: > > Use the "upside-down" property to tell that the sensor is mounted upside > > down. This reverses the behaviour of the VFLIP and HFLIP controls as well > >

Re: [PATCH v2 2/2] smiapp: Support the "upside-down" property

Hi, On Fri, May 25, 2018 at 03:27:26PM +0300, Sakari Ailus wrote: > Use the "upside-down" property to tell that the sensor is mounted upside > down. This reverses the behaviour of the VFLIP and HFLIP controls as well > as the pixel order. > > Signed-off-by: Sakari Ailus

[PATCH v2.1 2/2] smiapp: Support the "rotation" property

Use the "rotation" property to tell that the sensor is mounted upside down. This reverses the behaviour of the VFLIP and HFLIP controls as well as the pixel order. Signed-off-by: Sakari Ailus --- since v2: - Fix the property name in the commit message

Re: [PATCH 3/3] media: rc: nuvoton: Keep device enabled during reg init

On Thu, May 24, 2018 at 12:31:40PM +0100, Sean Young wrote: > On Mon, May 21, 2018 at 04:38:03PM +0200, Michał Winiarski wrote: > > Doing writes when the device is disabled seems to be a NOOP. > > Let's enable the device, write the values, and then disable it on init. > > This changes the behavior

Re: [PATCH v2] media: davinci vpbe: array underflow in vpbe_enum_outputs()

On Fri, May 25, 2018 at 03:16:21PM +0200, Hans Verkuil wrote: > On 25/05/18 15:12, Dan Carpenter wrote: > > In vpbe_enum_outputs() we check if (temp_index >= cfg->num_outputs) but > > the problem is that temp_index can be negative. I've made > > cgf->num_outputs unsigned to fix this issue. > >

Re: [PATCH v2] media: davinci vpbe: array underflow in vpbe_enum_outputs()

On 25/05/18 15:12, Dan Carpenter wrote: > In vpbe_enum_outputs() we check if (temp_index >= cfg->num_outputs) but > the problem is that temp_index can be negative. I've made > cgf->num_outputs unsigned to fix this issue. Shouldn't temp_index also be made unsigned? It certainly would make a lot

[PATCH v2] media: davinci vpbe: array underflow in vpbe_enum_outputs()

In vpbe_enum_outputs() we check if (temp_index >= cfg->num_outputs) but the problem is that temp_index can be negative. I've made cgf->num_outputs unsigned to fix this issue. Fixes: 66715cdc3224 ("[media] davinci vpbe: VPBE display driver") Signed-off-by: Dan Carpenter

[PATCH v2 2/2] smiapp: Support the "upside-down" property

Use the "upside-down" property to tell that the sensor is mounted upside down. This reverses the behaviour of the VFLIP and HFLIP controls as well as the pixel order. Signed-off-by: Sakari Ailus --- .../devicetree/bindings/media/i2c/nokia,smia.txt | 2 ++

[PATCH v2 1/2] dt-bindings: media: Define "rotation" property for sensors

Sensors are occasionally mounted upside down to systems such as mobile phones or tablets. In order to use such a sensor without having to turn every image upside down, most camera sensors support reversing the readout order by setting both horizontal and vertical flipping. This patch documents

[PATCH v2 0/2] Define rotation property for camera sensors

Hi, Here's an update on my previous patchset adding an "upside-down" property. Instead of dropping the first patch entirely as I first thought, I decided to add documentation for the rotation property for sensors as well. The updates to the patches are related to that. Sakari Ailus (2):

Re: qcom: add firmware file for Venus on SDM845

On Fri, May 25, 2018 at 7:03 AM Vikash Garodia wrote: > This pull request adds firmware files for Venus h/w codec found on the Qualcomm SDM845 chipset. > The following changes since commit 2a9b2cf50fb32e36e4fc1586c2f6f1421913b553: >Merge branch

Re: [PATCH v4 5/9] media: rcar-vin: Parse parallel input on Gen3

Hi Niklas, I might have another question before sending v5. On Fri, May 25, 2018 at 12:29:44AM +0200, Niklas Söderlund wrote: > Hi Jacopo, > > Thanks for your work. > > I really like what you did with this patch in v4. > > On 2018-05-25 00:02:15 +0200, Jacopo Mondi wrote: > > The rcar-vin

qcom: add firmware file for Venus on SDM845

This pull request adds firmware files for Venus h/w codec found on the Qualcomm SDM845 chipset. The following changes since commit 2a9b2cf50fb32e36e4fc1586c2f6f1421913b553: Merge branch 'for-upstreaming-v1.7.2' of https://github.com/felix-cavium/linux-firmware (2018-05-18 08:35:22 -0400)

qcom: add firmware file for Venus on SDM845

hi, This pull request adds firmware files for Venus h/w codec found on the Qualcomm SDM845 chipset. The following changes since commit 2a9b2cf50fb32e36e4fc1586c2f6f1421913b553: Merge branch 'for-upstreaming-v1.7.2' of https://github.com/felix-cavium/linux-firmware (2018-05-18 08:35:22

Re: [PATCH v2 11/13] dmaengine: pxa: make the filter function internal

On 24-05-18, 09:07, Robert Jarzmik wrote: > As the pxa architecture and all its related drivers do not rely anymore > on the filter function, thanks to the slave map conversion, make > pxad_filter_fn() static, and remove it from the global namespace. Acked-by: Vinod Koul --

Re: [PATCH v2 10/13] dmaengine: pxa: document pxad_param

On 24-05-18, 09:07, Robert Jarzmik wrote: > Add some documentation for the pxad_param structure, and describe the > contract behind the minimal required priority of a DMA channel. Acked-by: Vinod Koul -- ~Vinod

Re: [PATCH v3] media: imx319: Add imx319 camera sensor driver

Hi Tomasz, On Fri, May 25, 2018 at 04:31:07PM +0900, Tomasz Figa wrote: > On Fri, May 25, 2018 at 4:12 PM jacopo mondi wrote: > > > Hi Tomasz, > [snip] > > > the controls set before powering on will actually be programmed into the > > > hardware registers. > > > Thanks, I

[GIT PULL FOR v4.18] Various fixes

Hi Mauro, This is the usual collection of random fixes/improvements. A note on one patch "v4l2-core: push taking ioctl mutex down to ioctl handler.": I would like to get this in for 4.18 since it will help the fence and request API implementation. But it is also OK if you decide to push this

[RESEND PATCH V2 2/2] media: ak7375: Add ak7375 lens voice coil driver

From: Bingbu Cao Add a V4L2 sub-device driver for the ak7375 lens voice coil. This is a voice coil module using the I2C bus to control the focus position. Signed-off-by: Tianshu Qiu Signed-off-by: Bingbu Cao --- MAINTAINERS

[RESEND PATCH V2 1/2] dt-bindings: Add bindings for AKM ak7375 voice coil lens

From: Bingbu Cao Add device tree bindings for AKM ak7375 voice coil lens driver. This chip is used to drive a lens in a camera module. Signed-off-by: Tianshu Qiu Signed-off-by: Bingbu Cao --- Changes since v1: - remove the

[PATCH v2 1/2] dt-bindings: Add bindings for AKM ak7375 voice coil lens

From: Bingbu Cao Add device tree bindings for AKM ak7375 voice coil lens driver. This chip is used to drive a lens in a camera module. Signed-off-by: Tianshu Qiu Signed-off-by: Bingbu Cao --- Changes since v1: - remove the

[PATCH v2 2/2] media: ak7375: Add ak7375 lens voice coil driver

From: Bingbu Cao Add a V4L2 sub-device driver for the ak7375 lens voice coil. This is a voice coil module using the I2C bus to control the focus position. Signed-off-by: Tianshu Qiu Signed-off-by: Bingbu Cao --- MAINTAINERS

[PATCH 3/3 v2] gspca_zc3xx: Enable short exposure times for OV7648

The 50Hz and 60Hz power line frequency settings disable short (1/120s and 1/100s) exposure times for banding filter (causing overexposed image near lamps). No flicker setting enables them (when banding filter is disabled and they're not used). Seems that the logic is just the wrong way around.

[PATCH 2/3 v2] gspca_zc3xx: Fix power line frequency settings for OV7648

Power line frequency settings for OV7648 sensor contain autogain and exposure commands, affecting unrelated controls. Remove them. Signed-off-by: Ondrej Zary --- drivers/media/usb/gspca/zc3xx.c | 7 --- 1 file changed, 7 deletions(-) diff --git

[PATCH 1/3] gspca_zc3xx: Implement proper autogain and exposure control for OV7648

The ZS0211 internal autogain causes pumping and flickering with OV7648 sensor on 0ac8:307b webcam. Implement OV7648 autogain and exposure control and use that instead. Signed-off-by: Ondrej Zary --- drivers/media/usb/gspca/zc3xx.c | 42

Re: [PATCH] media: v4l2-ctrl: Add control for VP9 profile

On 17/05/18 11:53, Keiichi Watanabe wrote: > Add a new control V4L2_CID_MPEG_VIDEO_VP9_PROFILE for selecting desired > profile for VP9 encoder and querying for supported profiles by VP9 encoder > or decoder. > > An existing control V4L2_CID_MPEG_VIDEO_VPX_PROFILE cannot be > used for querying

Re: [PATCH] media: v4l2-ioctl: prevent underflow in v4l_enumoutput()

On 17/05/18 11:05, Dan Carpenter wrote: > My Smatch allmodconfig build only detects one function implementing > vpbe_device_ops->enum_outputs and that's vpbe_enum_outputs(). The > problem really happens in that function when we do: > > int temp_index = output->index; > > if

Re: [PATCH v2 08/13] ASoC: pxa: remove the dmaengine compat need

On Thursday, May 24, 2018 09:06 AM, Robert Jarzmik wrote: As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the

[GIT PULL FOR v4.18] gspca: convert to vb2

This patch series converts gspca to vb2. It also fixes a vb2 bug found while testing this, and it zeroes some fields for g/s_parm (they were never tested in v4l2-compliance, so nobody noticed before). Finally v4l2_disable_ioctl_locking() can now be removed since gspca no longer needs it. Tested

Re: [PATCH 2/3] gspca_zc3xx: Fix power line frequency settings for OV7648

On 24/05/18 17:09, Ondrej Zary wrote: > Power line frequency settings for OV7648 sensor contain autogain > and exposure commands, affecting unrelated controls. Remove them. > > Signed-off-by: Ondrej Zary > --- > drivers/media/usb/gspca/zc3xx.c | 17 ++---

Re: [PATCH v2 13/13] ARM: pxa: change SSP DMA channels allocation

On Thursday, May 24, 2018 09:07 AM, Robert Jarzmik wrote: Now the dma_slave_map is available for PXA architecture, switch the SSP device to it. This specifically means that : - for platform data based machines, the DMA requestor channels are extracted from the slave map, where pxa-ssp-dai.

Re: [PATCH v3] media: imx319: Add imx319 camera sensor driver

On Fri, May 25, 2018 at 4:12 PM jacopo mondi wrote: > Hi Tomasz, > On Fri, May 25, 2018 at 03:18:38PM +0900, Tomasz Figa wrote: > > On Fri, May 25, 2018 at 5:47 AM Sakari Ailus < sakari.ai...@linux.intel.com> > > wrote: > > > > > Hi Jacopo, > > > > > On Thu, May 24, 2018 at

Re: i.MX6 IPU CSI analog video input on Ventana

Philipp Zabel writes: > Maybe scanline interlave and double write reduction can't be used at the > same time? Well, if it works in non-interlaced modes - it may be the case. Perhaps the data reduction is done before the field merge step. This would make it incompatible:

Re: [PATCH v4 5/9] media: rcar-vin: Parse parallel input on Gen3

Hi Niklas, On Fri, May 25, 2018 at 12:29:44AM +0200, Niklas Söderlund wrote: > Hi Jacopo, > > Thanks for your work. > > I really like what you did with this patch in v4. Thanks for review and suggestions, what's there comes mostly from your comments and guidance. > > On 2018-05-25 00:02:15

Re: [PATCH v3] media: imx319: Add imx319 camera sensor driver

Hi Tomasz, On Fri, May 25, 2018 at 03:18:38PM +0900, Tomasz Figa wrote: > On Fri, May 25, 2018 at 5:47 AM Sakari Ailus > wrote: > > > Hi Jacopo, > > > On Thu, May 24, 2018 at 10:07:38PM +0200, jacopo mondi wrote: > > ... > > > > > about that, but I wonder why

Re: i.MX6 IPU CSI analog video input on Ventana

Steve Longerbeam writes: >> The manual says: Reduce Double Read or Writes (RDRW): >> This bit is relevant for YUV4:2:0 formats. For write channels: >> U and V components are not written to odd rows. >> >> How could it be so? With YUV420, are they normally written? > >

Re: [PATCH v10 01/16] videobuf2: Make struct vb2_buffer refcounted

Hello, On 5/21/18, Ezequiel Garcia wrote: > The in-fence implementation involves having a per-buffer fence callback, > that triggers on the fence signal. The fence callback is called > asynchronously > and needs a valid reference to the associated ideobuf2 buffer. > >

Re: i.MX6 IPU CSI analog video input on Ventana

Hi Steve, On Thu, 2018-05-24 at 14:33 -0700, Steve Longerbeam wrote: > Hi Krzysztof, Philipp, > > And I can confirm that capturing planar 4:2:0 (YU12, YV12, or NV12), > is broken because of the call to ipu_cpmem_skip_odd_chroma_rows(). > YU12 or NV12 images look correct again when commenting out

Re: i.MX6 IPU CSI analog video input on Ventana

On Thu, 2018-05-24 at 11:12 -0700, Steve Longerbeam wrote: [...] > > The following is required as well. Now the question is why we can't skip > > writing those odd UV rows. Anyway, with these 2 changes, I get a stable > > NTSC (and probably PAL) interlaced video stream. > > > > The manual says:

Re: [PATCH v3] media: imx319: Add imx319 camera sensor driver

On Fri, May 25, 2018 at 5:47 AM Sakari Ailus wrote: > Hi Jacopo, > On Thu, May 24, 2018 at 10:07:38PM +0200, jacopo mondi wrote: > ... > > > > about that, but I wonder why setting controls should be enabled only > > > > when streaming. I would have expected

Re: [PATCH v10 12/16] vb2: add in-fence support to QBUF

Hello, On 5/21/18, Ezequiel Garcia wrote: > From: Gustavo Padovan > > Receive in-fence from userspace and add support for waiting on them > before queueing the buffer to the driver. Buffers can't be queued to the > driver before its fences