cron job: media_tree daily build: OK

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 28 04:00:25 CEST 2016 git branch: test git hash: bc2b80ee3490651904f121eac1c8fb7652d48253 gcc

Re: [PATCH] remove lots of IS_ERR_VALUE abuses

On Fri, May 27, 2016 at 2:23 PM, Arnd Bergmann wrote: > > This patch changes all users of IS_ERR_VALUE() that I could find > on 32-bit ARM randconfig builds and x86 allmodconfig. For the > moment, this doesn't change the definition of IS_ERR_VALUE() > because there are probably

Re: [PATCH] remove lots of IS_ERR_VALUE abuses

On Fri, May 27, 2016 at 11:23:25PM +0200, Arnd Bergmann wrote: > @@ -837,7 +837,7 @@ static int load_flat_shared_library(int id, struct > lib_info *libs) > > res = prepare_binprm(); > > - if (!IS_ERR_VALUE(res)) > + if (res >= 0) if (res == 0), please -

Re: [PATCH] remove lots of IS_ERR_VALUE abuses

On 27/05/16 22:23, Arnd Bergmann wrote: drivers/acpi/acpi_dbg.c | 22 +++--- drivers/ata/sata_highbank.c | 2 +- drivers/clk/tegra/clk-tegra210.c | 2 +- drivers/cpufreq/omap-cpufreq.c | 2

Re: [PATCH] remove lots of IS_ERR_VALUE abuses

On Fri, May 27, 2016 at 2:46 PM, Andrew Morton wrote: > > So you do plan to add some sort of typechecking into IS_ERR_VALUE()? The easiest way to do it is to just turn the (x) into (unsigned long)(void *)(x), which then complains about casting an integer to a pointer

Re: [PATCH] remove lots of IS_ERR_VALUE abuses

On Fri, 27 May 2016 23:23:25 +0200 Arnd Bergmann wrote: > Most users of IS_ERR_VALUE() in the kernel are wrong, as they > pass an 'int' into a function that takes an 'unsigned long' > argument. This happens to work because the type is sign-extended > on 64-bit architectures before

[PATCH] remove lots of IS_ERR_VALUE abuses

Most users of IS_ERR_VALUE() in the kernel are wrong, as they pass an 'int' into a function that takes an 'unsigned long' argument. This happens to work because the type is sign-extended on 64-bit architectures before it gets converted into an unsigned type. However, anything that passes an

Re: [PATCH v3] media: Media Device Allocator API

On 05/27/2016 10:25 PM, Shuah Khan wrote: > Media Device Allocator API to allows multiple drivers share a media device. > Using this API, drivers can allocate a media device with the shared struct > device as the key. Once the media device is allocated by a driver, other > drivers can get a

Re: [PATCH v4 6/7] ARM: dts: exynos: convert MFC device to generic reserved memory bindings

Hello Marek, On 05/27/2016 07:32 AM, Marek Szyprowski wrote: > Hello, > > > On 2016-05-25 19:11, Javier Martinez Canillas wrote: >> Hello Marek, >> >> On 05/24/2016 09:31 AM, Marek Szyprowski wrote: >>> This patch replaces custom properties for defining reserved memory >>> regions with generic

[PATCHv5] support for AD5820 camera auto-focus coil

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone. Signed-off-by: Pavel Machek --- v2: simple cleanups, fix error paths, simplify probe v3: more cleanups, remove printk, add include v4: remove header file. v5: switch to devm_ , style

Re: [PATCH v2 1/2] media: Media Device Allocator API

On 05/27/2016 07:26 AM, Hans Verkuil wrote: > On 05/25/2016 01:39 AM, Shuah Khan wrote: >> Media Device Allocator API to allows multiple drivers share a media device. >> Using this API, drivers can allocate a media device with the shared struct >> device as the key. Once the media device is

Re: [PATCH v4 2/7] media: s5p-mfc: use generic reserved memory bindings

Hello Marek, On 05/27/2016 02:37 AM, Marek Szyprowski wrote: > Hello, > > > On 2016-05-25 19:36, Rob Herring wrote: >> On Wed, May 25, 2016 at 11:18:59AM -0400, Javier Martinez Canillas wrote: >>> Hello Marek, >>> >>> On 05/24/2016 09:31 AM, Marek Szyprowski wrote: Use generic reserved

Re: [PATCHv4] support for AD5820 camera auto-focus coil

Hi! > > + * Contact: Tuukka Toivonen > > + * Sakari Ailus > > Could you put the e-mail addresses back, please? > > Tuukka's e-mail is tuukkat76 at gmail.com . Ok. > > +#include > > +#include > > +#include > > +#include > > +#include > > Alphabetical order would be nice. The

[PATCH v3] media: Media Device Allocator API

Media Device Allocator API to allows multiple drivers share a media device. Using this API, drivers can allocate a media device with the shared struct device as the key. Once the media device is allocated by a driver, other drivers can get a reference to it. The media device is released when all

multi-sensor media controller

Hi, Can someone give me a quick sanity check on a media controller set up? We have have devices (well, phones) that can have 2 or more sensors and 2 or more 'front end' ISPs. The ISPs take CSI input from a sensor, and can produce Bayer and YUV output to memory. There is a bridge between the

Re: [PATCH 8/8] [media] rcar-vin: add Gen2 and Gen3 fallback compatibility strings

Hello. On 05/27/2016 02:36 PM, Niklas Söderlund wrote: From: Niklas Söderlund These are present in the soc-camera version of this driver and it's time to add them to this driver as well. Signed-off-by: Niklas Söderlund

Re: [PATCH 1/4] fcp: Extend FCP compatible list to support the FDP

My apologies - I had a stale file in my patches folder :( This one had the wrong commit-shortlog, please ignore. -- Kieran On 27/05/16 18:19, Kieran Bingham wrote: > The FCP must be powered up for the FDP1 to function, even when the FDP1 > does not make use of the FCNL features. Extend the

[PATCH 1/4] v4l: Extend FCP compatible list to support the FDP

The FCP must be powered up for the FDP1 to function, even when the FDP1 does not make use of the FCNL features. Extend the compatible list to allow us to use the power domain and runtime-pm support. Signed-off-by: Kieran Bingham --- drivers/media/platform/rcar-fcp.c | 1 + 1

[PATCH 1/4] fcp: Extend FCP compatible list to support the FDP

The FCP must be powered up for the FDP1 to function, even when the FDP1 does not make use of the FCNL features. Extend the compatible list to allow us to use the power domain and runtime-pm support. Signed-off-by: Kieran Bingham --- drivers/media/platform/rcar-fcp.c | 1 + 1

[PATCH 2/4] dt-bindings: Update Renesas R-Car FCP DT binding

The FCP driver, can also support the FCPF variant for FDP1 compatible processing. Signed-off-by: Kieran Bingham --- Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) Cc: devicet...@vger.kernel.org diff --git

[PATCH 3/4] dt-bindings: Document Renesas R-Car FCP power-domains usage

The example misses the power-domains usage, and documentation that the property is used by the node. Signed-off-by: Kieran Bingham --- Documentation/devicetree/bindings/media/renesas,fcp.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH 4/4] arm64: dts: r8a7795: add FCPF device nodes

Provide nodes for the FCP devices dedicated to the FDP device channels. Signed-off-by: Kieran Bingham --- arch/arm64/boot/dts/renesas/r8a7795.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi

[PATCH 0/4] RCar r8a7795 FCPF support

An RCar FCP driver is available with support for the FCPV module for VSP. This series updates that driver to support the FCPF and then provide the relevant nodes in the r8a7795 device tree. Checkpatch generates a warning on these DT references but they are documented under

[PATCH v3 1/2] [media] media: i2c/ov5645: add the device tree binding document

Add the document for ov5645 device tree binding. Signed-off-by: Todor Tomov --- .../devicetree/bindings/media/i2c/ov5645.txt | 50 ++ 1 file changed, 50 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5645.txt

[PATCH v3 2/2] media: Add a driver for the ov5645 camera sensor.

The ov5645 sensor from Omnivision supports up to 2592x1944 and CSI2 interface. The driver adds support for the following modes: - 1280x960 - 1920x1080 - 2592x1944 Output format is packed 8bit UYVY. Signed-off-by: Todor Tomov --- drivers/media/i2c/Kconfig | 12 +

[PATCH v3 0/2] OV5645 camera sensor driver

This is the third version of the OV5645 camera sensor driver patchset. Changes from version 2 include: - external camera clock configuration is moved from DT to driver; - pwdn-gpios renamed to enable-gpios; - switched polarity of reset-gpios to the more intuitive active low; - added Kconfig

Re: [PATCH v2 2/8] [media] Add signed 16-bit pixel format

On 27/05/2016 14:18, Hans Verkuil wrote: > On 05/27/2016 02:52 PM, Nick Dyer wrote: >> On 27/05/2016 13:38, Hans Verkuil wrote: >>> On 05/04/2016 07:07 PM, Nick Dyer wrote: +V4L2_PIX_FMT_YS16 +Grey-scale image + + +Description + +This is a

Re: [PATCH v2 1/2] media: Media Device Allocator API

On 05/25/2016 01:39 AM, Shuah Khan wrote: > Media Device Allocator API to allows multiple drivers share a media device. > Using this API, drivers can allocate a media device with the shared struct > device as the key. Once the media device is allocated by a driver, other > drivers can get a

Re: [PATCH v2 2/8] [media] Add signed 16-bit pixel format

On 05/27/2016 02:52 PM, Nick Dyer wrote: > On 27/05/2016 13:38, Hans Verkuil wrote: >> On 05/04/2016 07:07 PM, Nick Dyer wrote: >>> +V4L2_PIX_FMT_YS16 >>> +Grey-scale image >>> + >>> + >>> +Description >>> + >>> +This is a signed grey-scale image with a depth of 16 bits per >>>

Re: [PATCH v2 8/8] Input: atmel_mxt_ts - add support for reference data

On 05/04/2016 07:07 PM, Nick Dyer wrote: > There are different datatypes available from a maXTouch chip. Add > support to retrieve reference data as well. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/atmel_mxt_ts.c | 66 >

Re: [PATCH v2 4/8] Input: atmel_mxt_ts - output diagnostic debug via v4l2 device

Hi Nick, On 05/04/2016 07:07 PM, Nick Dyer wrote: > Register a video device to output T37 diagnostic data. > > Signed-off-by: Nick Dyer > --- > drivers/input/touchscreen/Kconfig| 2 + > drivers/input/touchscreen/atmel_mxt_ts.c | 271 >

Re: [PATCH v2 2/8] [media] Add signed 16-bit pixel format

On 27/05/2016 13:38, Hans Verkuil wrote: > On 05/04/2016 07:07 PM, Nick Dyer wrote: >> +V4L2_PIX_FMT_YS16 >> +Grey-scale image >> + >> + >> +Description >> + >> +This is a signed grey-scale image with a depth of 16 bits per >> +pixel. The most significant byte is stored at

[PATCH 4/6] media: Add 1X14 14-bit raw bayer media bus code definitions

From: Jouni Ukkonen The codes will be called: MEDIA_BUS_FMT_SBGGR14_1X14 MEDIA_BUS_FMT_SGBRG14_1X14 MEDIA_BUS_FMT_SGRBG14_1X14 MEDIA_BUS_FMT_SRGGB14_1X14 Signed-off-by: Jouni Ukkonen Signed-off-by: Sakari Ailus

[PATCH 1/6] v4l: Correct the ordering of LSBs of the 10-bit raw packed formats

The 10-bit packed raw bayer format documented that the data of the first pixel of a four-pixel group was found in the first byte and the two highest bits of the fifth byte. This was not entirely correct. The two bits in the fifth byte are the two lowest bits. The second pixel occupies the second

[PATCH 0/6] New raw bayer format definitions, fixes

Hi, These patches fix and add new raw bayer format definitions. 12-bit packed V4L2 format definition is added as well as definitions of 14-bit media bus codes as well as unpacked and packed V4L2 formats. No driver uses them right now, yet they're common formats needed by newer devices that use

[PATCH 6/6] v4l: Add packed Bayer raw14 pixel formats

These formats are compressed 14-bit raw bayer formats with four different pixel orders. They are similar to 10-bit variants. The formats added by this patch are V4L2_PIX_FMT_SBGGR14P V4L2_PIX_FMT_SGBRG14P V4L2_PIX_FMT_SGRBG14P V4L2_PIX_FMT_SRGGB14P Signed-off-by:

[PATCH 2/6] v4l: Fix number of zeroed high order bits in 12-bit raw format defs

The number of high order bits in samples was documented to be 6 for 12-bit data. This is clearly wrong, fix it. Signed-off-by: Sakari Ailus --- Documentation/DocBook/media/v4l/pixfmt-srggb12.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 5/6] v4l: Add 14-bit raw bayer pixel format definitions

The formats added by this patch are: V4L2_PIX_FMT_SBGGR14 V4L2_PIX_FMT_SGBRG14 V4L2_PIX_FMT_SGRBG14 V4L2_PIX_FMT_SRGGB14 Signed-off-by: Jouni Ukkonen Signed-off-by: Sakari Ailus ---

[PATCH 3/6] v4l: Add packed Bayer raw12 pixel formats

These formats are compressed 12-bit raw bayer formats with four different pixel orders. They are similar to 10-bit variants. The formats added by this patch are V4L2_PIX_FMT_SBGGR12P V4L2_PIX_FMT_SGBRG12P V4L2_PIX_FMT_SGRBG12P V4L2_PIX_FMT_SRGGB12P Signed-off-by:

Re: [PATCH v2 2/8] [media] Add signed 16-bit pixel format

On 05/04/2016 07:07 PM, Nick Dyer wrote: > This will be used for output of raw touch data. > > Signed-off-by: Nick Dyer > --- > Documentation/DocBook/media/v4l/pixfmt-ys16.xml | 79 > + > Documentation/DocBook/media/v4l/pixfmt.xml | 1 + >

Re: [PATCH v2 2/2] media: Add a driver for the ov5645 camera sensor.

Hi Stan, Thanks for the review. On 05/20/2016 06:20 PM, Stanimir Varbanov wrote: > Hi Todor, > > Thanks for the patch, few comments below. > > On 05/18/2016 02:50 PM, Todor Tomov wrote: >> The ov5645 sensor from Omnivision supports up to 2592x1944 >> and CSI2 interface. >> >> The driver adds

Re: [PATCH 8/8] [media] rcar-vin: add Gen2 and Gen3 fallback compatibility strings

Hi Sergei, On 2016-05-25 22:36:02 +0300, Sergei Shtylyov wrote: > On 05/25/2016 10:10 PM, Niklas Söderlund wrote: > > > From: Niklas Söderlund > > > > These are present in the soc-camera version of this driver and it's time > > to add them to this driver

Re: [PATCH v4 6/7] ARM: dts: exynos: convert MFC device to generic reserved memory bindings

Hello, On 2016-05-25 19:11, Javier Martinez Canillas wrote: Hello Marek, On 05/24/2016 09:31 AM, Marek Szyprowski wrote: This patch replaces custom properties for defining reserved memory regions with generic reserved memory bindings for MFC video codec device. Signed-off-by: Marek

[GIT PULL FOR v4.7] Two regression fixes for 4.7.

Mauro, These are two regression fixes for 4.7. The adv7604 patch is also for 4.6. Regards, Hans The following changes since commit 4ddd4fd497da1dfd99aa197eaca053d1b3da8eaf: Merge tag 'v4.6' into patchwork (2016-05-18 06:29:23 -0300) are available in the git repository at:

Re: RFC: HSV format

On 05/24/2016 11:19 PM, Ricardo Ribalda Delgado wrote: > Hi > > HSV is a cylindrical-coordinate representation of a color. It is very > useful for computer vision because the Hue component can be used to > segment a scene. > > My plan was to add a format in videodev2.h and then add support for

Re: [PATCH v4 2/7] media: s5p-mfc: use generic reserved memory bindings

Hello, On 2016-05-25 19:36, Rob Herring wrote: On Wed, May 25, 2016 at 11:18:59AM -0400, Javier Martinez Canillas wrote: Hello Marek, On 05/24/2016 09:31 AM, Marek Szyprowski wrote: Use generic reserved memory bindings and mark old, custom properties as obsoleted. Signed-off-by: Marek

Re: [PATCH v4 2/7] media: s5p-mfc: use generic reserved memory bindings

On 05/24/2016 03:31 PM, Marek Szyprowski wrote: > Use generic reserved memory bindings and mark old, custom properties > as obsoleted. > > Signed-off-by: Marek Szyprowski > --- > .../devicetree/bindings/media/s5p-mfc.txt | 39 > +- > 1