cron job: media_tree daily build: OK

2016-05-15 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:   Mon May 16 04:00:22 CEST 2016
git branch: test
git hash:   d1532d5575696965a52b19553dd7dacf75f3fec5
gcc version:i686-linux-gcc (GCC) 5.3.0
sparse version: v0.5.0-56-g7647c77
smatch version: v0.5.0-3428-gdfe27cf
host hardware:  x86_64
host os:4.5.0-164

linux-git-arm-at91: OK
linux-git-arm-davinci: OK
linux-git-arm-exynos: OK
linux-git-arm-mx: OK
linux-git-arm-omap: OK
linux-git-arm-omap1: OK
linux-git-arm-pxa: OK
linux-git-blackfin-bf561: OK
linux-git-i686: OK
linux-git-m32r: OK
linux-git-mips: OK
linux-git-powerpc64: OK
linux-git-sh: OK
linux-git-x86_64: OK
linux-2.6.36.4-i686: OK
linux-2.6.37.6-i686: OK
linux-2.6.38.8-i686: OK
linux-2.6.39.4-i686: OK
linux-3.0.60-i686: OK
linux-3.1.10-i686: OK
linux-3.2.37-i686: OK
linux-3.3.8-i686: OK
linux-3.4.27-i686: OK
linux-3.5.7-i686: OK
linux-3.6.11-i686: OK
linux-3.7.4-i686: OK
linux-3.8-i686: OK
linux-3.9.2-i686: OK
linux-3.10.1-i686: OK
linux-3.11.1-i686: OK
linux-3.12.23-i686: OK
linux-3.13.11-i686: OK
linux-3.14.9-i686: OK
linux-3.15.2-i686: OK
linux-3.16.7-i686: OK
linux-3.17.8-i686: OK
linux-3.18.7-i686: OK
linux-3.19-i686: OK
linux-4.0-i686: OK
linux-4.1.1-i686: OK
linux-4.2-i686: OK
linux-4.3-i686: OK
linux-4.4-i686: OK
linux-4.5-i686: OK
linux-4.6-rc1-i686: OK
linux-2.6.36.4-x86_64: OK
linux-2.6.37.6-x86_64: OK
linux-2.6.38.8-x86_64: OK
linux-2.6.39.4-x86_64: OK
linux-3.0.60-x86_64: OK
linux-3.1.10-x86_64: OK
linux-3.2.37-x86_64: OK
linux-3.3.8-x86_64: OK
linux-3.4.27-x86_64: OK
linux-3.5.7-x86_64: OK
linux-3.6.11-x86_64: OK
linux-3.7.4-x86_64: OK
linux-3.8-x86_64: OK
linux-3.9.2-x86_64: OK
linux-3.10.1-x86_64: OK
linux-3.11.1-x86_64: OK
linux-3.12.23-x86_64: OK
linux-3.13.11-x86_64: OK
linux-3.14.9-x86_64: OK
linux-3.15.2-x86_64: OK
linux-3.16.7-x86_64: OK
linux-3.17.8-x86_64: OK
linux-3.18.7-x86_64: OK
linux-3.19-x86_64: OK
linux-4.0-x86_64: OK
linux-4.1.1-x86_64: OK
linux-4.2-x86_64: OK
linux-4.3-x86_64: OK
linux-4.4-x86_64: OK
linux-4.5-x86_64: OK
linux-4.6-rc1-x86_64: OK
apps: OK
spec-git: OK
sparse: WARNINGS
smatch: WARNINGS

Detailed results are available here:

http://www.xs4all.nl/~hverkuil/logs/Monday.log

Full logs are available here:

http://www.xs4all.nl/~hverkuil/logs/Monday.tar.bz2

The Media Infrastructure API from this daily build is here:

http://www.xs4all.nl/~hverkuil/spec/media.html
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [GIT PULL FOR v4.7] Renesas VSP updates

2016-05-15 Thread Laurent Pinchart 
Hi Mauro,

I've found a small issue in one of the patches. As you don't plan to apply the 
series to v4.7 anyway I'll fix the problem and send a new pull request.

Another issue I wanted to mention is that the two rcar-du patches will very 
likely conflict with patches merged through Dave's tree for v4.8 (be accurate 
with the generic zpos property series posted by Benjamin Gaignard). Dave, one 
way to handle this would be for Mauro to merge this series very early in his 
tree (as soon as possible after the v4.6 release) and provide you with a 
stable branch to pull in your tree, on top of which Benjamin would have to 
rebase his series (the conflict will be easy to solve). Would that work for 
everybody ?

On Wednesday 11 May 2016 16:23:01 Laurent Pinchart wrote:
> Hi Mauro,
> 
> The following changes since commit aff093d4bbca91f543e24cde2135f393b8130f4b:
> 
>   [media] exynos-gsc: avoid build warning without CONFIG_OF (2016-05-09
> 18:38:33 -0300)
> 
> are available in the git repository at:
> 
>   git://linuxtv.org/pinchartl/media.git vsp1/next
> 
> for you to fetch changes up to 01986b08a08353a23bc89a588a14966cb0a09e0d:
> 
>   v4l: vsp1: Remove deprecated DRM API (2016-05-11 16:07:44 +0300)
> 
> Please note that the pull request includes two patches for the rcar-du-drm
> driver. They depend on previous patches for the vsp1 driver in the same
> series, and the last vsp1 patch depends on them. For this reason I'm
> submitting everything in a single pull request to you, with Dave's ack to
> get the rcar-du-drm patches merged through your tree. They shouldn't
> conflict with anything queued in Dave's tree for v4.7.
> 
> 
> Laurent Pinchart (13):
>   dt-bindings: Add Renesas R-Car FCP DT bindings
>   v4l: Add Renesas R-Car FCP driver
>   v4l: vsp1: Implement runtime PM support
>   v4l: vsp1: Don't handle clocks manually
>   v4l: vsp1: Add FCP support
>   v4l: vsp1: Add output node value to routing table
>   v4l: vsp1: Replace container_of() with dedicated macro
>   v4l: vsp1: Make vsp1_entity_get_pad_compose() more generic
>   v4l: vsp1: Move frame sequence number from video node to pipeline
>   v4l: vsp1: Group DRM RPF parameters in a structure
>   drm: rcar-du: Add alpha support for VSP planes
>   drm: rcar-du: Add Z-order support for VSP planes
>   v4l: vsp1: Remove deprecated DRM API
> 
>  Documentation/devicetree/bindings/media/renesas,fcp.txt |  32 +
>  .../devicetree/bindings/media/renesas,vsp1.txt  |   5 +
>  MAINTAINERS |  10 ++
>  drivers/gpu/drm/rcar-du/rcar_du_vsp.c   |  45 +++---
>  drivers/gpu/drm/rcar-du/rcar_du_vsp.h   |   2 +
>  drivers/media/platform/Kconfig  |  14 ++
>  drivers/media/platform/Makefile |   1 +
>  drivers/media/platform/rcar-fcp.c   | 181 +
>  drivers/media/platform/vsp1/vsp1.h  |   6 +-
>  drivers/media/platform/vsp1/vsp1_drm.c  |  68 -
>  drivers/media/platform/vsp1/vsp1_drv.c  | 120 +
>  drivers/media/platform/vsp1/vsp1_entity.c   |  88 
>  drivers/media/platform/vsp1/vsp1_entity.h   |  12 +-
>  drivers/media/platform/vsp1/vsp1_pipe.c |   4 +-
>  drivers/media/platform/vsp1/vsp1_pipe.h |   2 +
>  drivers/media/platform/vsp1/vsp1_rpf.c  |   7 +-
>  drivers/media/platform/vsp1/vsp1_video.c|   4 +-
>  drivers/media/platform/vsp1/vsp1_video.h|   1 -
>  include/media/rcar-fcp.h|  37 +
>  include/media/vsp1.h|  29 ++--
>  20 files changed, 497 insertions(+), 171 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/media/renesas,fcp.txt
>  create mode 100644 drivers/media/platform/rcar-fcp.c
>  create mode 100644 include/media/rcar-fcp.h

-- 
Regards,

Laurent Pinchart

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi

2016-05-15 Thread Robert Makusha 

-- 
We are in need of urgent assistance to transfer and invest our family fortune.

Please download the attachment for the proposal.

Thank you!

Mr Robert and Mrs Rosemary Makusha
(For the Family)

ROBERT.pdf
Description: Adobe PDF document

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

2016-05-15 Thread Stanimir Varbanov 
Hi Todor,

On 05/12/2016 05:59 PM, Todor Tomov wrote:
> 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 
> ---
>  .../devicetree/bindings/media/i2c/ov5645.txt   |   54 +
>  drivers/media/i2c/Kconfig  |   11 +
>  drivers/media/i2c/Makefile |1 +
>  drivers/media/i2c/ov5645.c | 1344 
> 
>  4 files changed, 1410 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5645.txt
>  create mode 100644 drivers/media/i2c/ov5645.c
> 
> diff --git a/Documentation/devicetree/bindings/media/i2c/ov5645.txt 
> b/Documentation/devicetree/bindings/media/i2c/ov5645.txt
> new file mode 100644
> index 000..1d65fa8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ov5645.txt

The binding doc should be a separate patch. Also you should add
devicetree ML in cc.

> @@ -0,0 +1,54 @@
> +* Omnivision 1/4-Inch 5Mp CMOS Digital Image Sensor
> +
> +The Omnivision OV5645 is a 1/4-Inch CMOS active pixel digital image sensor 
> with
> +an active array size of 2592H x 1944V. It is programmable through a serial 
> SCCB
> +interface.
> +
> +Required Properties:
> +- compatible: value should be "ovti,ov5645"
> +- clocks: reference to the xclk clock
> +- clock-names: should be "xclk"
> +- clock-rates: the xclk clock frequency
> +
> +Optional Properties:
> +- reset-gpio: Chip reset GPIO
> +- pwdn-gpio: Chip power down GPIO
> +- DOVDD-supply: Chip IO regulator
> +- DVDD-supply: Chip core regulator
> +- AVDD-supply: Chip analog regulator

I'd use lower-case for the -supply properties



> diff --git a/drivers/media/i2c/ov5645.c b/drivers/media/i2c/ov5645.c
> new file mode 100644
> index 000..bae07e4
> --- /dev/null
> +++ b/drivers/media/i2c/ov5645.c
> @@ -0,0 +1,1344 @@
> +/*
> + * Driver for the OV5645 camera sensor.
> + *
> + * Copyright (c) 2011-2015, The Linux Foundation. All rights reserved.
> + * Copyright (C) 2015 By Tech Design S.L. All Rights Reserved.
> + * Copyright (C) 2012-2013 Freescale Semiconductor, Inc. All Rights Reserved.
> + *
> + * Based on:
> + * - the OV5645 driver from QC msm-3.10 kernel on codeaurora.org:
> + *   https://us.codeaurora.org/cgit/quic/la/kernel/msm-3.10/tree/drivers/
> + *   media/platform/msm/camera_v2/sensor/ov5645.c?h=LA.BR.1.2.4_rb1.41
> + * - the OV5640 driver posted on linux-media:
> + *   https://www.mail-archive.com/linux-media%40vger.kernel.org/msg92671.html
> + */
> +
> +/*
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> +
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> + * GNU General Public License for more details.
> + */
> +
> +#include 
> +#include 
> +#include 
> +#include 

do you need ctype.h really ?

> +#include 
> +#include 
> +#include 
> +#include 
> +#include 
> +#include 
> +#include 
> +#include 
> +#include 
> +#include 
> +#include 

those two includes are useless.

> +#include 
> +#include 
> +#include 
> +
> +#define OV5645_VOLTAGE_ANALOG   280
> +#define OV5645_VOLTAGE_DIGITAL_CORE 150
> +#define OV5645_VOLTAGE_DIGITAL_IO   180
> +
> +#define OV5645_XCLK_MIN 600
> +#define OV5645_XCLK_MAX 2400
> +
> +#define OV5645_SYSTEM_CTRL0  0x3008
> +#define  OV5645_SYSTEM_CTRL0_START   0x02
> +#define  OV5645_SYSTEM_CTRL0_STOP0x42
> +#define OV5645_CHIP_ID_HIGH_REG  0x300A
> +#define  OV5645_CHIP_ID_HIGH 0x56
> +#define OV5645_CHIP_ID_LOW_REG   0x300B
> +#define  OV5645_CHIP_ID_LOW  0x45
> +#define OV5645_AWB_MANUAL_CONTROL0x3406
> +#define  OV5645_AWB_MANUAL_ENABLE(1 << 0)

use BIT(x) here and below for bit operations

> +#define OV5645_AEC_PK_MANUAL 0x3503
> +#define  OV5645_AEC_MANUAL_ENABLE(1 << 0)
> +#define  OV5645_AGC_MANUAL_ENABLE(1 << 1)
> +#define OV5645_TIMING_TC_REG20   0x3820
> +#define  OV5645_SENSOR_VFLIP (1 << 1)
> +#define  OV5645_ISP_VFLIP(1 << 2)
> +#define OV5645_TIMING_TC_REG21   0x3821
> +#define  OV5645_SENSOR_MIRROR(1 << 1)
> +#define OV5645_PRE_ISP_TEST_SETTING_10x503d
> +#define  OV5645_TEST_PATTERN_MASK0x3
> +#define  OV5645_SET_TEST_PATTERN(x)

Re: gstreamer: v4l2videodec plugin

2016-05-15 Thread Nicolas Dufresne 
Le vendredi 13 mai 2016 à 11:45 +0300, Stanimir Varbanov a écrit :
> One thing which bothers me is how the extra-controls property
> working,
> i.e. I failed to change the h264 profile for example with below
> construct:
> 
> extra-controls="controls,h264_profile=4;"

Yes, and profile should be negotiated with downstream in GStreamer. For
common controls, like bitrate, it should be exposed as separate
properties instead.

Nicolas

signature.asc
Description: This is a digitally signed message part