[PATCH v5 16/16] MAINTAINERS: add entry for Rockchip ISP1 driver

From: Jacob Chen Add MAINTAINERS entry for the rockchip isp1 driver. This driver is maintained by rockchip officially and it will be used for rockchip SoC on all linux-kernel based OS. Signed-off-by: Jacob Chen --- MAINTAINERS | 10

[PATCH v5 08/16] media: rkisp1: add capture device driver

From: Jacob Chen This is the capture device interface driver that provides the v4l2 user interface. Frames can be received from ISP1. Signed-off-by: Jacob Chen Signed-off-by: Shunqian Zheng Signed-off-by: Yichong

[PATCH v5 10/16] dt-bindings: Document the Rockchip ISP1 bindings

From: Jacob Chen Add DT bindings documentation for Rockchip ISP1 Signed-off-by: Jacob Chen Reviewed-by: Rob Herring --- .../devicetree/bindings/media/rockchip-isp1.txt| 69 ++ 1 file changed, 69

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: Fri Dec 29 05:00:16 CET 2017 media-tree git hash:201b56737f4ea59ee840ebdb88a9970ea6d49cf1 media_build

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 28 Dec 2017, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > > > Yes, you missed the typo in the command line. It should be: > > > > > > 'trace_event=irq_vectors:* ftrace_dump_on_oops' > > > > Indeed. >

IMX6 interlaced capture

Steve/Hans, I'm trying to get interlaced capture working with the TDA1997x driver I've been working on which is connected to an IMX6 CSI. The particular board I'm currently testing on is an IMX6Q which has both a TDA19971 HDMI receiver as well as an ADV7180 analog video decoder. The media-ctl

[linuxtv-media:master 3292/3294] htmldocs: include/media/dmxdev.h:152: warning: Function parameter or member 'vb2_ctx' not described in 'dmxdev_filter'

tree: git://linuxtv.org/media_tree.git master head: 201b56737f4ea59ee840ebdb88a9970ea6d49cf1 commit: fada1935590f66dc6784981e0d557ca09013c847 [3292/3294] media: move dvb kAPI headers to include/media reproduce: make htmldocs All warnings (new ones prefixed by >>):

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > > Yes, you missed the typo in the command line. It should be: > > > > 'trace_event=irq_vectors:* ftrace_dump_on_oops' > > Indeed. > > So, I had to disable LOCAL_TIMER_VECTOR,

[linuxtv-media:master 3281/3294] drivers/media/dvb-core/dvb_vb2.c:173: undefined reference to `vb2_core_queue_init'

tree: git://linuxtv.org/media_tree.git master head: 201b56737f4ea59ee840ebdb88a9970ea6d49cf1 commit: 57868acc369ab73ec8f6b43a0c6749077376b189 [3281/3294] media: videobuf2: Add new uAPI for DVB streaming I/O config: i386-randconfig-s1-201752 (attached as .config) compiler: gcc-6 (Debian

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > > > [

[linuxtv-media:master 3281/3294] drivers/media/dvb-core/dvb_vb2.c:170: undefined reference to `vb2_vmalloc_memops'

tree: git://linuxtv.org/media_tree.git master head: 201b56737f4ea59ee840ebdb88a9970ea6d49cf1 commit: 57868acc369ab73ec8f6b43a0c6749077376b189 [3281/3294] media: videobuf2: Add new uAPI for DVB streaming I/O config: i386-randconfig-n0-201752 (attached as .config) compiler: gcc-7 (Debian

Re: v4.15: camera problems on n900

On Wed 2017-12-27 23:17:19, Sakari Ailus wrote: > On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > > Hi! > > > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > > seconds, but then I get repeated oopses. > > > > On v4.15-rc0.5 (commit

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > >

[PATCH v6 1/6] v4l2-dv-timings: add v4l2_hdmi_colorimetry()

From: Hans Verkuil Add the v4l2_hdmi_colorimetry() function so we have a single function that determines the colorspace, YCbCr encoding, quantization range and transfer function from the InfoFrame data. Signed-off-by: Hans Verkuil Signed-off-by: Tim

[PATCH v6 0/6] TDA1997x HDMI video receiver

This is a v4l2 subdev driver supporting the TDA1997x HDMI video receiver. I've tested this on a Gateworks GW54xx/GW551x with an IMX6Q/IMX6DL which uses the TDA19971 with 16bits connected to the IMX6 CSI and single-lane I2S audio providing 2-channel audio. For this configuration I've tested both

[PATCH v6 6/6] ARM: dts: imx: Add TDA19971 HDMI Receiver to GW551x

Cc: Shawn Guo Signed-off-by: Tim Harvey --- v6: no changes v5: - add missing audmux config --- arch/arm/boot/dts/imx6qdl-gw551x.dtsi | 138 ++ 1 file changed, 138 insertions(+) diff --git

[PATCH v6 2/6] MAINTAINERS: add entry for NXP TDA1997x driver

Signed-off-by: Tim Harvey --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index aa71ab52f..502bc97 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -13244,6 +13244,14 @@ T: git git://linuxtv.org/mkrufky/tuners.git S:

[PATCH v6 4/6] media: i2c: Add TDA1997x HDMI receiver driver

Add support for the TDA1997x HDMI receivers. Cc: Hans Verkuil Signed-off-by: Tim Harvey --- v6: - fix return on regulator enablei in tda1997x_set_power() (Fabio) - replace copyright with SPDX tag (Philippe) - fix colorspace handling (Hans) v5: -

[PATCH v6 5/6] ARM: dts: imx: Add TDA19971 HDMI Receiver to GW54xx

The GW54xx has a front-panel microHDMI connector routed to a TDA19971 which is connected the the IPU CSI when using IMX6Q. Cc: Shawn Guo Signed-off-by: Tim Harvey --- v6: no changes v5: - remove leading 0 from unit address (Shawn) - add newline

[PATCH v6 3/6] media: dt-bindings: Add bindings for TDA1997X

Acked-by: Rob Herring Acked-by: Sakari Ailus Signed-off-by: Tim Harvey --- v6: - replace copyright with SPDX tag (Philippe) - added Rob's ack (Rob) v5: - added Sakari's ack v4: - move include/dt-bindings/media/tda1997x.h to

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 2017-12-28 at 21:31 +0200, Andy Shevchenko wrote: > Anything I missed? Perhaps I could bisect, though it's not so trivial in this case, when I have a little more time. I guess it might take up to ~16 steps. If you can point to more narrow range, it would be great. -- Andy Shevchenko

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > CPU#0, > > > > should never happen. > > > > [

[PATCH 2/2] media: don't include drivers/media/i2c at cflags

Most of the I2C headers got moved a long time ago to include/media/i2c. Stop including them at the patch. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/i2c/cx25840/Makefile| 2 -- drivers/media/pci/bt8xx/Makefile | 1 -

Re: [PATCH 4/5] media: vb2: add pr_fmt() macro

On Thu, Dec 28, 2017 at 02:29:37PM -0200, Mauro Carvalho Chehab wrote: > Simplify the pr_foo() macros by adding a pr_fmt() macro. > > Signed-off-by: Mauro Carvalho Chehab On 4th and 5th: Acked-by: Sakari Ailus -- Sakari Ailus

Re: [PATCH 2/5] media: vb2: Fix a bug about unnecessary calls to queue cancel and free

On Thu, Dec 28, 2017 at 02:29:35PM -0200, Mauro Carvalho Chehab wrote: > From: Satendra Singh Thakur > > Currently, there's a logic with checks if *count is non-zero, > q->num_buffers is zero and q->memory is different than memory. > > That's flawed when the device is

Re: [PATCH 1/5] media: vb2: don't go out of the buffer range

Hi Mauro, On Thu, Dec 28, 2017 at 02:29:34PM -0200, Mauro Carvalho Chehab wrote: > Currently, there's no check if an invalid buffer range > is passed. However, while testing DVB memory mapped apps, > I got this: > >videobuf2_core: VB: num_buffers -2143943680, buffer 33, index -2143943647 >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > [ 85.167061] spurious APIC interrupt through vector ff on CPU#0, > > > should never happen. > > > [ 85.199886] atomisp-isp2 :00:03.0: stream[0] started. > > > > > > and Ctrl+C

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Shevchenko, Andriy wrote: > > > Hi! > > > > Experimenting with AtomISP (yes, code is ugly and MSI handling > > rather > > hackish, though...). > > > > So, with v4.14 base: > > > > [ 33.639224] atomisp-isp2

[linuxtv-media:master 3288/3291] drivers/media/common/videobuf/videobuf2-core.c:2525:34-35: Unneeded semicolon

tree: git://linuxtv.org/media_tree.git master head: a114a585be4f3173fe454921a0918fb7e71633b0 commit: 03fbdb2fc2b8bb27b0ee0534fd3e9c57cdc3854a [3288/3291] media: move videobuf2 to drivers/media/common config: i386-allmodconfig (attached as .config) compiler: gcc-7 (Debian 7.2.0-12) 7.2.1

[PATCH] media: fix semicolon.cocci warnings

From: Fengguang Wu drivers/media/common/videobuf/videobuf2-core.c:2525:34-35: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: 03fbdb2fc2b8 ("media: move videobuf2 to drivers/media/common") Signed-off-by:

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 2017-12-28 at 19:17 +0200, Andy Shevchenko wrote: > Hi! > > Experimenting with AtomISP (yes, code is ugly and MSI handling rather > hackish, though...). > > So, with v4.14 base: See additional note below. > > [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for > asd0 >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

On Thu, 28 Dec 2017, Shevchenko, Andriy wrote: > Hi! > > Experimenting with AtomISP (yes, code is ugly and MSI handling rather > hackish, though...). > > So, with v4.14 base: > > [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for asd0 > [ 33.652355] atomisp-isp2

IRQ behaivour has been changed from v4.14 to v4.15-rc1

Hi! Experimenting with AtomISP (yes, code is ugly and MSI handling rather hackish, though...). So, with v4.14 base: [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for asd0 [ 33.652355] atomisp-isp2 :00:03.0: irq:0x20 [ 33.662456] atomisp-isp2 :00:03.0: irq:0x20 [

[PATCH 4/5] media: vb2: add pr_fmt() macro

Simplify the pr_foo() macros by adding a pr_fmt() macro. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/common/videobuf/videobuf2-core.c | 30 ++ 1 file changed, 16 insertions(+), 14 deletions(-) diff --git

[PATCH 5/5] media: vb2: add a new warning about pending buffers

There's a logic at the VB2 core that produces a WARN_ON if there are still buffers waiting to be filled. However, it doesn't indicate what buffers are still opened, with makes harder to identify issues inside caller drivers. So, add a new pr_warn() pointing to such buffers. That, together with

[PATCH 2/5] media: vb2: Fix a bug about unnecessary calls to queue cancel and free

From: Satendra Singh Thakur Currently, there's a logic with checks if *count is non-zero, q->num_buffers is zero and q->memory is different than memory. That's flawed when the device is initialized, or after the queues are freed, as it does, unnecessary calls to

[PATCH 1/5] media: vb2: don't go out of the buffer range

Currently, there's no check if an invalid buffer range is passed. However, while testing DVB memory mapped apps, I got this: videobuf2_core: VB: num_buffers -2143943680, buffer 33, index -2143943647 unable to handle kernel paging request at 888b773c0890 IP:

[PATCH 0/5] some VB2 bug fixes and improvements

While working with DVB memory mapped patches, a few issues were noticed at VB2. None of those patches are directly related to dvb-vb2 logic, but they fix 3 issues found at VB2. There are two other patches that improve vb2 print messages, by defining pr_fmt() macro and by making clearer what's

[PATCH 3/5] media: vb2: Enforce VB2_MAX_FRAME in vb2_core_reqbufs better

From: Sakari Ailus The check for the number of buffers requested against the maximum, VB2_MAX_FRAME, was performed before checking queue's minimum number of buffers. Reverse the order, thus ensuring that under no circumstances num_buffers exceeds VB2_MAX_FRAME here.

Re: [ov2722 Error] atomisp: ERROR

On Tue, 2017-10-31 at 16:35 +0200, Andrei Lavreniyuk wrote: > Hi, > > Very long I try to run ov2722 on Acer Aspire SW5-012 / Fendi2 Z3537F > > Kernel 4.13.10 + atomisp from 4.14 and all your corrections for > atomisp > from here Check this [1] thread, please. [1]:

Re: [BUG] atomisp_ov2680 not initializing correctly

On Sat, 2017-12-23 at 01:31 +0100, Kristian Beilke wrote: > On 12/21/2017 03:23 PM, Andy Shevchenko wrote: > > On Thu, 2017-12-21 at 13:54 +0100, Kristian Beilke wrote: > > > On Tue, Dec 19, 2017 at 10:37:01PM +0200, Andy Shevchenko wrote: > > > > On Tue, 2017-12-19 at 14:00 +0200, Sakari Ailus

[PATCH] media: dvb-core: make DVB mmap API optional

This API is still experimental. Make it optional, allowing to compile the code without it. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/Kconfig| 12 drivers/media/dvb-core/Makefile | 3 +- drivers/media/dvb-core/dmxdev.c | 66

Re: [PATCH v3] media: videobuf2-core: don't go out of the buffer range

On Thu, Dec 28, 2017 at 12:16:47PM -0200, Mauro Carvalho Chehab wrote: > Currently, there's no check if an invalid buffer range > is passed. However, while testing DVB memory mapped apps, > I got this: > >videobuf2_core: VB: num_buffers -2143943680, buffer 33, index -2143943647 >unable to

[PATCH 1/1] vb2: Enforce VB2_MAX_FRAME in vb2_core_reqbufs better

The check for the number of buffers requested against the maximum, VB2_MAX_FRAME, was performed before checking queue's minimum number of buffers. Reverse the order, thus ensuring that under no circumstances num_buffers exceeds VB2_MAX_FRAME here. Also add a warning of the condition.

[PATCH v3] media: videobuf2-core: don't go out of the buffer range

Currently, there's no check if an invalid buffer range is passed. However, while testing DVB memory mapped apps, I got this: videobuf2_core: VB: num_buffers -2143943680, buffer 33, index -2143943647 unable to handle kernel paging request at 888b773c0890 IP:

[PATCH v2 0/9] Renesas Capture Engine Unit (CEU) V4L2 driver

Hello, second round for Renesas CEU driver. I have closed review comments received on v1 and tested again on RZ and SH4 platforms to capture images in all available output formats (NV16/61, NV12/21 and YUYV). The patch is now based on v4.15-rc4, with a few patches on top to help testing on

[PATCH v2 1/9] dt-bindings: media: Add Renesas CEU bindings

Add bindings documentation for Renesas Capture Engine Unit (CEU). Signed-off-by: Jacopo Mondi --- .../devicetree/bindings/media/renesas,ceu.txt | 85 ++ 1 file changed, 85 insertions(+) create mode 100644

[PATCH v2 3/9] v4l: platform: Add Renesas CEU driver

Add driver for Renesas Capture Engine Unit (CEU). The CEU interface supports capturing 'data' (YUV422) and 'images' (NV[12|21|16|61]). This driver aims to replace the soc_camera-based sh_mobile_ceu one. Tested with ov7670 camera sensor, providing YUYV_2X8 data on Renesas RZ platform GR-Peach.

[PATCH v2 5/9] arch: sh: migor: Use new renesas-ceu camera driver

Migo-R platform uses sh_mobile_ceu camera driver, which is now being replaced by a proper V4L2 camera driver named 'renesas-ceu'. Move Migo-R platform to use the v4l2 renesas-ceu camera driver interface and get rid of soc_camera defined components used to register sensor drivers and of platform

[PATCH v2 4/9] ARM: dts: r7s72100: Add Capture Engine Unit (CEU)

Add Capture Engine Unit (CEU) node to device tree. Signed-off-by: Jacopo Mondi --- arch/arm/boot/dts/r7s72100.dtsi | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/arch/arm/boot/dts/r7s72100.dtsi b/arch/arm/boot/dts/r7s72100.dtsi

[PATCH v2 7/9] media: i2c: ov772x: Remove soc_camera dependencies

Remove soc_camera framework dependencies from ov772x sensor driver. - Handle clock and gpios - Register async subdevice - Remove soc_camera specific g/s_mbus_config operations - Change image format colorspace to SRGB - Remove sizes crop from get_selection as driver can't scale - Add kernel doc to

[PATCH v2 6/9] v4l: i2c: Copy ov772x soc_camera sensor driver

Copy the soc_camera based driver in v4l2 sensor driver directory. This commit just copies the original file without modifying it. No modification to KConfig and Makefile as soc_camera framework dependencies need to be removed first in next commit. Signed-off-by: Jacopo Mondi

[PATCH v2 8/9] v4l: i2c: Copy tw9910 soc_camera sensor driver

Copy the soc_camera based driver in v4l2 sensor driver directory. This commit just copies the original file without modifying it. No modification to KConfig and Makefile as soc_camera framework dependencies need to be removed first in next commit. Signed-off-by: Jacopo Mondi

[PATCH v2 9/9] media: i2c: tw9910: Remove soc_camera dependencies

Remove soc_camera framework dependencies from tw9910 sensor driver. - Handle clock and gpios - Register async subdevice - Remove soc_camera specific g/s_mbus_config operations - Add kernel doc to driver interface header file - Adjust build system This commit does not remove the original

[PATCH v2 2/9] include: media: Add Renesas CEU driver interface

Add renesas-ceu header file. Do not remove the existing sh_mobile_ceu.h one as long as the original driver does not go away. Signed-off-by: Jacopo Mondi --- include/media/drv-intf/renesas-ceu.h | 20 1 file changed, 20 insertions(+) create mode

[PATCH 1/2] media: videobuf2-core: don't go out of the buffer range

Currently, there's no check if an invalid buffer range is passed. However, while testing DVB memory mapped apps, I got this: videobuf2_core: VB: num_buffers -2143943680, buffer 33, index -2143943647 unable to handle kernel paging request at 888b773c0890 IP:

[PATCH 2/2] media: dvb_vb2: limit reqbufs size to a sane value

It is not a good idea to let users to request a very high buffer size. So, add an upper limit. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/dvb-core/dvb_vb2.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/media/dvb-core/dvb_vb2.c

Re: [PATCH] videobuf2-core: don't go out of the buffer range

On Thu, Dec 28, 2017 at 10:25:29AM -0200, Mauro Carvalho Chehab wrote: > Em Thu, 28 Dec 2017 14:19:56 +0200 > Sakari Ailus escreveu: > > > Hi Mauro, > > > > Thanks for the patch. > > > > On Thu, Dec 28, 2017 at 10:02:33AM -0200, Mauro Carvalho Chehab wrote: > > >

Re: [PATCH] uvcvideo: add a D4M camera description

Hi Sakari, On Wed, 27 Dec 2017, Sakari Ailus wrote: > Hi Guennadi, > > Thanks for the patch! > > On Sat, Dec 23, 2017 at 12:11:00PM +0100, Guennadi Liakhovetski wrote: > > From: Guennadi Liakhovetski > > > > D4M is a mobile model from the D4XX family of Intel

Re: [PATCH] videobuf2-core: don't go out of the buffer range

Em Thu, 28 Dec 2017 14:19:56 +0200 Sakari Ailus escreveu: > Hi Mauro, > > Thanks for the patch. > > On Thu, Dec 28, 2017 at 10:02:33AM -0200, Mauro Carvalho Chehab wrote: > > Currently, there's no check if an invalid buffer range > > is passed. However, while

Re: [PATCH] videobuf2-core: don't go out of the buffer range

Hi Mauro, Thanks for the patch. On Thu, Dec 28, 2017 at 10:02:33AM -0200, Mauro Carvalho Chehab wrote: > Currently, there's no check if an invalid buffer range > is passed. However, while testing DVB memory mapped apps, > I got this: > >videobuf2_core: VB: num_buffers -2143943680, buffer

[PATCH] videobuf2-core: don't go out of the buffer range

Currently, there's no check if an invalid buffer range is passed. However, while testing DVB memory mapped apps, I got this: videobuf2_core: VB: num_buffers -2143943680, buffer 33, index -2143943647 unable to handle kernel paging request at 888b773c0890 IP:

Re: v4.15: camera problems on n900

On Wed 2017-12-27 23:17:19, Sakari Ailus wrote: > On Wed, Dec 27, 2017 at 10:05:43PM +0100, Pavel Machek wrote: > > Hi! > > > > In v4.14, back camera on N900 works. On v4.15-rc1.. it works for few > > seconds, but then I get repeated oopses. > > > > On v4.15-rc0.5 (commit