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: Mon Oct 30 05:00:15 CET 2017 media-tree git hash:bbae615636155fa43a9b0fe0ea31c678984be864 media_build

[PATCH] st-hva: hva-h264: use swap macro in hva_h264_encode

Make use of the swap macro and remove unnecessary variable tmp_frame. This makes the code easier to read and maintain. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/media/platform/sti/hva/hva-h264.c | 5 + 1 file

Re: [PATCHv3 1/2] tda18250: support for new silicon tuner

Hello Michael, Many thanks for taking the time to review the patches. On 27 October 2017 at 13:27, Michael Ira Krufky wrote: >> +static int tda18250_sleep(struct dvb_frontend *fe) >> +{ >> + struct i2c_client *client = fe->tuner_priv; >> + struct tda18250_dev

[PATCH v3 3/3] MAINTAINERS: Add a new entry of the ov7740 driver

Add a new entry of the ov7740 sensor driver to the MAINTAINERS file. Signed-off-by: Wenyou Yang --- Changes in v3: - Put the MAINTAINERS change to a separate patch. Changes in v2: - Split off the bindings into a separate patch. - Add a new entry to the MAINTAINERS

[PATCH v3 2/3] media: ov7740: Document device tree bindings

Add the device tree binding documentation for the ov7740 sensor driver. Signed-off-by: Wenyou Yang --- Changes in v3: - Explicitly document the "remote-endpoint" property. Changes in v2: None .../devicetree/bindings/media/i2c/ov7740.txt | 47

[PATCH v3 1/3] media: i2c: Add the ov7740 image sensor driver

The ov7740 (color) image sensor is a high performance VGA CMOS image snesor, which supports for output formats: RAW RGB and YUV and image sizes: VGA, and QVGA, CIF and any size smaller. Signed-off-by: Songjun Wu Signed-off-by: Wenyou Yang ---

[PATCH v3 0/3] media: ov7740: Add a V4L2 sensor-level driver

Add a Video4Linux2 sensor-level driver for the OmniVision OV7740 VGA camera image sensor. Changes in v3: - Explicitly document the "remote-endpoint" property. - Put the MAINTAINERS change to a separate patch. Changes in v2: - Split off the bindings into a separate patch. - Add a new entry to

Re: [PATCH v2 2/2] media: ov7740: Document device tree bindings

Hi Sakari, Thank you very much for your review and advice. I will send a new version to fix it. On 2017/10/27 18:59, Sakari Ailus wrote: Hi Wenyou, On Fri, Oct 27, 2017 at 03:42:20PM +0800, Wenyou Yang wrote: Add the device tree binding documentation for ov7740 driver and add a new entry of

[PATCH] media: atmel-isc: Fix clock ID for clk_prepare/unprepare

Fix the clock ID to do the runtime pm should be ISC_ISPCK, instead of ISC_MCK in clk_prepare(), clk_unprepare() and isc_clk_is_enabled(). Signed-off-by: Wenyou Yang --- drivers/media/platform/atmel/atmel-isc.c | 8 1 file changed, 4 insertions(+), 4

Re: [PATCH v5 0/5] media: atmel-isc: Rework the format list and clock provider

Hi Hans, On 2017/10/27 20:41, Hans Verkuil wrote: Hi Wenyou, Unfortunately the v4 patch series was just merged instead of v5. Can you make a new patch applying just the v4 -> v5 changes? Thank you for your merging. Of course, I will send a patch to fix it. Thanks! Hans On

Re: [PATCH v16 32/32] arm: dts: omap3: N9/N950: Add flash references to the camera

Hi, On Thu, Oct 26, 2017 at 10:53:42AM +0300, Sakari Ailus wrote: > Add flash and indicator LED phandles to the sensor node. > > Signed-off-by: Sakari Ailus > Acked-by: Hans Verkuil > Acked-by: Pavel Machek > ---

Re: [PATCH v16 31/32] ov13858: Add support for flash and lens devices

Hi, On Thu, Oct 26, 2017 at 10:53:41AM +0300, Sakari Ailus wrote: > Parse async sub-devices related to the sensor by switching the async > sub-device registration function. > > Signed-off-by: Sakari Ailus > Acked-by: Hans Verkuil > ---

Re: [PATCH v16 30/32] ov5670: Add support for flash and lens devices

Hi, On Thu, Oct 26, 2017 at 10:53:40AM +0300, Sakari Ailus wrote: > Parse async sub-devices related to the sensor by switching the async > sub-device registration function. > > Signed-off-by: Sakari Ailus > Acked-by: Hans Verkuil > ---

Re: [PATCH v16 29/32] et8ek8: Add support for flash and lens devices

Hi, On Thu, Oct 26, 2017 at 10:53:39AM +0300, Sakari Ailus wrote: > Parse async sub-devices related to the sensor by switching the async > sub-device registration function. > > Signed-off-by: Sakari Ailus > Acked-by: Hans Verkuil >

Re: [PATCH v16 28/32] smiapp: Add support for flash and lens devices

Hi, On Thu, Oct 26, 2017 at 10:53:38AM +0300, Sakari Ailus wrote: > Parse async sub-devices related to the sensor by switching the async > sub-device registration function. > > These types devices aren't directly related to the sensor, but are > nevertheless handled by the smiapp driver due to

Re: [PATCH v16 27/32] dt: bindings: smiapp: Document lens-focus and flash-leds properties

Hi, On Thu, Oct 26, 2017 at 10:53:37AM +0300, Sakari Ailus wrote: > Document optional lens-focus and flash-leds properties for the smiapp > driver. > > Signed-off-by: Sakari Ailus > Acked-by: Hans Verkuil > Acked-by: Pavel Machek

Re: [PATCH v16 26/32] v4l: fwnode: Add a convenience function for registering sensors

Hi, On Thu, Oct 26, 2017 at 10:53:36AM +0300, Sakari Ailus wrote: > Add a convenience function for parsing firmware for information on related > devices using v4l2_async_notifier_parse_fwnode_sensor_common() registering > the notifier and finally the async sub-device itself. > > This should be

Re: [PATCH v16.1 25/32] v4l: fwnode: Add convenience function for parsing common external refs

Hi, On Thu, Oct 26, 2017 at 06:03:27PM +0300, Sakari Ailus wrote: > Add v4l2_fwnode_parse_reference_sensor_common for parsing common > sensor properties that refer to adjacent devices such as flash or lens > driver chips. > > As this is an association only, there's little a regular driver needs

Re: [PATCH v16.1 24/32] v4l: fwnode: Add a helper function to obtain device / integer references

Hi, On Thu, Oct 26, 2017 at 06:01:58PM +0300, Sakari Ailus wrote: > v4l2_fwnode_reference_parse_int_prop() will find an fwnode such that under > the device's own fwnode, it will follow child fwnodes with the given > property-value pair and return the resulting fwnode. > > Signed-off-by: Sakari

Re: [PATCH v16 23/32] v4l: fwnode: Add a helper function for parsing generic references

Hi, On Thu, Oct 26, 2017 at 10:53:33AM +0300, Sakari Ailus wrote: > Add function v4l2_fwnode_reference_parse() for parsing them as async > sub-devices. This can be done on e.g. flash or lens async sub-devices that > are not part of but are associated with a sensor. > > Signed-off-by: Sakari

Re: [PATCH v16 22/32] v4l: fwnode: Move KernelDoc documentation to the header

Hi, On Thu, Oct 26, 2017 at 10:53:32AM +0300, Sakari Ailus wrote: > In V4L2 the practice is to have the KernelDoc documentation in the header > and not in .c source code files. This consequently makes the V4L2 fwnode > function documentation part of the Media documentation build. > > Also

Re: [PATCH v16 20/32] dt: bindings: Add a binding for flash LED devices associated to a sensor

Hi, On Thu, Oct 26, 2017 at 10:53:30AM +0300, Sakari Ailus wrote: > Camera flash drivers (and LEDs) are separate from the sensor devices in > DT. In order to make an association between the two, provide the > association information to the software. > > Signed-off-by: Sakari Ailus

Re: [PATCH v16.1 19/32] v4l: async: Ensure only unique fwnodes are registered to notifiers

Hi, On Fri, Oct 27, 2017 at 01:53:09PM +0300, Sakari Ailus wrote: > While registering a notifier, check that each newly added fwnode is > unique, and return an error if it is not. Also check that a newly added > notifier does not have the same fwnodes twice. > > Signed-off-by: Sakari Ailus

Re: [PATCH v16.1 18/32] v4l: async: Allow binding notifiers to sub-devices

Hi, On Fri, Oct 27, 2017 at 11:27:09AM +0300, Sakari Ailus wrote: > Registering a notifier has required the knowledge of struct v4l2_device > for the reason that sub-devices generally are registered to the > v4l2_device (as well as the media device, also available through > v4l2_device). > >

[PATCH 28/28] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

If you try to store u64 in a kfifo (or a struct with u64 members), then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes padding due to alignment (note that struct __kfifo is 20 bytes on 32 bit). That in turn causes the __is_kfifo_ptr() to fail, which is caught by kfifo_alloc(), which now

[PATCH 25/28] media: lirc: document LIRC_MODE_SCANCODE

Lirc supports a new mode which requires documentation. Signed-off-by: Sean Young --- Documentation/media/lirc.h.rst.exceptions | 26 +++ Documentation/media/uapi/rc/lirc-dev-intro.rst | 51 +++---

[PATCH 26/28] media: lirc: introduce LIRC_SET_POLL_MODES

If you want to poll for both decoded scancodes and raw IR, then this ioctl will help you. int fd = open("/dev/lirc0", O_RDONLY | O_NONBLOCK); for (;;) { unsigned mode = LIRC_MODE_SCANCODE | LIRC_MODE_MODE2; ioctl(fd, LIRC_SET_POLL_MODES, ); poll(&((struct pollfd){ .fd =

[PATCH 27/28] media: lirc: scancode rc devices should have a lirc device too

Now that the lirc interface supports scancodes, RC scancode devices can also have a lirc device. The only receiving feature they will have enabled is LIRC_CAN_REC_SCANCODE. Note that CEC devices have no lirc device, since they can be controlled from their /dev/cecN chardev. Signed-off-by: Sean

[PATCH 23/28] media: lirc: implement reading scancode

This implements LIRC_MODE_SCANCODE reading from the lirc device. The scancode can be read from the input device too, but with this interface you get the rc protocol, keycode, toggle and repeat status in addition to just the scancode. int main() { int fd, mode, rc; fd =

[PATCH 24/28] media: rc: ensure lirc device receives nec repeats

The lirc device should get lirc repeats whether there is a keymap match or not. Signed-off-by: Sean Young --- drivers/media/rc/rc-main.c | 27 +-- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/drivers/media/rc/rc-main.c

[PATCH 22/28] media: lirc: remove last remnants of lirc kapi

rc-core has replaced the lirc kapi many years ago, and now with the last driver ported to rc-core, we can finally remove it. Note this has no effect on userspace. All future IR drivers should use the rc-core api. Signed-off-by: Sean Young ---

[PATCH 20/28] media: lirc: create rc-core open and close lirc functions

Replace the generic kernel lirc api with ones which use rc-core, further reducing the lirc_dev members. Signed-off-by: Sean Young --- drivers/media/rc/ir-lirc-codec.c | 59 -- drivers/media/rc/lirc_dev.c | 68

[PATCH 21/28] media: lirc: remove name from lirc_dev

This is a duplicate of rcdev->driver_name. Signed-off-by: Sean Young --- Documentation/media/uapi/rc/lirc-dev-intro.rst | 2 +- drivers/media/rc/ir-lirc-codec.c | 2 -- drivers/media/rc/lirc_dev.c| 9 +++-- include/media/lirc_dev.h

[PATCH 12/28] media: rc: auto load encoder if necessary

When sending scancodes, load the encoder if we need it. Signed-off-by: Sean Young --- drivers/media/rc/rc-core-priv.h | 1 + drivers/media/rc/rc-ir-raw.c| 2 ++ drivers/media/rc/rc-main.c | 2 +- 3 files changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH 08/28] media: MAINTAINERS: remove lirc staging area

Now that lirc is no longer in the staging area, remove the entry. Signed-off-by: Sean Young --- MAINTAINERS | 6 -- 1 file changed, 6 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index adbf69306e9e..59c061d3d61a 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -12712,12

[PATCH 16/28] media: lirc: merge lirc_dev_fop_ioctl and ir_lirc_ioctl

Calculate lirc features when necessary, and add LIRC_{S,G}ET_REC_MODE cases to ir_lirc_ioctl. This makes lirc_dev_fop_ioctl() unnecessary since all cases are already handled by ir_lirc_ioctl(). Signed-off-by: Sean Young --- drivers/media/rc/ir-lirc-codec.c | 79

[PATCH 17/28] media: lirc: use kfifo rather than lirc_buffer for raw IR

Since the only mode lirc devices can handle is raw IR, handle this in a plain kfifo. Remove lirc_buffer since this is no longer needed. Signed-off-by: Sean Young --- drivers/media/rc/ir-lirc-codec.c | 79 +--- drivers/media/rc/lirc_dev.c | 199

[PATCH 11/28] media: lirc: use the correct carrier for scancode transmit

If the lirc device supports it, set the carrier for the protocol. Signed-off-by: Sean Young --- drivers/media/rc/ir-jvc-decoder.c | 1 + drivers/media/rc/ir-lirc-codec.c | 29 ++--- drivers/media/rc/ir-mce_kbd-decoder.c | 1 +

[PATCH 09/28] media: lirc: remove LIRCCODE and LIRC_GET_LENGTH

LIRCCODE is a lirc mode where a driver produces driver-dependent codes for receive and transmit. No driver uses this any more. The LIRC_GET_LENGTH ioctl was used for this mode only. Signed-off-by: Sean Young --- Documentation/media/lirc.h.rst.exceptions | 5 +++

[PATCH 13/28] media: lirc: lirc interface should not be a raw decoder

The lirc user interface exists as a raw decoder, which does not make much sense for transmit-only devices. In addition, we want to have lirc char devices for devices which do not use raw IR, i.e. scancode only devices. Note that rc-code, lirc_dev, ir-lirc-codec are now calling functions of each

[PATCH 18/28] media: lirc: move lirc_dev->attached to rc_dev->registered

This is done to further remove the lirc kernel api. Ensure that every fops checks for this. Signed-off-by: Sean Young --- drivers/media/rc/ir-lirc-codec.c | 16 ++-- drivers/media/rc/lirc_dev.c | 4 +--- drivers/media/rc/rc-main.c | 8

[PATCH 14/28] media: lirc: validate scancode for transmit

Ensure we reject an attempt to transmit invalid scancodes. Signed-off-by: Sean Young --- drivers/media/rc/ir-lirc-codec.c | 10 drivers/media/rc/rc-core-priv.h | 1 + drivers/media/rc/rc-main.c | 53 +--- 3 files changed, 44

[PATCH 05/28] media: rc: implement zilog transmitter

This code implements the transmitter which is currently implemented in the staging lirc_zilog driver. The new code does not need a signal database, iow. the haup-ir-blaster.bin firmware file is no longer needed, and the driver does not know anything about the keycodes in that file. Instead, the

[PATCH 10/28] media: lirc: implement scancode sending

This introduces a new lirc mode: scancode. Any device which can send raw IR can now also send scancodes. int main() { int mode, fd = open("/dev/lirc0", O_RDWR); mode = LIRC_MODE_SCANCODE; if (ioctl(fd, LIRC_SET_SEND_MODE, )) { // kernel too old or lirc

[PATCH 06/28] media: i2c: enable i2c IR for hardware which isn't HD-PVR

This is a fix for commit 329d88da4df9 ("[media] media: i2c: Don't export ir-kbd-i2c module alias") that stopped the module from being loaded automagically. The problems described only affect the HD-PVR, so it should not affect other hardware; also if the module happens to be loaded, the i2c IR

[PATCH 19/28] media: lirc: do not call rc_close() on unregistered devices

If a lirc chardev is held open after a device is unplugged, rc_close() will be called after rc_unregister_device(). The driver is not expecting any calls at this point, and the iguanair driver causes an oops in this scenario. Signed-off-by: Sean Young ---

[PATCH 15/28] media: rc: document and fix rc_validate_scancode()

For some IR protocols, some scancode values not valid, i.e. they're part of a different protocol variant. Signed-off-by: Sean Young --- drivers/media/rc/rc-main.c | 18 -- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/drivers/media/rc/rc-main.c

[PATCH 07/28] media: staging: remove lirc_zilog driver

The ir-kbd-i2c driver is functionally equivalent to the lirc_zilog driver. The lirc_zilog driver only polls if the lirc chardev is opened; similarly the ir-kbd-i2c driver only polls if the corresponding input device is opened, or the lirc device. Polling is disabled during IR transmission

[PATCH 03/28] media: rc: i2c: only poll if the rc device is opened

The lirc_zilog driver only polls the device if the lirc chardev is opened; do the same with the rc-core driver. Signed-off-by: Sean Young --- drivers/media/i2c/ir-kbd-i2c.c | 25 + 1 file changed, 21 insertions(+), 4 deletions(-) diff --git

[PATCH 01/28] media: rc: i2c: set parent of rc device and improve name

With the parent set for the rc device, the messages clearly state that it is attached via i2c. The additional printk is unnecessary. So these are the old messages: rc rc1: i2c IR (Hauppauge WinTV PVR-150 as /devices/virtual/rc/rc1 ir-kbd-i2c: i2c IR (Hauppauge WinTV PVR-150 detected at

[PATCH 04/28] media: merge ir_tx_z8f0811_haup and ir_rx_z8f0811_haup i2c devices

These two devices ids are really just one device with multiple addresses. Probing becomes much simpler if we simply fold this into one i2c device with two address. Note that this breaks the lirc_zilog driver, however we will teach ir-kbd-i2c to do what lirc_zilog does in a later commit.

[PATCH 00/28] lirc scancode interface, and more

Port lirc_zilog to rc-core, introduce lirc scancode mode for sending and receiving, and then remove the lirc kernel api. Note that the ported zilog driver needs the scancode interface, since without it the RC_DRIVER_SCANCODE type IR driver would not have a lirc chardev. In summary: - This

[PATCH 02/28] media: rc: i2c: use dev_dbg rather hand-rolled debug

Use the dev_dbg dynamic infrastructure instead of rolling our own custom debug logic. Signed-off-by: Sean Young --- drivers/media/i2c/ir-kbd-i2c.c | 61 +- 1 file changed, 25 insertions(+), 36 deletions(-) diff --git

Re: 'LITE-ON USB2.0 DVB-T Tune' driver crash with kernel 4.13 / ubuntu 17.10

On Sun, Oct 29, 2017 at 06:54:28PM +0100, Laurent Caumont wrote: > Hi Sean, > > I recompiled the modules by following the > https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers > page and applied the patch. > But I still have problems (see below). It

Re: 'LITE-ON USB2.0 DVB-T Tune' driver crash with kernel 4.13 / ubuntu 17.10

Hi Sean, I recompiled the modules by following the https://www.linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers page and applied the patch. But I still have problems (see below). It doesn't seem to be the same callstack. Is it the right way to get the fix ?

[PATCH] [media] dvb-core: always call invoke_release() in fe_free()

From: Daniel Scheller Follow-up to: ead666000a5f ("media: dvb_frontend: only use kref after initialized") The aforementioned commit fixed refcount OOPSes when demod driver attaching succeeded but tuner driver didn't. However, the use count of the attached demod drivers

[PATCH][V2] bdisp: remove redundant assignment to pix

From: Colin Ian King Pointer pix is being initialized to a value and a little later being assigned the same value again. Remove the initial assignment to avoid a duplicate assignment. Cleans up the clang warning: drivers/media/platform/sti/bdisp/bdisp-v4l2.c:726:26:

[GIT PULL FOR v4.15] ids and RC timer API change

Hi Mauro, Here the timer updates and some IDs for mceusb and cx231xx. Thanks Sean The following changes since commit bbae615636155fa43a9b0fe0ea31c678984be864: media: staging: atomisp2: cleanup null check on memory allocation (2017-10-27 17:33:39 +0200) are available in the git repository

Re: [PATCH] [media] bdisp: remove redundant assignment to pix

On 29/10/17 13:30, Julia Lawall wrote: > > > On Sun, 29 Oct 2017, Colin King wrote: > >> From: Colin Ian King >> >> Pointer pix is being initialized to a value and a little later >> being assigned the same value again. Remove the redundant second >> duplicate

Re: [PATCH] [media] bdisp: remove redundant assignment to pix

On Sun, 29 Oct 2017, Colin King wrote: > From: Colin Ian King > > Pointer pix is being initialized to a value and a little later > being assigned the same value again. Remove the redundant second > duplicate assignment. Cleans up the clang warning: > >

[PATCH] [media] bdisp: remove redundant assignment to pix

From: Colin Ian King Pointer pix is being initialized to a value and a little later being assigned the same value again. Remove the redundant second duplicate assignment. Cleans up the clang warning: drivers/media/platform/sti/bdisp/bdisp-v4l2.c:726:26: warning: Value

[PATCH] [media] gspca: remove redundant assignment to variable j

From: Colin Ian King Variable j is being set to zero before a loop and also immediately inside the loop and is not used after the loop. Hence the first assignment is redundant and can be removed. Cleans up clang warning: drivers/media/usb/gspca/gspca.c:1078:2: warning:

[PATCH] [media] mxl111sf: remove redundant assignment to index

From: Colin Ian King Variable index is set to zero and then set to zero again a few lines later in a for loop initialization. Remove the redundant setting of index to zero. Cleans up the clang warning: drivers/media/usb/dvb-usb-v2/mxl111sf-i2c.c:519:3: warning: Value