cron job: media_tree daily build: WARNINGS

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 Sep 9 05:00:20 CEST 2017 media-tree git hash:1efdf1776e2253b77413c997bed862410e4b6aaf media_build

Re: [PATCH] em28xx: add support for Hauppauge WinTV-dualHD DVB tuner

Hi Mauro, On 2017-09-07 09:52, Mauro Carvalho Chehab wrote: > Hi Brad, > > Em Wed, 31 May 2017 15:01:00 -0500 > Brad Love escreveu: > >> Christian et al, >> >> I am an engineer at Hauppauge. This repo is the staging area for all the >> patches I am testing, with the

Travelers List

Hi, Greeting of the day! I hope this note finds you well! Would you be interested in acquiring an email list of "Travelers" from USA? We also have data for Frequent Travelers List, Camping and Outdoor List, Scuba Divers List, Cruise Travelers List, Vacation Travelers List,Boat Owners List,

Re: [PATCH] media: default for RC_CORE should be n

Em Fri, 8 Sep 2017 12:06:48 -0700 Stephen Hemminger escreveu: > On Fri, 8 Sep 2017 19:52:47 +0100 > Sean Young wrote: > > > On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote: > > > The Linus policy on Kconfig is that the default

Re: [PATCH v9 23/24] dt: bindings: smiapp: Document lens-focus and flash properties

On Fri 2017-09-08 16:42:26, Sakari Ailus wrote: > Hi Pavel, > > On Fri, Sep 08, 2017 at 03:36:52PM +0200, Pavel Machek wrote: > > Hi! > > > > > Document optional lens-focus and flash properties for the smiapp driver. > > > > > > Signed-off-by: Sakari Ailus > > >

[PATCH] [media] tuners: mxl5005s: make arrays static const, reduces object code size

From: Colin Ian King Don't populate the arrays RegAddr on the stack, instead make them static const. Makes the object code smaller by over 980 bytes: Before: textdata bss dec hex filename 64923 304 0 65227fecb

[PATCH 3/3] [media] s5p-mfc: Adjust a null pointer check in four functions

From: Markus Elfring Date: Fri, 8 Sep 2017 22:37:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus

[PATCH 2/3] [media] s5p-mfc: Improve a size determination in s5p_mfc_alloc_memdev()

From: Markus Elfring Date: Fri, 8 Sep 2017 22:30:09 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 1/3] [media] s5p-mfc: Delete an error message for a failed memory allocation in s5p_mfc_probe()

From: Markus Elfring Date: Fri, 8 Sep 2017 22:25:17 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/3] S5P MFC: Adjustments for five function implementations

From: Markus Elfring Date: Fri, 8 Sep 2017 22:44:55 +0200 Three update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in s5p_mfc_probe() Improve a size

[PATCH] [media] pxa_camera: Delete an error message for a failed memory allocation in pxa_camera_probe()

From: Markus Elfring Date: Fri, 8 Sep 2017 22:05:14 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [PATCH 0/3] AS3645A fixes

Hi Sakari, Thanks for the patch set. On 09/08/2017 02:42 PM, Sakari Ailus wrote: > Hi folks, > > Here are a few fixes for the as3645a DTS as well as changes in bindings. > The driver is not in a release yet. I'd like to get these in as through > the media tree fixes branch. > > Sakari Ailus

[PATCH 3/3] [media] fsl-viu: Adjust six checks for null pointers

From: Markus Elfring Date: Fri, 8 Sep 2017 21:16:50 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH] media: rc: Use bsearch library function

Replace self coded binary search, by existing library version. Signed-off-by: Thomas Meyer --- drivers/media/rc/rc-main.c | 34 -- 1 file changed, 20 insertions(+), 14 deletions(-) diff --git a/drivers/media/rc/rc-main.c

[PATCH 2/3] [media] fsl-viu: Improve two size determinations in viu_of_probe()

From: Markus Elfring Date: Fri, 8 Sep 2017 21:12:52 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 1/3] [media] fsl-viu: Delete an error message for a failed memory allocation in viu_of_probe()

From: Markus Elfring Date: Fri, 8 Sep 2017 21:03:22 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[RFC PATCH v8 0/2] mmap: safely enable support for new flags

Changes since v7 [1]: * rebase on the mid-merge-window state of the tree to pick up new mmap implementations. * expand the mmap operation handler conversion beyond 'struct file_operations' to include, 'struct etnaviv_gem_ops', 'struct dma_buf_ops', 'struct drm_driver', 'struct fb_ops', and

[PATCH 0/3] [media] Freescale VIU: Adjustments for five function implementations

From: Markus Elfring Date: Fri, 8 Sep 2017 21:28:12 +0200 Three update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in viu_of_probe() Improve two size

Re: [PATCH 1/1] media: i2c: as3645a: Remove driver

On Fri 2017-09-08 16:51:40, Sakari Ailus wrote: 1;2802;0c> Remove the V4L2 AS3645A sub-device driver in favour of the LED flash class > driver for the same hardware, drivers/leds/leds-as3645a.c. The latter uses > the V4L2 flash LED class framework to provide V4L2 sub-device interface. > >

Re: [PATCH] media: default for RC_CORE should be n

On Fri, 8 Sep 2017 19:52:47 +0100 Sean Young wrote: > On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote: > > The Linus policy on Kconfig is that the default should be no > > for all new devices. I.e the user rebuild a new kernel from an > > old config should not by

Re: [PATCH] media: default for RC_CORE should be n

On Fri, Sep 08, 2017 at 09:39:29AM -0700, Stephen Hemminger wrote: > The Linus policy on Kconfig is that the default should be no > for all new devices. I.e the user rebuild a new kernel from an > old config should not by default get a larger kernel. That might make sense for new config, but

[PATCH] media: default for RC_CORE should be n

The Linus policy on Kconfig is that the default should be no for all new devices. I.e the user rebuild a new kernel from an old config should not by default get a larger kernel. Fixes: b4c184e506a4 ("[media] media: reorganize the main Kconfig items") Signed-off-by: Stephen Hemminger

Re: [Outreachy kernel] [PATCH] Staging: media: imx: Prefer using BIT macro

On Fri, Sep 8, 2017 at 8:59 PM, Sean Paul wrote: > On Fri, Sep 8, 2017 at 11:11 AM, Srishti Sharma wrote: >> Use BIT(x) instead of (1<> >> Signed-off-by: Srishti Sharma >> --- >> drivers/staging/media/imx/imx-media.h |

[PATCH] v4l-ioctl: Fix typo on v4l_print_frmsizeenum

max_width and max_height are swap with step_width and step_height. Signed-off-by: Ricardo Ribalda Delgado --- Since that this bug has been here for ever. I do not know if we should notify stable or not I have also cut the lines to respect the 80 char limit

Re: [Outreachy kernel] [PATCH] Staging: media: imx: Prefer using BIT macro

On Fri, Sep 8, 2017 at 11:11 AM, Srishti Sharma wrote: > Use BIT(x) instead of (1< > Signed-off-by: Srishti Sharma > --- > drivers/staging/media/imx/imx-media.h | 16 > 1 file changed, 8 insertions(+), 8 deletions(-) > > diff

[PATCH] Staging: media: imx: Prefer using BIT macro

Use BIT(x) instead of (1< --- drivers/staging/media/imx/imx-media.h | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/staging/media/imx/imx-media.h b/drivers/staging/media/imx/imx-media.h index

Re: [PATCH] Staging: media: omap4iss: Use WARN_ON() instead of BUG_ON().

On Fri, Sep 8, 2017 at 8:08 PM, Dan Carpenter wrote: > On Fri, Sep 08, 2017 at 07:38:18PM +0530, Srishti Sharma wrote: >> Use WARN_ON() instead of BUG_ON() to avoid crashing the kernel. >> >> Signed-off-by: Srishti Sharma >> --- >>

[GIT FIXES FOR v4.14] Fixes for 4.14

The following changes since commit 1efdf1776e2253b77413c997bed862410e4b6aaf: media: leds: as3645a: add V4L2_FLASH_LED_CLASS dependency (2017-09-05 16:32:45 -0400) are available in the git repository at: git://linuxtv.org/hverkuil/media_tree.git for-v4.14l for you to fetch changes up to

Re: [PATCH] Staging: media: omap4iss: Use WARN_ON() instead of BUG_ON().

On Fri, Sep 08, 2017 at 07:38:18PM +0530, Srishti Sharma wrote: > Use WARN_ON() instead of BUG_ON() to avoid crashing the kernel. > > Signed-off-by: Srishti Sharma > --- > drivers/staging/media/omap4iss/iss.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

[GIT PULL FOR v4.15] Cleanup fixes

coccinelle, checkpatch, coverity, etc. etc. Regards, Hans The following changes since commit 1efdf1776e2253b77413c997bed862410e4b6aaf: media: leds: as3645a: add V4L2_FLASH_LED_CLASS dependency (2017-09-05 16:32:45 -0400) are available in the git repository at:

Re: [Outreachy kernel] [PATCH] Staging: media: omap4iss: Use WARN_ON() instead of BUG_ON().

On Fri, Sep 8, 2017 at 7:40 PM, Julia Lawall wrote: > > > On Fri, 8 Sep 2017, Srishti Sharma wrote: > >> Use WARN_ON() instead of BUG_ON() to avoid crashing the kernel. >> >> Signed-off-by: Srishti Sharma >> --- >>

Re: [Outreachy kernel] [PATCH] Staging: media: omap4iss: Use WARN_ON() instead of BUG_ON().

On Fri, 8 Sep 2017, Srishti Sharma wrote: > Use WARN_ON() instead of BUG_ON() to avoid crashing the kernel. > > Signed-off-by: Srishti Sharma > --- > drivers/staging/media/omap4iss/iss.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

[PATCH] Staging: media: omap4iss: Use WARN_ON() instead of BUG_ON().

Use WARN_ON() instead of BUG_ON() to avoid crashing the kernel. Signed-off-by: Srishti Sharma --- drivers/staging/media/omap4iss/iss.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/media/omap4iss/iss.c

Re: [PATCH v9 17/24] ACPI: Document how to refer to LEDs from remote nodes

On Fri, Sep 08, 2017 at 04:54:07PM +0300, Sakari Ailus wrote: > On Fri, Sep 08, 2017 at 04:43:20PM +0300, Mika Westerberg wrote: > > On Fri, Sep 08, 2017 at 04:18:15PM +0300, Sakari Ailus wrote: > > > + Device (LED) > > > + { > > > + Name ((_DSD), Package () { > > > +

Re: [PATCH v9 17/24] ACPI: Document how to refer to LEDs from remote nodes

On Fri, Sep 08, 2017 at 04:43:20PM +0300, Mika Westerberg wrote: > On Fri, Sep 08, 2017 at 04:18:15PM +0300, Sakari Ailus wrote: > > + Device (LED) > > + { > > + Name ((_DSD), Package () { > > + ToUUID("dbb8e3e6-5886-4ba6-8795-1319f52a966b"), > > +

[PATCH 1/1] media: i2c: as3645a: Remove driver

Remove the V4L2 AS3645A sub-device driver in favour of the LED flash class driver for the same hardware, drivers/leds/leds-as3645a.c. The latter uses the V4L2 flash LED class framework to provide V4L2 sub-device interface. Signed-off-by: Sakari Ailus ---

Re: [PATCH 3/3] as3645a: Use integer numbers for parsing LEDs

On Fri, Sep 08, 2017 at 03:38:41PM +0200, Pavel Machek wrote: > On Fri 2017-09-08 16:23:34, Sakari Ailus wrote: > > Hi Pavel, > > > > Thanks for the review. > > > > On Fri, Sep 08, 2017 at 03:17:58PM +0200, Pavel Machek wrote: > > > On Fri 2017-09-08 15:42:13, Sakari Ailus wrote: > > > > Use

Re: [PATCH v9 17/24] ACPI: Document how to refer to LEDs from remote nodes

On Fri, Sep 08, 2017 at 04:18:15PM +0300, Sakari Ailus wrote: > + Device (LED) > + { > + Name ((_DSD), Package () { > + ToUUID("dbb8e3e6-5886-4ba6-8795-1319f52a966b"), > + Package () { > + Package () { "led0",

Re: [PATCH v9 23/24] dt: bindings: smiapp: Document lens-focus and flash properties

Hi Pavel, On Fri, Sep 08, 2017 at 03:36:52PM +0200, Pavel Machek wrote: > Hi! > > > Document optional lens-focus and flash properties for the smiapp driver. > > > > Signed-off-by: Sakari Ailus > > --- > > Documentation/devicetree/bindings/media/i2c/nokia,smia.txt

Re: [PATCH 3/4] [media] sp2: Adjust a jump target in sp2_probe()

Hi Markus, On 09/01/17 21:44, SF Markus Elfring wrote: > From: Markus Elfring > Date: Fri, 1 Sep 2017 21:08:38 +0200 > > * Adjust a jump target so that a null pointer will not be passed to a call > of the function "kfree". > > * Move this function call into an

Re: [PATCH 3/3] as3645a: Use integer numbers for parsing LEDs

On Fri 2017-09-08 16:23:34, Sakari Ailus wrote: > Hi Pavel, > > Thanks for the review. > > On Fri, Sep 08, 2017 at 03:17:58PM +0200, Pavel Machek wrote: > > On Fri 2017-09-08 15:42:13, Sakari Ailus wrote: > > > Use integer numbers for LEDs, 0 is the flash and 1 is the indicator. > > > > > >

Re: [PATCH v9 23/24] dt: bindings: smiapp: Document lens-focus and flash properties

Hi! > Document optional lens-focus and flash properties for the smiapp driver. > > Signed-off-by: Sakari Ailus > --- > Documentation/devicetree/bindings/media/i2c/nokia,smia.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git

Re: [PATCH 3/3] as3645a: Use integer numbers for parsing LEDs

Hi Pavel, Thanks for the review. On Fri, Sep 08, 2017 at 03:17:58PM +0200, Pavel Machek wrote: > On Fri 2017-09-08 15:42:13, Sakari Ailus wrote: > > Use integer numbers for LEDs, 0 is the flash and 1 is the indicator. > > > > Signed-off-by: Sakari Ailus > >

Re: [PATCH v9 00/23] Unified fwnode endpoint parser, async sub-device notifier support, N9 flash DTS

On Fri, Sep 08, 2017 at 04:11:51PM +0300, Sakari Ailus wrote: > With this, the as3645a driver successfully registers a sub-device to the > media device created by the omap3isp driver. The kernel also has the > information it's related to the sensor driven by the smiapp driver but we > don't have a

[PATCH v9 05/24] v4l: fwnode: Support generic parsing of graph endpoints in a device

The current practice is that drivers iterate over their endpoints and parse each endpoint separately. This is very similar in a number of drivers, implement a generic function for the job. Driver specific matters can be taken into account in the driver specific callback. Signed-off-by: Sakari

[PATCH v9 11/24] v4l: async: Introduce helpers for calling async ops callbacks

Add three helper functions to call async operations callbacks. Besides simplifying callbacks, this allows async notifiers to have no ops set, i.e. it can be left NULL. Signed-off-by: Sakari Ailus --- drivers/media/v4l2-core/v4l2-async.c | 49

[PATCH v9 12/24] v4l: async: Register sub-devices before calling bound callback

Register the sub-device before calling the notifier's bound callback. Doing this the other way around is problematic as the struct v4l2_device has not assigned for the sub-device yet and may be required by the bound callback. Signed-off-by: Sakari Ailus Acked-by:

[PATCH v9 06/24] omap3isp: Use generic parser for parsing fwnode endpoints

Instead of using driver implementation, use v4l2_async_notifier_parse_fwnode_endpoints() to parse the fwnode endpoints of the device. Signed-off-by: Sakari Ailus Acked-by: Hans Verkuil --- drivers/media/platform/omap3isp/isp.c | 115

[PATCH v9 10/24] v4l: async: Move async subdev notifier operations to a separate structure

From: Laurent Pinchart The async subdev notifier .bound(), .unbind() and .complete() operations are function pointers stored directly in the v4l2_async_subdev structure. As the structure isn't immutable, this creates a potential security risk as the function

[PATCH v9 20/24] v4l: fwnode: Add a helper function to obtain device / interger references

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 Ailus ---

[PATCH v9 16/24] dt: bindings: Add lens-focus binding for image sensors

The lens-focus property contains a phandle to the lens voice coil driver that is associated to the sensor; typically both are contained in the same camera module. Signed-off-by: Sakari Ailus Acked-by: Pavel Machek Reviewed-by: Sebastian Reichel

[PATCH v9 15/24] dt: bindings: Add a binding for flash LED devices associated to a sensor

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 Acked-by: Rob Herring Acked-by: Hans

[PATCH v9 13/24] v4l: async: Allow async notifier register call succeed with no subdevs

The information on how many async sub-devices would be bindable to a notifier is typically dependent on information from platform firmware and it's not driver's business to be aware of that. Many V4L2 main drivers are perfectly usable (and useful) without async sub-devices and so if there aren't

[PATCH v9 24/24] arm: dts: omap3: N9/N950: Add flash references to the camera

Add flash and indicator LED phandles to the sensor node. Signed-off-by: Sakari Ailus --- arch/arm/boot/dts/omap3-n9.dts | 1 + arch/arm/boot/dts/omap3-n950-n9.dtsi | 4 ++-- arch/arm/boot/dts/omap3-n950.dts | 1 + 3 files changed, 4 insertions(+), 2

[PATCH v9 08/24] omap3isp: Fix check for our own sub-devices

We only want to link sub-devices that were bound to the async notifier the isp driver registered but there may be other sub-devices in the v4l2_device as well. Check for the correct async notifier. Signed-off-by: Sakari Ailus Acked-by: Hans Verkuil

[PATCH v9 17/24] ACPI: Document how to refer to LEDs from remote nodes

Document referring to LEDs from remote device nodes, such as from camera sensors. Signed-off-by: Sakari Ailus --- Documentation/acpi/dsd/leds.txt | 92 + 1 file changed, 92 insertions(+) create mode 100644

[PATCH v9 19/24] v4l: fwnode: Add a helper function for parsing generic references

Add function v4l2_fwnode_reference_count() for counting external references and 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. struct

[PATCH v9 14/24] v4l: async: Allow binding notifiers to sub-devices

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). This information is not available for sub-device drivers at probe time. What this

[PATCH v9 23/24] dt: bindings: smiapp: Document lens-focus and flash properties

Document optional lens-focus and flash properties for the smiapp driver. Signed-off-by: Sakari Ailus --- Documentation/devicetree/bindings/media/i2c/nokia,smia.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v9 09/24] omap3isp: Print the name of the entity where no source pads could be found

If no source pads are found in an entity, print the name of the entity. Signed-off-by: Sakari Ailus Acked-by: Hans Verkuil --- drivers/media/platform/omap3isp/isp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v9 22/24] smiapp: Add support for flash and lens devices

Parse async sub-devices by using v4l2_subdev_fwnode_reference_parse_sensor_common(). These types devices aren't directly related to the sensor, but are nevertheless handled by the smiapp driver due to the relationship of these component to the main part of the camera module --- the sensor. This

[PATCH v9 21/24] v4l: fwnode: Add convenience function for parsing common external refs

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 to know about these devices as such. Signed-off-by: Sakari Ailus

[PATCH v9 07/24] rcar-vin: Use generic parser for parsing fwnode endpoints

Instead of using driver implementation, use v4l2_async_notifier_parse_fwnode_endpoints() to parse the fwnode endpoints of the device. Signed-off-by: Sakari Ailus Acked-by: Hans Verkuil --- drivers/media/platform/rcar-vin/rcar-core.c | 112

[PATCH v9 18/24] as3645a: Switch to fwnode property API

Switch the as3645a from OF to the fwnode property API. Also add ACPI support. Signed-off-by: Sakari Ailus --- drivers/leds/leds-as3645a.c | 81 + 1 file changed, 46 insertions(+), 35 deletions(-) diff --git

Re: [PATCH 3/3] as3645a: Use integer numbers for parsing LEDs

On Fri 2017-09-08 15:42:13, Sakari Ailus wrote: > Use integer numbers for LEDs, 0 is the flash and 1 is the indicator. > > Signed-off-by: Sakari Ailus Dunno. Old code is shorter, old device tree is shorter, ... IMO both versions are fine, because the LEDs are

Re: [PATCH 1/3] as3645a: Use ams,input-max-microamp as documented in DT bindings

On Fri 2017-09-08 15:42:11, Sakari Ailus wrote: > DT bindings document the property "ams,input-max-microamp" that limits the > chip's maximum input current. The driver and the DTS however used > "peak-current-limit" property. Fix this by using the property documented > in DT binding documentation.

[PATCH v9 04/24] v4l: async: Add V4L2 async documentation to the documentation build

The V4L2 async wasn't part of the documentation build. Fix this. Signed-off-by: Sakari Ailus Reviewed-by: Niklas Söderlund Acked-by: Hans Verkuil --- Documentation/media/kapi/v4l2-async.rst | 3 +++

[PATCH v9 00/23] Unified fwnode endpoint parser, async sub-device notifier support, N9 flash DTS

Hi folks, We have a large influx of new, unmerged, drivers that are now parsing fwnode endpoints and each one of them is doing this a little bit differently. The needs are still exactly the same for the graph data structure is device independent. This is still a non-trivial task and the majority

[PATCH v9 01/24] v4l: fwnode: Move KernelDoc documentation to the header

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 correct the link related function and argument naming in documentation.

[PATCH v9 03/24] v4l: async: Use more intuitive names for internal functions

Rename internal functions to make the names of the functions better describe what they do. Old nameNew name v4l2_async_test_notify v4l2_async_match_notify v4l2_async_belongs v4l2_async_find_match Signed-off-by: Sakari Ailus

[PATCH v9 02/24] v4l: async: Remove re-probing support

Remove V4L2 async re-probing support. The re-probing support has been there to support cases where the sub-devices require resources provided by the main driver's hardware to function, such as clocks. Reprobing has allowed unbinding and again binding the main driver without explicilty unbinding

[PATCH 3/3] as3645a: Use integer numbers for parsing LEDs

Use integer numbers for LEDs, 0 is the flash and 1 is the indicator. Signed-off-by: Sakari Ailus --- arch/arm/boot/dts/omap3-n950-n9.dtsi | 8 ++-- drivers/leds/leds-as3645a.c | 26 -- 2 files changed, 30 insertions(+), 4

[PATCH 0/3] AS3645A fixes

Hi folks, Here are a few fixes for the as3645a DTS as well as changes in bindings. The driver is not in a release yet. I'd like to get these in as through the media tree fixes branch. Sakari Ailus (3): as3645a: Use ams,input-max-microamp as documented in DT bindings dt: bindings: as3645a:

[PATCH 1/3] as3645a: Use ams,input-max-microamp as documented in DT bindings

DT bindings document the property "ams,input-max-microamp" that limits the chip's maximum input current. The driver and the DTS however used "peak-current-limit" property. Fix this by using the property documented in DT binding documentation. Signed-off-by: Sakari Ailus

[PATCH 2/3] dt: bindings: as3645a: Use LED number to refer to LEDs

Use integers (reg property) to tell the number of the LED to the driver instead of the node name. While both of these approaches are currently used by the LED bindings, using integers will require less driver changes for ACPI support. Additionally, it will make possible LED naming using chip and

Re: [PATCH v8 03/21] v4l: async: Use more intuitive names for internal functions

On Tue 2017-09-05 16:05:35, Sakari Ailus wrote: > Rename internal functions to make the names of the functions better > describe what they do. > > Old nameNew name > v4l2_async_test_notify v4l2_async_match_notify > v4l2_async_belongs

Re: [PATCH v8 01/21] v4l: fwnode: Move KernelDoc documentation to the header

On Tue 2017-09-05 16:05:33, Sakari Ailus wrote: > In V4L2 the practice is to have the KernelDoc documentation in the header > and not in .c source code files. This consequientally makes the V4L2 > fwnode function documentation part of the Media documentation build. > > Also correct the link

[PATCH 3/3] [media] DaVinci-VPBE-Display: Adjust 12 checks for null pointers

From: Markus Elfring Date: Fri, 8 Sep 2017 14:00:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus

[PATCH 2/3] [media] DaVinci-VPBE-Display: Improve a size determination in two functions

From: Markus Elfring Date: Fri, 8 Sep 2017 10:50:32 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 1/3] [media] DaVinci-VPBE-Display: Delete an error message for a failed memory allocation in init_vpbe_layer()

From: Markus Elfring Date: Thu, 7 Sep 2017 22:37:16 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/3] [media] DaVinci-VPBE-Display: Adjustments for some function implementations

From: Markus Elfring Date: Fri, 8 Sep 2017 14:12:10 +0200 Three update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in init_vpbe_layer() Improve a size

Re: [PATCH v7 11/18] v4l: async: Register sub-devices before calling bound callback

On Sun 2017-09-03 20:49:51, Sakari Ailus wrote: > Register the sub-device before calling the notifier's bound callback. > Doing this the other way around is problematic as the struct v4l2_device > has not assigned for the sub-device yet and may be required by the bound > callback. > >

Re: [PATCH v7 1/1] dt: bindings: smiapp: Document lens-focus and flash properties

On Sun 2017-09-03 23:18:05, Sakari Ailus wrote: > Document optional lens-focus and flash properties for the smiapp driver. > > Signed-off-by: Sakari Ailus Acked-by: Pavel Machek -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures)

Re: [PATCH v3 3/6] drm/exynos/gsc: Add hardware rotation limits

On 08/09/17 07:02, Hoegeun Kwon wrote: > The gscaler has hardware rotation limits that need to be hardcoded > into driver. Distinguish them and add them to the property list. > > The hardware rotation limits are related to the cropped source size. > When swap occurs, use rot_max size instead of

Re: [PATCH v3 2/6] ARM: dts: exynos: Add clean name of compatible.

On 08/09/17 07:02, Hoegeun Kwon wrote: > Exynos 5250 and 5420 have different hardware rotation limits. However, > currently it uses only one compatible - "exynos5-gsc". Since we have > to distinguish between these two, we add different compatible. > > Signed-off-by: Hoegeun Kwon

Re: [PATCH v3 5/6] [media] exynos-gsc: Remove unnecessary compatible

On Fri, Sep 8, 2017 at 8:02 AM, Hoegeun Kwon wrote: > Currently, the compatible('samsung,exynos5-gsc') is not used. > Remove unnecessary compatible. > > Signed-off-by: Hoegeun Kwon > --- >

Re: [RFC PATCH v4 3/6] i2c: add docs to clarify DMA handling

Em Fri, 8 Sep 2017 10:56:40 +0200 Wolfram Sang escreveu: > Hi Mauro, > > thanks for your comments. Much appreciated! > > > There are also a couple of things here that Sphinx would complain. > > So, it could be worth to rename it to *.rst, while you're writing > > it, and

Re: [PATCH 00/11] drm/sun4i: add CEC support

Hi Maxime, On 07/18/17 18:29, Maxime Ripard wrote: > Hi, > > On Tue, Jul 11, 2017 at 11:06:52PM +0200, Hans Verkuil wrote: >> On 11/07/17 22:39, Maxime Ripard wrote: >>> On Tue, Jul 11, 2017 at 08:30:33AM +0200, Hans Verkuil wrote: From: Hans Verkuil This

Re: [ANN] Call for topics for the media mini-summit on Friday Oct 27 in Prague

Hi! On Fri, Sep 1, 2017 at 6:46 PM, Hans Verkuil wrote: > Hi all, > > We are organizing a media mini-summit on Friday October 27 in Prague, > co-located > with the ELCE conference: > > http://events.linuxfoundation.org/events/embedded-linux-conference-europe > > This is a

Re: [RFC PATCH v4 3/6] i2c: add docs to clarify DMA handling

Hi Mauro, thanks for your comments. Much appreciated! > There are also a couple of things here that Sphinx would complain. > So, it could be worth to rename it to *.rst, while you're writing > it, and see what: > make htmldocs > will complain and how it will look in html. OK, I'll check

Re: [PATCH v2 00/10] media: rc: gpio-ir-recv: driver update

Hi Andi, On Fri, Sep 08, 2017 at 11:21:10AM +0900, Andi Shyti wrote: > Hi Ladislav, > > > Serie was rebased on top of current linux.git, but something > > happened there and my userspace decoder no longer works: driver > > reports completely bogus timing such as (rc-5): > > ^427, _1342, ^945,

[PATCH v3 6/6] ARM: dts: exynos: Remove unnecessary compatible

Currently, the compatible('samsung,exynos5-gsc') is not used. Remove unnecessary compatible. Signed-off-by: Hoegeun Kwon --- arch/arm/boot/dts/exynos5250.dtsi | 8 arch/arm/boot/dts/exynos5420.dtsi | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-)

[PATCH v3 5/6] [media] exynos-gsc: Remove unnecessary compatible

Currently, the compatible('samsung,exynos5-gsc') is not used. Remove unnecessary compatible. Signed-off-by: Hoegeun Kwon --- Documentation/devicetree/bindings/media/exynos5-gsc.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v3 4/6] [media] exynos-gsc: Add hardware rotation limits

The hardware rotation limits of gsc depends on SOC (Exynos 5250/5420/5433). Distinguish them and add them to the driver data. Signed-off-by: Hoegeun Kwon --- drivers/media/platform/exynos-gsc/gsc-core.c | 96 1 file changed, 83

[PATCH v3 3/6] drm/exynos/gsc: Add hardware rotation limits

The gscaler has hardware rotation limits that need to be hardcoded into driver. Distinguish them and add them to the property list. The hardware rotation limits are related to the cropped source size. When swap occurs, use rot_max size instead of crop_max size. Also the scaling limits are

[PATCH v3 2/6] ARM: dts: exynos: Add clean name of compatible.

Exynos 5250 and 5420 have different hardware rotation limits. However, currently it uses only one compatible - "exynos5-gsc". Since we have to distinguish between these two, we add different compatible. Signed-off-by: Hoegeun Kwon --- arch/arm/boot/dts/exynos5250.dtsi

[PATCH v3 0/6] Exynos-gsc: Support the hardware rotation limits

Hello all, The gscaler has hardware rotation limits. So this patch set support the rotate hardware limits of gsc. To avoid problems with bisectability, patches 1~4 must be merged and then merged 5 and 6. Changes for V3: - Fixed of_match_node() to of_device_get_match_data() in drm gsc driver. -

[PATCH v3 1/6] [media] exynos-gsc: Add compatible for Exynos 5250 and 5420 specific version

Exynos 5250 and 5420 have different hardware rotation limits. Since we have to distinguish between these two, we add different compatible(samsung,exynos5250-gsc and samsung,exynos5420-gsc). Signed-off-by: Hoegeun Kwon ---