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: Sat Jul 22 05:00:21 CEST 2017 media-tree git hash:0e50e84a11f4854e9a7e3b7f4443ffb99e6be292 media_build

Re: [PATCH v2 4/6] [media] rc: pwm-ir-tx: add new driver

Hi Sean, sorry for double-post, forgot to CC the list and others. On Fri, Jul 07, 2017 at 10:52:02AM +0100, Sean Young wrote: > This is new driver which uses pwm, so it is more power-efficient > than the bit banging gpio-ir-tx driver. > > Signed-off-by: Sean Young Tested-by:

Re: [GIT PULL] SAA716x DVB driver

Hi Mauro, On 20.07.2017 07:49:36 -0300, Mauro Carvalho Chehab wrote: >Hi Soeren, > >Em Sun, 16 Jul 2017 20:34:23 +0200 >Soeren Moch escreveu: > >> This is a driver for DVB cards based on the SAA7160/62 PCIe bridges from >> Philips/NXP. The most important of these cards, at least

Re: [PATCH v2 3/6] [media] rc: gpio-ir-tx: add new driver

Hi Sean, On Fri, Jul 21, 2017 at 04:12:45PM +0200, Matthias Reichl wrote: > Hi Sean, > > On Fri, Jul 07, 2017 at 10:51:59AM +0100, Sean Young wrote: > > This is a simple bit-banging GPIO IR TX driver. > > thanks a lot for the driver, this is highly appreciated! > > I tested the patch series on

[PATCH v2] media: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Acked-by: Niklas Söderlund Acked-by:

Re: [PATCHv2 5/5] media-device: remove driver_version

Hi Hans, Thank you for the patch. On Friday 21 Jul 2017 12:57:06 Hans Verkuil wrote: > From: Hans Verkuil > > Since the driver_version field in struct media_device is no longer > used, just remove it. > > Signed-off-by: Hans Verkuil

Re: [PATCHv2 1/5] media-device: set driver_version directly

Hi Hans, Thank you for the patch. On Friday 21 Jul 2017 12:57:02 Hans Verkuil wrote: > From: Hans Verkuil > > Don't use driver_version from struct media_device, just return > LINUX_VERSION_CODE as the other media subsystems do. > > The driver_version field in struct

Re: [PATCHv2 1/5] media-device: set driver_version directly

Hi Hans, On Friday 21 Jul 2017 13:06:38 Hans Verkuil wrote: > On 21/07/17 12:57, Hans Verkuil wrote: > > From: Hans Verkuil > > > > Don't use driver_version from struct media_device, just return > > LINUX_VERSION_CODE as the other media subsystems do. > > > > The

Re: [PATCH v4] uvcvideo: add a metadata device node

Hi Guennadi, Thank you for the patch. > Some UVC video cameras contain metadata in their payload headers. This > patch extracts that data, adding more clock synchronisation information, > on both bulk and isochronous endpoints and makes it available to the > user space on a separate video node,

Re: [PATCH] dvb_frontend: initialize variable s with FE_NONE instead of 0

On 21/07/17 19:05, Shuah Khan wrote: > On 07/21/2017 10:01 AM, Colin King wrote: >> From: Colin Ian King >> >> In a previous commit, we added FE_NONE as an unknown fe_status. >> Initialize variable s to FE_NONE instead of the more opaque value 0. >> >> Signed-off-by:

Re: [PATCH] dvb_frontend: initialize variable s with FE_NONE instead of 0

On 07/21/2017 10:01 AM, Colin King wrote: > From: Colin Ian King > > In a previous commit, we added FE_NONE as an unknown fe_status. > Initialize variable s to FE_NONE instead of the more opaque value 0. > > Signed-off-by: Colin Ian King The

[PATCH] dma-buf: fix reservation_object_wait_timeout_rcu to wait correctly

From: Christian König With hardware resets in mind it is possible that all shared fences are signaled, but the exlusive isn't. Fix waiting for everything in this situation. Signed-off-by: Christian König --- drivers/dma-buf/reservation.c | 2

[PATCH] [media] imx: add VIDEO_V4L2_SUBDEV_API dependency

Without this, I get a build error: drivers/staging/media/imx/imx-media-vdic.c: In function '__vdic_get_fmt': drivers/staging/media/imx/imx-media-vdic.c:554:10: error: implicit declaration of function 'v4l2_subdev_get_try_format'; did you mean 'v4l2_subdev_notify_event'?

[PATCH] [media] v4l: omap_vout: vrfb: include linux/slab.h

Without this header, we get a build error in some configurations: drivers/media/platform/omap/omap_vout_vrfb.c: In function 'omap_vout_setup_vrfb_bufs': drivers/media/platform/omap/omap_vout_vrfb.c:143:26: error: implicit declaration of function 'kzalloc'; did you mean 'vzalloc'?

[PATCH] [media] docs-next: update the fe_status documentation for FE_NONE

From: Colin Ian King Recently added FE_NONE to the enum fe_status, so update the documentation accordingly. Signed-off-by: Colin Ian King --- Documentation/media/uapi/dvb/fe-read-status.rst | 20 ++-- 1 file changed, 14

Re: linux-next: Tree for Jul 21 (drivers/media: use of __WARN())

On 07/20/2017 09:10 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20170720: > on x86_64: when CONFIG_BUG is not enabled: ../drivers/media/platform/pxa_camera.c:642:3: error: implicit declaration of function ‘__WARN’ [-Werror=implicit-function-declaration]

[PATCH] dvb_frontend: initialize variable s with FE_NONE instead of 0

From: Colin Ian King In a previous commit, we added FE_NONE as an unknown fe_status. Initialize variable s to FE_NONE instead of the more opaque value 0. Signed-off-by: Colin Ian King --- drivers/media/dvb-core/dvb_frontend.c | 2 +- 1 file

[PATCH v1 2/2] [media] ov9655: fix missing mutex_destroy()

Fix missing mutex_destroy() when probe fails and when driver is removed. Signed-off-by: Hugues Fruchet --- drivers/media/i2c/ov9650.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/media/i2c/ov9650.c b/drivers/media/i2c/ov9650.c index

[PATCH v1 0/2] OV9650 code cleanup

Here is a bunch of small fixes found when upstreaming the OV9655 sensor driver based on OV9650 driver: - Fix coding style (checkpatch --strict) - Fix missing mutex_destroy, see http://www.mail-archive.com/linux-media@vger.kernel.org/msg115245.html Hugues Fruchet (2): [media] ov9650: fix coding

[PATCH v1 1/2] [media] ov9650: fix coding style

Fix a bunch of coding style issues detected by checkpatch --strict. Signed-off-by: Hugues Fruchet --- drivers/media/i2c/ov9650.c | 59 ++ 1 file changed, 33 insertions(+), 26 deletions(-) diff --git a/drivers/media/i2c/ov9650.c

Re: [PATCH] Revert "[media] v4l: async: make v4l2 coexist with devicetree nodes in a dt overlay"

Hi Rob, On Thu, Jul 20, 2017 at 05:06:22PM -0500, Rob Herring wrote: > This reverts commit d2180e0cf77dc7a7049671d5d57dfa0a228f83c1. > > The commit was flawed in that if the device_node pointers are different, > then in fact a different device is present and the device node could be > different

[GIT FIXES for 4.13] More atomisp fixes

Hi Mauro, A few more atomisp fixes here. Please pull. The following changes since commit 6538b02d210f52ef2a2e67d59fcb58be98451fbd: media: Make parameter of media_entity_remote_pad() const (2017-07-20 16:54:04 -0400) are available in the git repository at:

[GIT PULL for 4.14] V4L2 flash class and misc patches

Hi Mauro, More patches for 4.14. Flash fixes and improvements plus other miscellaneous patches. Please pull. The following changes since commit 6538b02d210f52ef2a2e67d59fcb58be98451fbd: media: Make parameter of media_entity_remote_pad() const (2017-07-20 16:54:04 -0400) are available in

Re: [PATCH v2 3/6] [media] rc: gpio-ir-tx: add new driver

Hi Sean, On Fri, Jul 07, 2017 at 10:51:59AM +0100, Sean Young wrote: > This is a simple bit-banging GPIO IR TX driver. thanks a lot for the driver, this is highly appreciated! I tested the patch series on a RPi2, against RPi downstream kernel 4.13-rc1, and noticed an issue: the polarity of the

WARNING from linux/drivers/media/v4l2-core/v4l2-ioctl.c: Unknown pixelformat 0x20203852

Deal all, My v4l2 capture driver advertises some non-v4l2 pixel formats and in new kernels I get a warning message to kernel logs when VIDIOC_ENUM_FMT ioctl is called in the driver: [11205.998032] WARNING: CPU: 5 PID: 2471 at /home/kernel/COD/linux/drivers/media/v4l2-core/v4l2-ioctl.c:1272

[GIT PULL FOR 4.14] Samsung SoC related updates

Hi Mauro, The following changes since commit 6538b02d210f52ef2a2e67d59fcb58be98451fbd: media: Make parameter of media_entity_remote_pad() const (2017-07-20 16:54:04 -0400) are available in the git repository at: git://linuxtv.org/snawrocki/samsung.git for-v4.14/media/next for you to

Re: [PATCH 3/8] dt: bindings: Add a binding for referencing EEPROM from camera sensors

Hi Maxime, On Wed, Jul 19, 2017 at 01:18:43PM +0200, Maxime Ripard wrote: > Hi Sakari, > > On Wed, Jul 19, 2017 at 12:21:06PM +0300, Sakari Ailus wrote: > > On Wed, Jul 19, 2017 at 09:52:55AM +0200, Maxime Ripard wrote: > > > Hi Sakari, > > > > > > On Wed, Jun 14, 2017 at 12:47:14PM +0300,

Re: [PATCHv2 1/5] media-device: set driver_version directly

On 21/07/17 12:57, Hans Verkuil wrote: > From: Hans Verkuil > > Don't use driver_version from struct media_device, just return > LINUX_VERSION_CODE as the other media subsystems do. > > The driver_version field in struct media_device will be removed > in the following

[PATCH][media-next] media: dvb-frontends/stv0910: make various local variables static

From: Colin Ian King The list stvlist and arrays padc_lookup, s1_sn_lookup and s2_sn_lookup do not need to be in global scope, so make them all static. Cleans up a bunch of smatch warnings: symbol 'padc_lookup' was not declared. Should it be static? symbol

[PATCHv2 5/5] media-device: remove driver_version

From: Hans Verkuil Since the driver_version field in struct media_device is no longer used, just remove it. Signed-off-by: Hans Verkuil --- drivers/media/media-device.c | 3 --- include/media/media-device.h | 2 -- 2 files changed, 5

[PATCHv2 4/5] atomisp2: don't set driver_version

From: Hans Verkuil This field will be removed as it is not needed anymore. Signed-off-by: Hans Verkuil --- drivers/staging/media/atomisp/pci/atomisp2/atomisp_v4l2.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git

[PATCHv2 3/5] uvc: don't set driver_version

From: Hans Verkuil This field will be removed as it is not needed anymore. Signed-off-by: Hans Verkuil Reviewed-by: Laurent Pinchart --- drivers/media/usb/uvc/uvc_driver.c | 1 - 1 file changed, 1 deletion(-)

[PATCHv2 2/5] s3c-camif: don't set driver_version

From: Hans Verkuil This field will be removed as it is not needed anymore. Signed-off-by: Hans Verkuil --- drivers/media/platform/s3c-camif/camif-core.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCHv2 1/5] media-device: set driver_version directly

From: Hans Verkuil Don't use driver_version from struct media_device, just return LINUX_VERSION_CODE as the other media subsystems do. The driver_version field in struct media_device will be removed in the following patches. Signed-off-by: Hans Verkuil

[PATCHv2 0/5] media: drop driver_version from media_device

From: Hans Verkuil Just a little thing that always annoyed me: the driver_version shouldn't be set in drivers. The version number never, ever gets updated in drivers. We saw that in the other media subsystems and now the core always sets it, not drivers. This works much

Re: [PATCH] Revert "[media] v4l: async: make v4l2 coexist with devicetree nodes in a dt overlay"

On Thu, Jul 20, 2017 at 05:06:22PM -0500, Rob Herring wrote: > This reverts commit d2180e0cf77dc7a7049671d5d57dfa0a228f83c1. > > The commit was flawed in that if the device_node pointers are different, > then in fact a different device is present and the device node could be > different in ways

Re: [PATCH 1/4] media-device: set driver_version in media_device_init

On 21/07/17 12:12, Laurent Pinchart wrote: > Hi Hans, > > Thank you for the patch. > > On Friday 21 Jul 2017 11:02:31 Hans Verkuil wrote: >> From: Hans Verkuil >> >> Set the driver_version to LINUX_VERSION_CODE in the media_device_init >> call, just as the other media

Re: [PATCH] v4l: rcar-vin: Simplify rvin_group_notify_{bound,unbind}

Hi Kieran, Thanks for your patch. On 2017-07-21 10:55:50 +0100, Kieran Bingham wrote: > Use a container_of macro to obtain the graph entity object from the ASD > This removes the error conditions, and reduces the lock contention. > > (The locking may even be potentially removed) > >

Re: [PATCH 1/4] media-device: set driver_version in media_device_init

Hi Hans, Thank you for the patch. On Friday 21 Jul 2017 11:02:31 Hans Verkuil wrote: > From: Hans Verkuil > > Set the driver_version to LINUX_VERSION_CODE in the media_device_init > call, just as the other media subsystems do. > > There is no point in doing anything

Re: [PATCH 3/4] uvc: don't set driver_version anymore

Hi Hans, Thank you for the patch. On Friday 21 Jul 2017 11:02:33 Hans Verkuil wrote: > From: Hans Verkuil > > This is now set by media_device_init. > > Signed-off-by: Hans Verkuil Reviewed-by: Laurent Pinchart

Re: [PATCH 4/4] atomisp2: don't set driver_version anymore

Hi Hans, On Friday 21 Jul 2017 11:02:34 Hans Verkuil wrote: > From: Hans Verkuil > > This is now set by media_device_init. > > Drop the print of driver_version in the error message: the driver > version is 1) not yet set at this point (the media_device_init call > comes

[PATCH] v4l: rcar-vin: Simplify rvin_group_notify_{bound,unbind}

Use a container_of macro to obtain the graph entity object from the ASD This removes the error conditions, and reduces the lock contention. (The locking may even be potentially removed) Signed-off-by: Kieran Bingham --- Hi Niklas, While working through

[PATCH 0/4] media: set driver_version in media_device_init

From: Hans Verkuil Just a little thing that always annoyed me: the driver_version should be set in media_device_init, not in the drivers themselves. The version number never, ever gets updated in drivers. We saw that in the other media subsystems and now the core always

[PATCH 2/4] s3c-camif: don't set driver_version anymore

From: Hans Verkuil This is now set by media_device_init. Signed-off-by: Hans Verkuil --- drivers/media/platform/s3c-camif/camif-core.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/media/platform/s3c-camif/camif-core.c

[PATCH 3/4] uvc: don't set driver_version anymore

From: Hans Verkuil This is now set by media_device_init. Signed-off-by: Hans Verkuil --- drivers/media/usb/uvc/uvc_driver.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/media/usb/uvc/uvc_driver.c

[PATCH 4/4] atomisp2: don't set driver_version anymore

From: Hans Verkuil This is now set by media_device_init. Drop the print of driver_version in the error message: the driver version is 1) not yet set at this point (the media_device_init call comes later AFAICS), and 2) irrelevant here, since it is the hw_revision that is

[PATCH 1/4] media-device: set driver_version in media_device_init

From: Hans Verkuil Set the driver_version to LINUX_VERSION_CODE in the media_device_init call, just as the other media subsystems do. There is no point in doing anything else, since version numbers that are set by drivers are never, ever updated. LINUX_VERSION_CODE will

Re: [PATCH v3 22/23] camss: Use optimal clock frequency rates

Hello, On 19.07.2017 18:59, kbuild test robot wrote: > Hi Todor, > > [auto build test ERROR on linuxtv-media/master] > [also build test ERROR on v4.13-rc1] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH v3 00/23] Qualcomm 8x16 Camera Subsystem driver

Hello Sakari, Thank you for the review! On 20.07.2017 18:25, Sakari Ailus wrote: > Hi Todor, > > On Mon, Jul 17, 2017 at 01:33:26PM +0300, Todor Tomov wrote: >> This patchset adds basic support for the Qualcomm Camera Subsystem found >> on Qualcomm MSM8916 and APQ8016 processors. >> >> The

Re: [PATCH v3 00/23] Qualcomm 8x16 Camera Subsystem driver

Hello Hans, On 19.07.2017 13:54, Hans Verkuil wrote: > On 17/07/17 12:33, Todor Tomov wrote: >> This patchset adds basic support for the Qualcomm Camera Subsystem found >> on Qualcomm MSM8916 and APQ8016 processors. >> >> The driver implements V4L2, Media controller and V4L2 subdev interfaces. >>

Re: [RFC 11/19] v4l2-async: Register sub-devices before calling bound callback

On 20/07/17 21:23, Sakari Ailus wrote: > Hi Hans, > > On Thu, Jul 20, 2017 at 06:23:38PM +0200, Hans Verkuil wrote: >> On 20/07/17 18:09, Sakari Ailus wrote: >>> Hi Hans, >>> >>> On Wed, Jul 19, 2017 at 01:24:54PM +0200, Hans Verkuil wrote: On 18/07/17 21:03, Sakari Ailus wrote: > The

Re: [RFC 00/19] Async sub-notifiers and how to use them

Hi Sakari, On 2017-07-20 19:14:01 +0300, Sakari Ailus wrote: > Hi Hans, > > Thanks for the review. > > On Wed, Jul 19, 2017 at 01:42:55PM +0200, Hans Verkuil wrote: > > On 18/07/17 21:03, Sakari Ailus wrote: > > > Hi folks, > > > > > > This RFC patchset achieves a number of things which I've