Re: [PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Andrzej Hajda
On 01.03.2017 16:21, Nicolas Dufresne wrote: > Le mercredi 01 mars 2017 à 14:12 +0100, Andrzej Hajda a écrit : >> - on output side you have encoded bytestream - you cannot say about >> interlacing in such case, so the only valid value is NONE, >> - on capture side you have decoded frames, and in th

cron job: media_tree daily build: ERRORS

2017-03-01 Thread Hans Verkuil
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 Mar 2 05:00:19 CET 2017 media-tree git hash:e6b377dbbb944d5e3ceef4e5d429fc5c841e3692 media_build git

Re: Passionate Partner

2017-03-01 Thread M. G
Dear Sir, Did you recieved my mail? I have sent it twice without a response. Mr Masella Giuseppe

Re: [PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread Fengguang Wu
On Wed, Mar 01, 2017 at 10:58:59PM +0100, Daniel Glöckner wrote: On Wed, Mar 01, 2017 at 06:30:17PM +0800, kbuild test robot wrote: drivers/staging/media/atomisp/i2c/imx/imx.c:2486:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automat

[PATCH] [media] Staging: media: radio-bcm2048: remove incorrect __exit markups

2017-03-01 Thread Dmitry Torokhov
Even if bus is not hot-pluggable, devices can be unbound from the driver via sysfs, so we should not be using __exit annotations on remove() methods. The only exception is drivers registered with platform_driver_probe() which specifically disables sysfs bind/unbind attributes. Signed-off-by: Dmitr

[PATCH] [media] ad5820: remove incorrect __exit markups

2017-03-01 Thread Dmitry Torokhov
Even if bus is not hot-pluggable, devices can be unbound from the driver via sysfs, so we should not be using __exit annotations on remove() methods. The only exception is drivers registered with platform_driver_probe() which specifically disables sysfs bind/unbind attributes. Signed-off-by: Dmitr

Re: [PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread Alan Cox
On Wed, 2017-03-01 at 22:58 +0100, Daniel Glöckner wrote: > On Wed, Mar 01, 2017 at 06:30:17PM +0800, kbuild test robot wrote: > > > > drivers/staging/media/atomisp/i2c/imx/imx.c:2486:3-8: No need to > > set .owner here. The core will do it. > > > >  Remove .owner field if calls are used which se

Re: [PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread Daniel Glöckner
On Wed, Mar 01, 2017 at 06:30:17PM +0800, kbuild test robot wrote: > drivers/staging/media/atomisp/i2c/imx/imx.c:2486:3-8: No need to set .owner > here. The core will do it. > > Remove .owner field if calls are used which set it automatically > > Generated by: scripts/coccinelle/api/platform_no

Re: [PATCH] [media] coda: restore original firmware locations

2017-03-01 Thread Baruch Siach
Hi Philipp, On Wed, Mar 01, 2017 at 04:36:25PM +0100, Philipp Zabel wrote: > Recently, an unfinished patch was merged that added a third entry to the > beginning of the array of firmware locations without changing the code > to also look at the third element, thus pushing an old firmware location

[RFC PATCH 3/3] drm: rcar-du: Register a completion callback with VSP1

2017-03-01 Thread Kieran Bingham
Updating the state in a running VSP1 requires two interrupts from the VSP. Initially, the updated state will be committed - but only after the VSP1 has completed processing it's current frame will the new state be taken into account. As such, the committed state will only be 'completed' after an ex

[PATCH] [media] coda: restore original firmware locations

2017-03-01 Thread Philipp Zabel
Recently, an unfinished patch was merged that added a third entry to the beginning of the array of firmware locations without changing the code to also look at the third element, thus pushing an old firmware location off the list. Fixes: 8af7779f3cbc ("[media] coda: add Freescale firmware compatib

[PATCH] videodev2.h: map xvYCC601/709 to limited range quantization

2017-03-01 Thread Hans Verkuil
The xvYCC601/709 encodings were mapped by default to full range quantization. This is actually wrong since these encodings use limited range quantization, but accept values outside of the limited range. This makes sense since for values within the limited range it behaves exactly the same as BT.6

Re: [PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Nicolas Dufresne
Le mercredi 01 mars 2017 à 14:12 +0100, Andrzej Hajda a écrit : > - on output side you have encoded bytestream - you cannot say about > interlacing in such case, so the only valid value is NONE, > - on capture side you have decoded frames, and in this case it > depends > on the device and driver ca

Re: [PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Thibault Saunier
Hello, On 03/01/2017 11:35 AM, Nicolas Dufresne wrote: Le mercredi 01 mars 2017 à 14:12 +0100, Andrzej Hajda a écrit : On 01.03.2017 12:51, Thibault Saunier wrote: It is required by the standard that the field order is set by the driver, default to NONE in case any is provided, but we can bas

Re: [PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Nicolas Dufresne
Le mercredi 01 mars 2017 à 14:12 +0100, Andrzej Hajda a écrit : > On 01.03.2017 12:51, Thibault Saunier wrote: > > It is required by the standard that the field order is set by the > > driver, default to NONE in case any is provided, but we can > > basically > > accept any value provided by the use

[RFC PATCH 1/3] v4l: vsp1: Register pipe with output WPF

2017-03-01 Thread Kieran Bingham
The DRM object does not register the pipe with the WPF object. This is used internally throughout the driver as a means of accessing the pipe. As such this breaks operations which require access to the pipe from WPF interrupts. Register the pipe inside the WPF object after it has been declared as

[RFC PATCH 2/3] v4l: vsp1: extend VSP1 module API to allow DRM callback registration

2017-03-01 Thread Kieran Bingham
To be able to perform page flips in DRM without flicker we need to be able to notify the rcar-du module when the VSP has completed its processing. To synchronise the page flip events for userspace, we move the required event through the VSP to track the data flow. When the frame is completed, the

[RFC PATCH 0/3] RCAR-DU, VSP1: Prevent pre-emptive frame flips on VSP1-DRM pipelines

2017-03-01 Thread Kieran Bingham
The RCAR-DU utilises a running VSPD pipeline to perform processing for the display pipeline. Changes to this pipeline are performed with an atomic flush operation which updates the state in the VSPD. Due to the way the running pipeline is operated, any flush operation has an implicit latency of on

Re: [PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Thibault Saunier
Hello, On 03/01/2017 10:12 AM, Andrzej Hajda wrote: On 01.03.2017 12:51, Thibault Saunier wrote: It is required by the standard that the field order is set by the driver, default to NONE in case any is provided, but we can basically accept any value provided by the userspace as we will anyway

Re: [PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Andrzej Hajda
On 01.03.2017 12:51, Thibault Saunier wrote: > It is required by the standard that the field order is set by the > driver, default to NONE in case any is provided, but we can basically > accept any value provided by the userspace as we will anyway not > be able to do any deinterlacing. > > In this

[media] omap3isp: Correctly set IO_OUT_SEL and VP_CLK_POL for CCP2 mode

2017-03-01 Thread Pavel Machek
ISP CSI1 module needs all the bits correctly set to work. Signed-off-by: Ivaylo Dimitrov Signed-off-by: Pavel Machek index ca09523..e6584a2 100644 --- a/drivers/media/platform/omap3isp/ispccp2.c +++ b/drivers/media/platform/omap3isp/ispccp2.c @@ -213,14 +236,17 @@ static int ccp2_phyif_config(s

[PATCH v6 1/2] [media] exynos-gsc: Use user configured colorspace if provided

2017-03-01 Thread Thibault Saunier
Use colorspace provided by the user as we are only doing scaling and color encoding conversion, we won't be able to transform the colorspace itself and the colorspace won't mater in that operation. Also always use output colorspace on the capture side. If the user does not provide a colorspace do

[PATCH v6 2/2] [media] s5p-mfc: Handle 'v4l2_pix_format:field' in try_fmt and g_fmt

2017-03-01 Thread Thibault Saunier
It is required by the standard that the field order is set by the driver, default to NONE in case any is provided, but we can basically accept any value provided by the userspace as we will anyway not be able to do any deinterlacing. In this patch we also make sure to pass the interlacing mode pro

[PATCH v6 0/2] Fixes for colorspace logic in exynos-gsc and s5p-mfc drivers

2017-03-01 Thread Thibault Saunier
Hello, This patchset fixes a few issues on the colorspace logic for the exynos-gsc and s5p-mfc drivers. We now handle the colorspace in those drivers, and make sure to respect user setting if possible. We also now set the 'v4l2_pix_format:field' if userspace passed ANY, and replicate users val

[PATCH] staging/atomisp: fix semicolon.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_v4l2.c:465:2-3: Unneeded semicolon drivers/staging/media/atomisp/pci/atomisp2/./atomisp_v4l2.c:511:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Alan Cox Signed-off-by: Fenggu

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/gc0310.c:1470:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- gc0310.c |

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/imx/../ov8858.c:2199:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- ov8858

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/platform/clock/vlv2_plat_clock.c:248:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu

[PATCH] staging/atomisp: fix returnvar.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_subdev.c:161:5-8: Unneeded variable: "ret". Return "0" on line 163 Remove unneeded variable used to store return value. Generated by: scripts/coccinelle/misc/returnvar.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- Please take the pa

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/ov2680.c:1535:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- ov2680.c |

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/gc2235.c:1208:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- gc2235.c |

Re: [RFC 1/1] omap3isp: Ignore endpoints with invalid configuration

2017-03-01 Thread Pavel Machek
On Wed 2017-03-01 09:33:59, Sakari Ailus wrote: > Pavel Machek wrote: > >On Tue 2017-02-28 14:45:31, Sakari Ailus wrote: > >>Pavel Machek wrote: > >>>Tested-by: Pavel Machek > >> > >>Thanks! > >> > >>I've applied the patch, plus yours, to the ccp2 branch. > > > >Thanks! > > > >https://git.linuxtv.

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/ov2722.c:1352:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- ov2722.c |

[PATCH] staging/atomisp: fix returnvar.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_ioctl.c:560:5-8: Unneeded variable: "ret". Return "0" on line 577 Remove unneeded variable used to store return value. Generated by: scripts/coccinelle/misc/returnvar.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- Please take the pat

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/mt9m114.c:1946:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- mt9m114.c |

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/lm3554.c:986:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- lm3554.c |

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/ap1302.c:1250:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- ap1302.c |

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/ov5693/ov5693.c:2066:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- ov5693

[PATCH] staging/atomisp: fix platform_no_drv_owner.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/i2c/imx/imx.c:2486:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- imx.c |1

[PATCH] staging/atomisp: fix semicolon.cocci warnings

2017-03-01 Thread kbuild test robot
drivers/staging/media/atomisp/pci/atomisp2/./atomisp_compat_css20.c:551:3-4: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Alan Cox Signed-off-by: Fengguang Wu --- atomisp_compat_css20.c |2 +- 1 file changed, 1 insertion(+), 1

Re: Kaffeine commit b510bff2 won't compile

2017-03-01 Thread Mauro Carvalho Chehab
Hi Bill, Em Mon, 27 Feb 2017 23:46:09 -0500 bill murphy escreveu: > Hi Mauro, > > Thanks for looking in to it. All is well now. Good! Thanks for testing. > On a sidenote, given 700 MHz is used for LTE, and not broadcasting > > anymore, would you folks consider removing ch 52 thru 69 > > in

[PATCH v3 2/8] v4l: vsp1: Add histogram support

2017-03-01 Thread Laurent Pinchart
The histogram common code will be used to implement support for both the HGO and HGT histogram computation engines. Signed-off-by: Laurent Pinchart --- drivers/media/platform/Kconfig | 1 + drivers/media/platform/vsp1/Makefile | 1 + drivers/media/platform/vsp1/vsp1_histo.c | 6

[PATCH v3 3/8] v4l: vsp1: Support histogram generators in pipeline configuration

2017-03-01 Thread Laurent Pinchart
Histogram generators are single-pad entities that branch as leaf nodes at any point in the pipeline. Make sure that pipeline traversal and routing configuration support them correctly. Support for the actual HGO and HGT operation will come later. Signed-off-by: Laurent Pinchart --- drivers/medi