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 Aug 27 04:00:16 CEST 2016 git branch: test git hash: fb6609280db902bd5d34445fba1c926e95e63914 gcc

[RFC v3 03/21] Revert "[media] media-device: dynamically allocate struct media_devnode"

This reverts commit a087ce704b80 ("[media] media-device: dynamically allocate struct media_devnode"). The commit was part of an original patchset to avoid crashes when an unregistering device is in use. Signed-off-by: Sakari Ailus --- drivers/media/media-device.c

[RFC v3 04/21] media: Remove useless curly braces and parentheses

Signed-off-by: Sakari Ailus Acked-by: Hans Verkuil --- drivers/media/media-device.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/media/media-device.c b/drivers/media/media-device.c index a1cd50f..8bdc316

[RFC v3 00/21] Make use of kref in media device, grab references as needed

Hi folks, This is the third version of the RFC set to fix referencing in media devices. The lifetime of the media device (and media devnode) is now bound to that of struct device embedded in it and its memory is only released once the last reference is gone: unregistering is simply

[RFC v3 02/21] Revert "[media] media: fix use-after-free in cdev_put() when app exits after driver unbind"

This reverts commit 5b28dde51d0c ("[media] media: fix use-after-free in cdev_put() when app exits after driver unbind"). The commit was part of an original patchset to avoid crashes when an unregistering device is in use. Signed-off-by: Sakari Ailus ---

[RFC v3 01/21] Revert "[media] media: fix media devnode ioctl/syscall and unregister race"

This reverts commit 6f0dd24a084a ("[media] media: fix media devnode ioctl/syscall and unregister race"). The commit was part of an original patchset to avoid crashes when an unregistering device is in use. Signed-off-by: Sakari Ailus ---

[RFC v3 09/21] media: Split initialising and adding media devnode

As registering a device node of an entity belonging to a media device will require a reference to the struct device. Taking that reference is only possible once the device has been initialised, which took place only when it was registered. Split this in two, and initialise the device when the

[RFC v3 08/21] media: Enable allocating the media device dynamically

From: Sakari Ailus Allow allocating the media device dynamically. As the struct media_device embeds struct media_devnode, the lifetime of that object is that same than that of the media_device. Signed-off-by: Sakari Ailus ---

[RFC v3 13/21] media device: Deprecate media_device_{init,cleanup}() for drivers

Drivers should no longer directly allocate media_device but rely on media_device_alloc(), media_device_get() and media_device_put() instead. Deprecate media_device_init() and media_device_cleanup(). Signed-off-by: Sakari Ailus --- include/media/media-device.h | 8

[RFC v3 19/21] omap3isp: Allocate the media device dynamically

Use the new media_device_alloc() API to allocate and release the media device. Signed-off-by: Sakari Ailus --- drivers/media/platform/omap3isp/isp.c | 24 +--- drivers/media/platform/omap3isp/isp.h | 2 +-

[RFC v3 10/21] media: Shuffle functions around

As the call paths of the functions in question will change, move them around in anticipation of that. No other changes. Signed-off-by: Sakari Ailus Acked-by: Hans Verkuil --- drivers/media/media-device.c | 56

[RFC v3 14/21] media device: Get the media device driver's device

The struct device of the media device driver (i.e. not that of the media devnode) is pointed to by the media device. The struct device pointer is mostly used for debug prints. Ensure it will stay around as long as the media device does. Signed-off-by: Sakari Ailus

[RFC v3 20/21] omap3isp: Release the isp device struct by media device callback

Use the media device release callback to release the isp device's data structure. This approach has the benefit of not releasing memory which may still be accessed through open file handles whilst the isp driver is being unbound. Signed-off-by: Sakari Ailus ---

[RFC v3 21/21] omap3isp: Don't rely on devm for memory resource management

devm functions are fine for managing resources that are directly related to the device at hand and that have no other dependencies. However, a process holding a file handle to a device created by a driver for a device may result in the file handle left behind after the device is long gone. This

[RFC v3 17/21] v4l: Acquire a reference to the media device for every video device

The video device depends on the existence of its media device --- if there is one. Acquire a reference to it. Signed-off-by: Sakari Ailus --- drivers/media/v4l2-core/v4l2-dev.c | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git

[RFC v3 05/21] media: devnode: Rename mdev argument as devnode

Historically, mdev argument name was being used on both struct media_device and struct media_devnode. Recently most occurrences of mdev referring to struct media_devnode were replaced by devnode, which makes more sense. Fix the last remaining occurrence. Fixes: 163f1e93e9950 ("[media]

[RFC v3 07/21] media-device: Make devnode.dev->kobj parent of devnode.cdev

The struct cdev embedded in struct media_devnode contains its own kobj. Instead of trying to manage its lifetime separately from struct media_devnode, make the cdev kobj a parent of the struct media_device.dev kobj. The cdev will thus be released during unregistering the media_devnode, not in

[RFC v3 11/21] media device: Refcount the media device

As the struct media_device embeds struct media_devnode, the lifetime of that object must be that same than that of the media_device. References are obtained by media_entity_get() and released by media_entity_put(). In case a driver uses media_device_alloc() to allocate its media device, it must

[RFC v3 12/21] media device: Initialise media devnode in media_device_init()

Call media_devnode_init() from media_device_init(). This has the effect of creating a struct device for the media_devnode before it is registered, making it possible to obtain a reference to it for e.g. video devices. Signed-off-by: Sakari Ailus ---

[RFC v3 16/21] media: Add release callback for media device

The release callback may be used by the driver to signal the release of the media device. This way the lifetime of the driver's own memory allocations may be made dependent on that of the media device. Signed-off-by: Sakari Ailus --- drivers/media/media-device.c |

[RFC v3 18/21] media-device: Postpone graph object removal until free

The media device itself will be unregistered based on it being unbound and driver's remove callback being called. The graph objects themselves may still be in use; rely on the media device release callback to release them. Signed-off-by: Sakari Ailus Acked-by: Hans

[RFC v3 06/21] media device: Drop nop release callback

The release callback is only used to print a debug message. Drop it. (It will be re-introduced later in a different form.) Signed-off-by: Sakari Ailus --- drivers/media/media-device.c | 6 -- 1 file changed, 6 deletions(-) diff --git

[RFC v3 15/21] media: Provide a way to the driver to set a private pointer

Now that the media device can be allocated dynamically, drivers have no longer a way to conveniently obtain the driver private data structure. Provide one again in the form of a private pointer passed to the media_device_alloc() function. Signed-off-by: Sakari Ailus

Re: [PATCH 5/8] media: vidc: add Host Firmware Interface (HFI)

Hi Bjorn, Thanks for the comments! On 08/23/2016 06:25 AM, Bjorn Andersson wrote: > On Mon 22 Aug 06:13 PDT 2016, Stanimir Varbanov wrote: > >> This is the implementation of HFI. It is loaded with the >> responsibility to comunicate with the firmware through an >> interface commands and

Re: Plan to support Rockchip VPU in DRM, is it a good idea

On 08/26/2016 06:56 PM, Hans Verkuil wrote: On 08/26/2016 12:05 PM, Randy Li wrote: On 08/26/2016 05:34 PM, Hans Verkuil wrote: Hi Randi, On 08/26/2016 04:13 AM, Randy Li wrote: Hello, We always use some kind of hack work to make our Video Process Unit(Multi-format Video

Re: [PATCH 0/3] doc-rst: generic way to build PDF of sub-folder

Am 26.08.2016 um 13:34 schrieb Mauro Carvalho Chehab : > Hi Markus, > > Em Wed, 24 Aug 2016 17:36:13 +0200 > Markus Heiser escreveu: > >> From: Markus Heiser >> >> Hi Mauro, >> >> here is a small patch series

[PATCH 2/2] cec-follower: extend man page

The man page is extended with some more information about the tool and what it does, and a SEE ALSO section is added. Signed-off-by: Johan Fjeldtvedt --- utils/cec-follower/cec-follower.1.in | 45 ++-- 1 file changed, 38 insertions(+), 7

[PATCH 1/2] cec-compliance: extend man page

The man page is extended with a more detailed description including a more in-depth explanation of the different test result codes. An example of how to run tests is also included, and a SEE ALSO section is added. Signed-off-by: Johan Fjeldtvedt ---

Re: [PATCH 0/3] doc-rst: generic way to build PDF of sub-folder

Hi Markus, Em Wed, 24 Aug 2016 17:36:13 +0200 Markus Heiser escreveu: > From: Markus Heiser > > Hi Mauro, > > here is a small patch series which extends the method to build only > sub-folders > to the targets "latexdocs" and "pdfdocs". >

Re: Plan to support Rockchip VPU in DRM, is it a good idea

On 08/26/2016 12:05 PM, Randy Li wrote: > > > On 08/26/2016 05:34 PM, Hans Verkuil wrote: >> Hi Randi, >> >> On 08/26/2016 04:13 AM, Randy Li wrote: >>> Hello, >>>We always use some kind of hack work to make our Video Process >>> Unit(Multi-format Video Encoder/Decoder) work in kernel. From

Re: Plan to support Rockchip VPU in DRM, is it a good idea

On 08/26/2016 05:34 PM, Hans Verkuil wrote: Hi Randi, On 08/26/2016 04:13 AM, Randy Li wrote: Hello, We always use some kind of hack work to make our Video Process Unit(Multi-format Video Encoder/Decoder) work in kernel. From a customize driver(vpu service) to the customize V4L2 driver.

Re: Plan to support Rockchip VPU in DRM, is it a good idea

Hi Randi, On 08/26/2016 04:13 AM, Randy Li wrote: > Hello, >We always use some kind of hack work to make our Video Process > Unit(Multi-format Video Encoder/Decoder) work in kernel. From a > customize driver(vpu service) to the customize V4L2 driver. The V4L2 > subsystem is really not

[PATCH] cec-compliance: recognize PRESUMED_OK and REFUSED as ok

It is only checked for PRESUMED_OK and REFUSED when performing remote tests, but these test result codes are also used elsewhere, so checking for them is moved to the ok function. Signed-off-by: Johan Fjeldtvedt --- utils/cec-compliance/cec-compliance.cpp | 9 +++--

Re: [RFC PATCH 5/7] ov7670: add devicetree support

Hi Laurent, On 08/17/2016 02:44 PM, Laurent Pinchart wrote: > Hi Hans, > > Thank you for the patch. > > On Wednesday 17 Aug 2016 08:29:41 Hans Verkuil wrote: >> From: Hans Verkuil >> >> Add DT support. Use it to get the reset and pwdn pins (if there are any). >> Tested