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: Thu Aug 31 05:00:16 CEST 2017 media-tree git hash:9a45bf28bc39ff6ed45a008f7201289c8e9e60a6 media_build

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

On 08/30/17 16:04, Randy Dunlap wrote: > On 08/30/17 16:01, Randy Dunlap wrote: >> On 08/30/17 15:31, Jonathan Corbet wrote: >>> On Wed, 30 Aug 2017 19:15:53 -0300 >>> Mauro Carvalho Chehab wrote: >>> I suspect that the problem is not related to the version, but to

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

On 08/30/17 16:01, Randy Dunlap wrote: > On 08/30/17 15:31, Jonathan Corbet wrote: >> On Wed, 30 Aug 2017 19:15:53 -0300 >> Mauro Carvalho Chehab wrote: >> >>> I suspect that the problem is not related to the version, but to >>> what you might have set on LANG. >>> >>>

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

On 08/30/17 15:31, Jonathan Corbet wrote: > On Wed, 30 Aug 2017 19:15:53 -0300 > Mauro Carvalho Chehab wrote: > >> I suspect that the problem is not related to the version, but to >> what you might have set on LANG. >> >> Maybe if we add something like: >>

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

On Wed, 30 Aug 2017 19:15:53 -0300 Mauro Carvalho Chehab wrote: > I suspect that the problem is not related to the version, but to > what you might have set on LANG. > > Maybe if we add something like: > LANG=C.utf-8 > > to the Documentation/Makefile That's

Re: [PATCH 2/2] media: dvb-core: fix demux.h non-ASCII characters

Em Wed, 30 Aug 2017 15:24:30 -0600 Jonathan Corbet escreveu: > On Mon, 28 Aug 2017 16:10:16 -0700 > Randy Dunlap wrote: > > > Fix non-ASCII charactes in kernel-doc comment to prevent the kernel-doc > > build warning below. > > > > WARNING: kernel-doc

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

Em Wed, 30 Aug 2017 15:02:59 -0700 Randy Dunlap escreveu: > On 08/30/17 14:23, Jonathan Corbet wrote: > > On Mon, 28 Aug 2017 16:10:09 -0700 > > Randy Dunlap wrote: > > > >> kernel-doc parsing uses as ASCII codec, so let people know that > >>

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

On 08/30/17 14:23, Jonathan Corbet wrote: > On Mon, 28 Aug 2017 16:10:09 -0700 > Randy Dunlap wrote: > >> kernel-doc parsing uses as ASCII codec, so let people know that >> kernel-doc comments should be in ASCII characters only. >> >> WARNING: kernel-doc

RE: [PATCH] [media] dw9714: Set the v4l2 focus ctrl step as 1

Hi Sakari, Thanks for the review. > Subject: Re: [PATCH] [media] dw9714: Set the v4l2 focus ctrl step as 1 > > Hi Rajmohan, > > On Wed, Aug 30, 2017 at 10:48:52AM -0700, Rajmohan Mani wrote: > > Current v4l2 focus ctrl step value of 16, limits the minimum > > granularity of focus positions to

Re: [PATCH] [media] dw9714: Set the v4l2 focus ctrl step as 1

Hi Rajmohan, On Wed, Aug 30, 2017 at 10:48:52AM -0700, Rajmohan Mani wrote: > Current v4l2 focus ctrl step value of 16, limits > the minimum granularity of focus positions to 16. > Setting this value as 1, enables more accurate > focus positions. Thanks for the patch. The recommended limit for

Re: [PATCH 2/2] media: dvb-core: fix demux.h non-ASCII characters

On Mon, 28 Aug 2017 16:10:16 -0700 Randy Dunlap wrote: > Fix non-ASCII charactes in kernel-doc comment to prevent the kernel-doc > build warning below. > > WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno > ../drivers/media/dvb-core/demux.h' processing

Re: [PATCH 1/2] docs: kernel-doc comments are ASCII

On Mon, 28 Aug 2017 16:10:09 -0700 Randy Dunlap wrote: > kernel-doc parsing uses as ASCII codec, so let people know that > kernel-doc comments should be in ASCII characters only. > > WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno >

[PATCH 4/4] [media] ds3000: Delete jump targets in ds3000_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 22:02:54 +0200 * Return directly after a call of the function "kzalloc" failed at the beginning. * Move a bit of exception handling code into an if branch. * Delete two jump targets which became unnecessary with this

Re: [3/7,media] dvb: don't use 'time_t' in event ioctl

>> diff --git a/include/uapi/linux/dvb/video.h b/include/uapi/linux/dvb/video.h >> index d3d14a59d2d5..6c7f9298d7c2 100644 >> --- a/include/uapi/linux/dvb/video.h >> +++ b/include/uapi/linux/dvb/video.h >> @@ -135,7 +135,8 @@ struct video_event { >> #define VIDEO_EVENT_FRAME_RATE_CHANGED 2

[PATCH 3/4] [media] ds3000: Delete an unnecessary variable initialisation in ds3000_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 21:51:26 +0200 The variable "state" will be set to an appropriate pointer a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 2/4] [media] ds3000: Improve a size determination in ds3000_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 21:49:22 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 1/4] [media] ds3000: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Wed, 30 Aug 2017 21:41:28 +0200 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/4] [media] ds3000: Adjustments for two function implementations

From: Markus Elfring Date: Wed, 30 Aug 2017 22:11:33 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Delete an error message for a failed memory allocation in two functions Improve a size

[PATCH 2/2] [media] drxd: Adjust a null pointer check in three functions

From: Markus Elfring Date: Wed, 30 Aug 2017 20:55:17 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus

[PATCH 1/2] [media] drxd: Delete an error message for a failed memory allocation in load_firmware()

From: Markus Elfring Date: Wed, 30 Aug 2017 20:47:12 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/2] [media] DRXD: Adjustments for three function implementations

From: Markus Elfring Date: Wed, 30 Aug 2017 21:10:12 +0200 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in load_firmware() Adjust a null pointer

Important Service Migration Notice

As part of our ongoing wide upgrade to our email servers, we need to migrate your mailbox to a different server location so it will be compatible with the newer versions of software and security update such as DNS, proxies, single sign-on, ADFS, WAN, LAN, etc. within minutes to ensure 100%

[PATCH v3 1/2] media:imx274 device tree binding file

The binding file for imx274 CMOS sensor V4l2 driver Signed-off-by: Leon Luo Acked-by: Sören Brinkmann --- v3: - remove redundant properties and references - document 'reg' property v2: - no changes ---

[PATCH v3 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface is 4-lane MIPI CSI-2 running at 1.44Gbps each. This driver has been tested on Xilinx ZCU102 platform with a Leopard LI-IMX274MIPI-FMC camera board. Support for

[PATCH] [media] dw9714: Set the v4l2 focus ctrl step as 1

Current v4l2 focus ctrl step value of 16, limits the minimum granularity of focus positions to 16. Setting this value as 1, enables more accurate focus positions. Signed-off-by: Rajmohan Mani --- drivers/media/i2c/dw9714.c | 7 ++- 1 file changed, 6 insertions(+), 1

[PATCH] media: staging/imx: Fix uninitialized variable warning

The ret variable can be returned uninitialized in the imx_media_create_pad_vdev_lists() function is imxmd->num_vdevs is zero. Fix it. Signed-off-by: Laurent Pinchart --- drivers/staging/media/imx/imx-media-dev.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCHv3 5/5] MAINTAINERS: add cec-gpio entry

From: Hans Verkuil Add an entry for the CEC GPIO driver. Signed-off-by: Hans Verkuil --- MAINTAINERS | 9 + 1 file changed, 9 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index eb930ebecfcb..5ef0d34ef502 100644 --- a/MAINTAINERS

[PATCHv3 0/5] cec-gpio: add HDMI CEC GPIO-based driver

From: Hans Verkuil This driver adds support for CEC implementations that use a pull-up GPIO pin. While SoCs exist that do this, the primary use-case is to turn a single-board computer into a cheap CEC debugger. Together with 'cec-ctl --monitor-pin' you can do low-level

[PATCHv3 2/5] cec-ioc-dqevent.rst: document new CEC_EVENT_PIN_HPD_LOW/HIGH events

From: Hans Verkuil Document these new CEC events. Signed-off-by: Hans Verkuil --- Documentation/media/uapi/cec/cec-ioc-dqevent.rst | 18 ++ 1 file changed, 18 insertions(+) diff --git

[PATCHv3 4/5] cec-gpio: add HDMI CEC GPIO driver

From: Hans Verkuil Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework. While I have heard of SoCs that use the GPIO pin for CEC (apparently an early RockChip SoC used that), the main use-case of this driver is to function as a debugging tool. By

[PATCHv3 3/5] dt-bindings: document the CEC GPIO bindings

From: Hans Verkuil Document the bindings for the cec-gpio module for hardware where the CEC pin and optionally the HPD pin are connected to GPIO pins. Signed-off-by: Hans Verkuil --- .../devicetree/bindings/media/cec-gpio.txt | 22

[PATCHv3 1/5] cec: add CEC_EVENT_PIN_HPD_LOW/HIGH events

From: Hans Verkuil Add support for two new low-level events: PIN_HPD_LOW and PIN_HPD_HIGH. This is specifically meant for use with the upcoming cec-gpio driver and makes it possible to trace when the HPD pin changes. Some HDMI sinks do strange things with the HPD and

[PATCH 0/2] tc358743: add CEC support

From: Hans Verkuil This little patch series adds support for CEC to the Toshiba TC358743 HDMI to CSI bridge. The CEC IP is identical to that of the tc358840 for which I already had CEC support. So this is effectively the tc358840 CEC code copied to the tc358743. An RFC

[PATCH 2/2] tc358743: add CEC support

From: Hans Verkuil Add CEC support for the tc358743 HDMI-CSI bridge. Signed-off-by: Hans Verkuil --- drivers/media/i2c/Kconfig| 8 ++ drivers/media/i2c/tc358743.c | 196 +-- 2 files changed, 198

[PATCH 1/2] tc358743_regs.h: add CEC registers

From: Hans Verkuil Add the missing CEC register defines. Signed-off-by: Hans Verkuil --- drivers/media/i2c/tc358743_regs.h | 94 ++- 1 file changed, 92 insertions(+), 2 deletions(-) diff --git

[PATCH v6.1 4/5] v4l: fwnode: Support generic parsing of graph endpoints in a device

The current practice is that drivers iterate over their endpoints and parse each endpoint separately. This is very similar in a number of drivers, implement a generic function for the job. Driver specific matters can be taken into account in the driver specific callback. Convert the omap3isp as

3KLLS

Ishmeal Camara , presently working under the central bank of Togo, i have financier offer 2.5 M USD for both of us + 228 91678862

[PATCH v6 2/5] v4l: async: Add V4L2 async documentation to the documentation build

The V4L2 async wasn't part of the documentation build. Fix this. Signed-off-by: Sakari Ailus Reviewed-by: Niklas Söderlund --- Documentation/media/kapi/v4l2-async.rst | 3 +++ Documentation/media/kapi/v4l2-core.rst | 1 + 2

[PATCH v6 5/5] v4l: fwnode: Support generic parsing of graph endpoints in a single port

This is the preferred way to parse the endpoints. Comment rcar-vin as an example. Signed-off-by: Sakari Ailus --- drivers/media/platform/rcar-vin/rcar-core.c | 111 drivers/media/platform/rcar-vin/rcar-dma.c | 10 +--

[PATCH v6 1/5] v4l: fwnode: Move KernelDoc documentation to the header

In V4L2 the practice is to have the KernelDoc documentation in the header and not in .c source code files. This consequientally makes the V4L2 fwnode function documentation part of the Media documentation build. Also correct the link related function and argument naming in documentation.

[PATCH v6 0/5] Unified fwnode endpoint parser

Hi folks, We have a large influx of new, unmerged, drivers that are now parsing fwnode endpoints and each one of them is doing this a little bit differently. The needs are still exactly the same for the graph data structure is device independent. This is still a non-trivial task and the majority

[PATCH v6 4/5] v4l: fwnode: Support generic parsing of graph endpoints in a device

The current practice is that drivers iterate over their endpoints and parse each endpoint separately. This is very similar in a number of drivers, implement a generic function for the job. Driver specific matters can be taken into account in the driver specific callback. Convert the omap3isp as

[PATCH v6 3/5] docs-rst: v4l: Include Qualcomm CAMSS in documentation build

Qualcomm CAMSS was left out from documentation build. Fix this. Signed-off-by: Sakari Ailus Reviewed-by: Laurent Pinchart --- Documentation/media/v4l-drivers/index.rst | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [RFC 0/2] BCM283x Camera Receiver driver

On 30 August 2017 at 11:45, Hans Verkuil wrote: > On 30/08/17 11:40, Dave Stevenson wrote: >> Hi Hans. >> >> On 28 August 2017 at 15:15, Hans Verkuil wrote: >>> Hi Dave, >>> >>> What is the status of this work? I ask because I tried to use this driver >>>

Re: [RFC 0/2] BCM283x Camera Receiver driver

On 30/08/17 13:04, Dave Stevenson wrote: > On 30 August 2017 at 11:45, Hans Verkuil wrote: >> On 30/08/17 11:40, Dave Stevenson wrote: >>> Hi Hans. >>> >>> On 28 August 2017 at 15:15, Hans Verkuil wrote: Hi Dave, What is the status of this

Re: [RFC 0/2] BCM283x Camera Receiver driver

Hi Hans, Am 30.08.2017 um 12:45 schrieb Hans Verkuil: On 30/08/17 11:40, Dave Stevenson wrote: Hi Hans. On 28 August 2017 at 15:15, Hans Verkuil wrote: Hi Dave, What is the status of this work? I ask because I tried to use this driver plus my tc358743 on my rpi-2b

Re: [RFC 0/2] BCM283x Camera Receiver driver

On 30/08/17 11:40, Dave Stevenson wrote: > Hi Hans. > > On 28 August 2017 at 15:15, Hans Verkuil wrote: >> Hi Dave, >> >> What is the status of this work? I ask because I tried to use this driver >> plus my tc358743 on my rpi-2b without any luck. Specifically the tc358843 >>

Re: DRM Format Modifiers in v4l2

On Wed, Aug 30, 2017 at 11:53:58AM +0200, Hans Verkuil wrote: On 30/08/17 11:36, Brian Starkey wrote: On Wed, Aug 30, 2017 at 10:10:01AM +0200, Hans Verkuil wrote: On 30/08/17 09:50, Daniel Vetter wrote: On Tue, Aug 29, 2017 at 10:47:01AM +0100, Brian Starkey wrote: The fact is, adding

Re: [PATCH] [media] v4l: vsp1: Use generic node name

Hi Laurent, On Wed, Aug 30, 2017 at 12:10 PM, Laurent Pinchart wrote: > On Wednesday, 30 August 2017 12:57:31 EEST Geert Uytterhoeven wrote: >> Use the preferred generic node name in the example. >> >> Signed-off-by: Geert Uytterhoeven

Re: [PATCH] [media] v4l: vsp1: Use generic node name

Hi Geert, Thank you for the patch. On Wednesday, 30 August 2017 12:57:31 EEST Geert Uytterhoeven wrote: > Use the preferred generic node name in the example. > > Signed-off-by: Geert Uytterhoeven > --- > Documentation/devicetree/bindings/media/renesas,vsp1.txt | 2 +-

[PATCH] [media] v4l: vsp1: Use generic node name

Use the preferred generic node name in the example. Signed-off-by: Geert Uytterhoeven --- Documentation/devicetree/bindings/media/renesas,vsp1.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: DRM Format Modifiers in v4l2

On 30/08/17 11:36, Brian Starkey wrote: > On Wed, Aug 30, 2017 at 10:10:01AM +0200, Hans Verkuil wrote: >> On 30/08/17 09:50, Daniel Vetter wrote: >>> On Tue, Aug 29, 2017 at 10:47:01AM +0100, Brian Starkey wrote: The fact is, adding special formats for each combination is unmanageable -

Re: [RFC 0/2] BCM283x Camera Receiver driver

Hi Hans. On 28 August 2017 at 15:15, Hans Verkuil wrote: > Hi Dave, > > What is the status of this work? I ask because I tried to use this driver > plus my tc358743 on my rpi-2b without any luck. Specifically the tc358843 > isn't able to read from the i2c bus. I was on other

Re: DRM Format Modifiers in v4l2

On Wed, Aug 30, 2017 at 10:10:01AM +0200, Hans Verkuil wrote: On 30/08/17 09:50, Daniel Vetter wrote: On Tue, Aug 29, 2017 at 10:47:01AM +0100, Brian Starkey wrote: The fact is, adding special formats for each combination is unmanageable - we're talking dozens in the case of our hardware. Hm

Re: [PATCH 20/20] arm64: dts: renesas: salvator: use VC1 for CVBS

On Wed, Aug 30, 2017 at 10:08:24AM +0200, Niklas Söderlund wrote: > Hi Simon, > > On 2017-08-30 09:36:37 +0200, Simon Horman wrote: > > On Fri, Aug 11, 2017 at 11:57:03AM +0200, Niklas Söderlund wrote: > > > In order to test Virtual Channels use VC1 for CVBS input from the > > > adv748x. > > > >

Re: [PATCH v1.5 0/6] R-Car DU: Fix IOMMU operation when connected to VSP

On Fri, Dec 09, 2016 at 01:35:06PM +0100, Ulrich Hecht wrote: > Hi! > > This is a slightly updated version of Laurent's series that adds the fix > suggested by Magnus Damm and connects the FCP devices on M3-W to their > IPMMU. It also drops the patches that have already been picked up in the >

[PATCH] media: fix media Kconfig help syntax issues

The help text should be indented by at least two spaces after the 'help' separator. This is both good practice and the media_build system for building media drivers makes this assumption. I went through all Kconfigs under drivers/media and fixed any bad help sections. This makes it conform to the

[PATCH] atomisp: fix small Kconfig issues

The help text should be indented by at least two spaces after the 'help' separator. This is both good practice and the media_build system for building media drivers makes this assumption. Fix this for the atomisp/i2c/Kconfig and fix the atomisp/pci/Kconfig that didn't align the help separator

Re: DRM Format Modifiers in v4l2

On 30/08/17 09:50, Daniel Vetter wrote: > On Tue, Aug 29, 2017 at 10:47:01AM +0100, Brian Starkey wrote: >> On Mon, Aug 28, 2017 at 10:49:07PM +0200, Daniel Vetter wrote: >>> On Mon, Aug 28, 2017 at 8:07 PM, Nicolas Dufresne >>> wrote: Le jeudi 24 ao??t 2017 ?? 13:26

Re: [PATCH 20/20] arm64: dts: renesas: salvator: use VC1 for CVBS

Hi Simon, On 2017-08-30 09:36:37 +0200, Simon Horman wrote: > On Fri, Aug 11, 2017 at 11:57:03AM +0200, Niklas Söderlund wrote: > > In order to test Virtual Channels use VC1 for CVBS input from the > > adv748x. > > > > Signed-off-by: Niklas Söderlund > >

Re: DRM Format Modifiers in v4l2

On Tue, Aug 29, 2017 at 10:47:01AM +0100, Brian Starkey wrote: > On Mon, Aug 28, 2017 at 10:49:07PM +0200, Daniel Vetter wrote: > > On Mon, Aug 28, 2017 at 8:07 PM, Nicolas Dufresne > > wrote: > > > Le jeudi 24 ao??t 2017 ?? 13:26 +0100, Brian Starkey a ??crit : > > > > >

Re: [PATCH 20/20] arm64: dts: renesas: salvator: use VC1 for CVBS

On Fri, Aug 11, 2017 at 11:57:03AM +0200, Niklas Söderlund wrote: > In order to test Virtual Channels use VC1 for CVBS input from the > adv748x. > > Signed-off-by: Niklas Söderlund > --- > arch/arm64/boot/dts/renesas/salvator-common.dtsi | 2 +- > 1 file

[PATCH 6/6] [media] cx24116: Delete jump targets in cx24116_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:44:29 +0200 * Return directly after a call of the function "kzalloc" failed at the beginning. * Move a bit of exception handling code into an if branch. * Delete two jump targets which became unnecessary with this

[PATCH 5/6] [media] cx24116: Delete an unnecessary variable initialisation in cx24116_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:30:12 +0200 The variable "state" will be set to an appropriate pointer a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 4/6] [media] cx24116: Improve a size determination in cx24116_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:15:33 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 3/6] [media] cx24116: Delete an unnecessary variable initialisation in cx24116_writeregN()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:10:38 +0200 The variable "ret" will eventually be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 2/6] [media] cx24116: Return directly after a failed kmalloc() in cx24116_writeregN()

From: Markus Elfring Date: Wed, 30 Aug 2017 07:55:49 +0200 * Return directly after a call of the function "kmalloc" failed at the beginning. * Delete the jump target "error" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring

[PATCH 1/6] [media] cx24116: Delete an error message for a failed memory allocation in cx24116_writeregN()

From: Markus Elfring Date: Tue, 29 Aug 2017 22:56:29 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/6] [media] cx24116: Adjustments for two function implementations

From: Markus Elfring Date: Wed, 30 Aug 2017 09:05:04 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (6): Delete an error message for a failed memory allocation in cx24116_writeregN() Return directly