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: Thu Mar 30 05:00:20 CEST 2017 media-tree git hash:c3d4fb0fb41f4b5eafeee51173c14e50be12f839 media_build

Re: [PATCH 22/22] usb: document that URB transfer_buffer should be aligned

Em Thu, 30 Mar 2017 01:15:27 +0300 Laurent Pinchart escreveu: > Hi Mauro, > > Thank you for the patch. > > On Wednesday 29 Mar 2017 15:54:21 Mauro Carvalho Chehab wrote: > > Several host controllers, commonly found on ARM, like dwc2, > > require buffers that

build_media compilation issues

I'm trying to use build_media to build the media drivers, specifically usb/em28xx, for Centos7. I'm getting compile errors, see below. Can anyone help me? Kernel: $ uname -a Linux mythpbx.lan 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Errors: ...

Re: [PATCH 22/22] usb: document that URB transfer_buffer should be aligned

Hi Mauro, Thank you for the patch. On Wednesday 29 Mar 2017 15:54:21 Mauro Carvalho Chehab wrote: > Several host controllers, commonly found on ARM, like dwc2, > require buffers that are CPU-word aligned for they to work. > > Failing to do that will cause random troubles at the caller >

Re: [PATCH 1/3] [media] mceusb: RX -EPIPE (urb status = -32) lockup failure fix

On 3/29/2017 5:06 PM, Sean Young wrote: > > Anyway, you're right and this patch looks ok. It would be nice to have the > tx case handled too though. > > Thanks > Sean > Thanks; I'm looking at handling the tx case. If I can figure out the details, I'll post a new patch proposal separate, and

[GIT PULL for v4.12] Make use of refcount_t in V4L2

Hi Mauro, These patches begin using refcount_t in counting references to VB2 buffers as well as cx88 core. Please pull. The following changes since commit c3d4fb0fb41f4b5eafeee51173c14e50be12f839: [media] rc: sunxi-cir: simplify optional reset handling (2017-03-24 08:30:03 -0300) are

[PATCH v2] staging: atomisp: avoid false-positive maybe-uninitialized warning

In combination with CONFIG_PROFILE_ANNOTATED_BRANCHES=y, the unlikely() inside of the WARN() macro becomes too complex for gcc to see that we don't use the output arguments of mt9m114_to_res() are used correctly: drivers/staging/media/atomisp/i2c/mt9m114.c: In function 'mt9m114_get_fmt':

Re: [PATCH 1/3] [media] mceusb: RX -EPIPE (urb status = -32) lockup failure fix

On Tue, Mar 28, 2017 at 09:40:05PM -0400, A Sun wrote: > On 3/28/2017 4:25 PM, Sean Young wrote: > > > > >> The unused EVENT_TX_HALT and the apparently extra _kevent functions and > >> kevent_flags are necessary for a later: > >> [PATCH] [media] mceusb: TX -EPIPE lockup fix > >> ...not yet

Re: [PATCHv5 00/11] video/exynos/sti/cec: add CEC notifier & use in drivers

Hi Daniel, On 29/03/17 19:47, Daniel Vetter wrote: > On Wed, Mar 29, 2017 at 04:15:32PM +0200, Hans Verkuil wrote: >> From: Hans Verkuil >> >> This patch series adds the CEC physical address notifier code, based on >> Russell's code: >> >>

[PATCH 09/22] usb/callbacks.txt: convert to ReST and add to driver-api book

This document describe some USB core functions. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- .../callbacks.txt => driver-api/usb/callbacks.rst} | 61 +++--- Documentation/driver-api/usb/index.rst | 1 + 2 files

[PATCH 08/22] usb/bulk-streams.txt: convert to ReST and add to driver-api book

This document describe some USB core functions. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- .../bulk-streams.txt => driver-api/usb/bulk-streams.rst}| 13 + Documentation/driver-api/usb/index.rst | 1 + 2

[PATCH 10/22] usb/power-management.txt: convert to ReST and add to driver-api book

This document describe some USB core functions. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/usb/index.rst | 1 + .../usb/power-management.rst} | 403 +++-- 2 files

[PATCH 01/22] driver-api/basics.rst: add device table header

The structs there at device table are used by other documentation at the Kernel. So, add it to the driver API. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/basics.rst | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 19/22] usb: composite.h: fix two warnings when building docs

By definition, we use /* private: */ tag when we won't be documenting a parameter. However, those two parameters are documented: ./include/linux/usb/composite.h:510: warning: Excess struct/union/enum/typedef member 'setup_pending' description in 'usb_composite_dev'

[PATCH 05/22] writing_usb_driver.rst: Enrich its ReST representation

The pandoc conversion is not perfect. Do handwork in order to: - add a title to this chapter; - adjust function and struct references; - use monospaced fonts for C code names; - some other minor adjustments to make it better to read in text mode and in html. Signed-off-by: Mauro Carvalho

[PATCH 21/22] docs-rst: fix usb cross-references

As some USB documentation files got moved, adjust their cross-references to their new place. Signed-off-by: Mauro Carvalho Chehab --- Documentation/ABI/stable/sysfs-bus-usb| 2 +- Documentation/driver-api/usb/URB.rst | 2 ++

[PATCH 16/22] usb/gadget.rst: remove unused kernel-doc tags

The DocBook file used to have "!E" include tags for usb gadget functions. However, there's nothing there to be documented: ./drivers/usb/gadget/function/f_acm.c:1: warning: no structured comments found ./drivers/usb/gadget/function/f_ecm.c:1: warning: no structured comments

[PATCH 13/22] usb/hotplug.txt: convert to ReST and add to driver-api book

This document describe some USB core features. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- .../hotplug.txt => driver-api/usb/hotplug.rst} | 66 -- Documentation/driver-api/usb/index.rst | 1 + 2 files

[PATCH 11/22] usb/dma.txt: convert to ReST and add to driver-api book

This document describe some USB core features. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- .../{usb/dma.txt => driver-api/usb/dma.rst}| 51 -- Documentation/driver-api/usb/index.rst | 1 + 2 files

[PATCH 04/22] gadget.rst: Enrich its ReST representation and add kernel-doc tag

The pandoc conversion is not perfect. Do handwork in order to: - add a title to this chapter; - use the proper warning and note markups; - use kernel-doc to include Kernel header and c files; - remove legacy notes with regards to DocBook; - some other minor adjustments to make it better to read

[PATCH 15/22] usb/URB.txt: convert to ReST and update it

The URB doc describes the Kernel mechanism that do USB transfers. While the functions are already described at urb.h, there are a number of concepts and theory that are important for USB driver developers. Convert it to ReST and use C ref links to point to the places at usb.h where each function

[PATCH 18/22] usb: get rid of some ReST doc build errors

We need an space before a numbered list to avoid those warnings: ./drivers/usb/core/message.c:478: ERROR: Unexpected indentation. ./drivers/usb/core/message.c:479: WARNING: Block quote ends without a blank line; unexpected unindent. ./include/linux/usb/composite.h:455: ERROR: Unexpected

[PATCH 12/22] error-codes.rst: convert to ReST and add to driver-api book

This document describe some USB core features. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/usb/error-codes.rst | 205 +++ Documentation/driver-api/usb/index.rst | 1 +

[PATCH 06/22] writing_musb_glue_layer.rst: Enrich its ReST representation

This file is actually quite complex, and required several manual handwork: - add a title for the document; - use the right tags for monospaced fonts; - use c references where needed; - adjust cross-reference to writing_usb_driver.rst - hightlight cross-referenced lines. With regards to C code

[PATCH 03/22] usb.rst: Enrich its ReST representation

- use the proper warning and note markups; - add references for parts of the document that will be cross-referenced on other USB docs; - some minor adjustments to make it better to read in text mode and in html. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 17/22] usb.rst: get rid of some Sphinx errors

Get rid of those warnings: Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name: "usb_type". Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name: "usb_dir". Documentation/driver-api/usb/usb.rst:615: ERROR: Unknown target name: "usb_recip".

[PATCH 14/22] usb/persist.txt: convert to ReST and add to driver-api book

This document describe some USB core features. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- Documentation/driver-api/usb/index.rst | 1 + .../persist.txt => driver-api/usb/persist.rst} | 22 +- 2 files

[PATCH 22/22] usb: document that URB transfer_buffer should be aligned

Several host controllers, commonly found on ARM, like dwc2, require buffers that are CPU-word aligned for they to work. Failing to do that will cause random troubles at the caller drivers, causing them to fail. Document it. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 07/22] usb/anchors.txt: convert to ReST and add to driver-api book

This document describe some USB core functions. Add it to the driver-api book. Signed-off-by: Mauro Carvalho Chehab --- .../anchors.txt => driver-api/usb/anchors.rst} | 36 -- Documentation/driver-api/usb/index.rst | 1 + 2 files

[PATCH 20/22] usb: gadget.h: be consistent at kernel doc macros

There's one value that use spaces instead of tabs to ident. That causes the following warning: ./include/linux/usb/gadget.h:193: ERROR: Unexpected indentation. Signed-off-by: Mauro Carvalho Chehab --- include/linux/usb/gadget.h | 2 +- 1 file changed, 1 insertion(+),

Re: [PATCH RFC] dwc2: Don't assume URB transfer_buffer are dword-aligned

Em Wed, 29 Mar 2017 11:57:22 +0200 Greg Kroah-Hartman escreveu: > On Tue, Mar 28, 2017 at 06:48:02AM -0300, Mauro Carvalho Chehab wrote: > > Em Fri, 17 Mar 2017 10:24:15 +0900 > > Greg Kroah-Hartman escreveu: > > > > > On Thu, Mar 16,

Re: dvb-tools: dvbv5-scan segfaults with DVB-T2 HD service that just started in Germany

Hello Mauro & list, could you please have a look at the dvbv5-scan crash report below? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859008 Is there anything else you need to debug this? Thanks, Gregor On 3/29/17 4:42 PM, Tino Mettler wrote: > > $ gdb --args ./utils/dvb/dvbv5-scan

Re: [PATCHv5 00/11] video/exynos/sti/cec: add CEC notifier & use in drivers

On Wed, Mar 29, 2017 at 04:15:32PM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > This patch series adds the CEC physical address notifier code, based on > Russell's code: > > https://patchwork.kernel.org/patch/9277043/ > > It adds support for it to the exynos_hdmi

Re: [PATCH v2] staging: media: atomisp: Fix style. remove space before ',' and convert to tabs.

On Wed, 2017-03-29 at 09:57 -0700, Daniel Cashman wrote: > From: Dan Cashman > > Signed-off-by: Dan Cashman As the TODO asks - please no whitespace cleanups yet. They make it harder to keep other cleanups that fix (or mostly remove) code

[PATCH v2] staging: media: atomisp: Fix style. remove space before ',' and convert to tabs.

From: Dan Cashman Signed-off-by: Dan Cashman --- drivers/staging/media/atomisp/i2c/ap1302.c | 4 ++-- drivers/staging/media/atomisp/i2c/gc0310.c | 2 +- drivers/staging/media/atomisp/i2c/gc2235.c | 2 +- 3 files changed, 4 insertions(+), 4

[PATCH v3 12/13] [media] ddbridge: add i2c_read_regs()

From: Daniel Scheller Adds new i2c_read_regs() function and make i2c_read_reg() wrap into this with len=1. Required for the tuner_tda18212_ping() and XO2 handling functions (part of the Sony CXD28xx support patch series). Signed-off-by: Daniel Scheller

[PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware

From: Daniel Scheller Third iteration of the DD CineCTv6/FlexCT support patches with mostly all things cleaned up that popped up so far. Obsoletes V1 and V2 series. These patches enhance the functionality of dvb-frontends/stv0367 to work with Digital Devices hardware driven

[PATCH v3 09/13] [media] dvb-frontends/stv0367: fix symbol rate conditions in cab_SetQamSize()

From: Daniel Scheller The values used for comparing symbol rates and the resulting conditional reg writes seem wrong (rates multiplied by ten), so fix those values. While this doesn't seem to influence operation, it should be fixed anyway. Signed-off-by: Daniel Scheller

[PATCH v3 10/13] [media] dvb-frontends/stv0367: add defaults for use w/DD-branded devices

From: Daniel Scheller Digital Devices uses defaults tables in their stv0367dd demod driver variant which differ in a few registers, at least enough that no stable operation can be provided with the tables already present in the driver (init succeeds and DVB reception works

[PATCH v3 13/13] [media] ddbridge: support STV0367-based cards and modules

From: Daniel Scheller This adds detection and activation for STV0367-based tuner hardware (namely CineCTv6 bridge cards and older DuoFlex CT addon modules). Utilises the extended stv0367 demod driver. TDA18212 i2c_client/regmap-api code was originally implemented by Antti

[PATCH v3 04/13] [media] dvb-frontends/stv0367: move out tables, support multiple tab variants

From: Daniel Scheller Move the *ter and *cab st_register tables into a separate header file and additionally organize them via a multidimensional array, allowing to add more tables with differing init values, and also prepare for a base init table which should contain general

[PATCH v3 06/13] [media] dvb-frontends/stv0367: make full reinit on set_frontend() optional

From: Daniel Scheller Every time dvb_frontend_ops.set_frontend() is called, an almost full reinit of the demodulator will be performed. While this might cause a slight delay when switching channels due to all involved tables being rewritten, it can even be dangerous in

[PATCH v3 11/13] [media] dvb-frontends/stv0367: add Digital Devices compatibility

From: Daniel Scheller This - in conjunction with the previous changes - makes it possible to use the STV0367 DVB-C/T demodulator driver with Digital Devices hardware having this demodulator soldered on them (namely CineCTv6 bridges and some earlier DuoFlex CT addon modules).

[PATCH v3 01/13] [media] dvb-frontends/stv0367: add flag to make i2c_gatectrl optional

From: Daniel Scheller Some hardware and bridges (namely ddbridge) require that tuner access is limited to one concurrent access and wrap i2c gate control with a mutex_lock when attaching frontends. According to vendor information, this is required as concurrent tuner

[PATCH v3 02/13] [media] dvb-frontends/stv0367: print CPAMP status only if stv_debug is enabled

From: Daniel Scheller The CPAMP log lines generated in stv0367_ter_check_cpamp() are printed everytime tuning succeeds or fails, quite cluttering the normal kernel log. Use dprintk() instead of printk(KERN_ERR...) so that if the information is needed, it'll be printed when

[PATCH v3 08/13] [media] dvb-frontends/stv0367: selectable QAM FEC Lock status register

From: Daniel Scheller In some configurations (due to different PIN config, wiring or so), the QAM FECLock might be signalled using a different register than F367CAB_QAMFEC_LOCK (e.g. F367CAB_DESCR_SYNCSTATE on Digital Devices hw), so make that register selectable.

[PATCH v3 03/13] [media] dvb-frontends/stv0367: refactor defaults table handling

From: Daniel Scheller Change defaults table writing so tables can be of dynamic length without having to keep track of their lengths by adding and evaluating an end marker (reg 0x), also move table writing to a dedicated function to remove code duplication. Additionally

[PATCH v3 07/13] [media] dvb-frontends/stv0367: support reading if_khz from tuner config

From: Daniel Scheller Currently, if_khz is set and provided using the configuration var in struct stv0367_config. However, in some constellations, the value might be different for differing channel bandwidths or even -T and -C operation. When e.g. used in conjunction with

[PATCH v3 05/13] [media] dvb-frontends/stv0367: make PLLSETUP a function, add 58MHz IC speed

From: Daniel Scheller This moves the PLL SETUP code from stv0367ter_init() into a dedicated function, and also make it possible to configure 58Mhz IC speed at 27MHz Xtal (used on STV0367-based DDB cards/modules in QAM mode). Signed-off-by: Daniel Scheller

Re: [PATCHv5 00/11] video/exynos/sti/cec: add CEC notifier & use in drivers

2017-03-29 16:15 GMT+02:00 Hans Verkuil : > From: Hans Verkuil > > This patch series adds the CEC physical address notifier code, based on > Russell's code: > > https://patchwork.kernel.org/patch/9277043/ > > It adds support for it to the exynos_hdmi

[PATCHv5.1 03/11] cec: integrate CEC notifier support

Support the CEC notifier framework, simplifying drivers that depend on this. Signed-off-by: Hans Verkuil Tested-by: Marek Szyprowski --- Accidentally removed adap->notifier causing this to fail. Fixed this stupid mistake. ---

[RESEND PATCH] staging: media: davinci_vpfe: Replace a bit shift

This patch replaces bit shifting on 1 with the BIT(x) macro. This was done with coccinelle: @@ constant c; @@ -1 << c +BIT(c) Signed-off-by: Arushi Singhal --- drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 2 +-

[RESEND PATCH] staging: media: omap4iss: Replace a bit shift by a use of BIT

This patch replaces bit shifting on 1 with the BIT(x) macro. This was done with coccinelle: @@ constant c; @@ -1 << c +BIT(c) Signed-off-by: Arushi Singhal --- drivers/staging/media/omap4iss/iss_csi2.c| 2 +- drivers/staging/media/omap4iss/iss_ipipe.c | 2

[PATCHv5 04/11] exynos_hdmi: add CEC notifier support

From: Hans Verkuil Implement the CEC notifier support to allow CEC drivers to be informed when there is a new physical address. Signed-off-by: Hans Verkuil Tested-by: Marek Szyprowski ---

[PATCHv5 01/11] cec-edid: rename cec_get_edid_phys_addr

From: Hans Verkuil Rename cec_get_edid_phys_addr to cec_get_raw_edid_phys_addr. Add a new cec_get_edid_phys_addr function that takes a struct edid pointer. This reflects the fact that some drivers have a struct edid pointer and others a u8 pointer to the raw edid data.

[PATCHv5 02/11] media: add CEC notifier support

From: Hans Verkuil Add support for CEC notifiers, which is used to convey CEC physical address information from video drivers to their CEC counterpart driver(s). Based on an earlier version from Russell King: https://patchwork.kernel.org/patch/9277043/ The cec_notifier

[PATCHv5 07/11] s5p-cec: add cec-notifier support, move out of staging

From: Hans Verkuil By using the CEC notifier framework there is no longer any reason to manually set the physical address. This was the one blocking issue that prevented this driver from going out of staging, so do this move as well. Update the bindings documenting the

[PATCHv5 06/11] s5p-cec.txt: document the HDMI controller phandle

From: Hans Verkuil Update the bindings documenting the new hdmi phandle. Signed-off-by: Hans Verkuil CC: linux-samsung-...@vger.kernel.org CC: devicet...@vger.kernel.org CC: Krzysztof Kozlowski ---

[PATCHv5 05/11] ARM: dts: exynos: add HDMI controller phandle to exynos4.dtsi

From: Hans Verkuil Add the new hdmi phandle to exynos4.dtsi. This phandle is needed by the s5p-cec driver to initialize the CEC notifier framework. Tested with my Odroid U3. Signed-off-by: Hans Verkuil Tested-by: Marek Szyprowski

[PATCHv5 03/11] cec: integrate CEC notifier support

From: Hans Verkuil Support the CEC notifier framework, simplifying drivers that depend on this. Signed-off-by: Hans Verkuil Tested-by: Marek Szyprowski --- drivers/media/cec/cec-core.c | 21 +

[PATCHv5 09/11] stih-cec.txt: document new hdmi phandle

From: Benjamin Gaignard Update the bindings documentation with the new hdmi phandle. Signed-off-by: Benjamin Gaignard Signed-off-by: Hans Verkuil Acked-by: Rob Herring CC:

[PATCHv5 08/11] sti: hdmi: add CEC notifier support

From: Benjamin Gaignard Implement the CEC notifier support to allow CEC drivers to be informed when there is a new physical address. Signed-off-by: Benjamin Gaignard Signed-off-by: Hans Verkuil ---

[PATCHv5 10/11] stih-cec: add CEC notifier support

From: Benjamin Gaignard By using the CEC notifier framework there is no longer any reason to manually set the physical address. This was the one blocking issue that prevented this driver from going out of staging, so do this move as well. Signed-off-by: Benjamin

[PATCHv5 11/11] arm: sti: update sti-cec for CEC notifier support

From: Benjamin Gaignard To use CEC notifier sti CEC driver needs to get phandle of the hdmi device. Signed-off-by: Benjamin Gaignard Signed-off-by: Hans Verkuil CC: devicet...@vger.kernel.org ---

[PATCHv5 00/11] video/exynos/sti/cec: add CEC notifier & use in drivers

From: Hans Verkuil This patch series adds the CEC physical address notifier code, based on Russell's code: https://patchwork.kernel.org/patch/9277043/ It adds support for it to the exynos_hdmi drm driver, adds support for it to the CEC framework and finally adds support

Re: [PATCHv6 11/14] ov2640: convert from soc-camera to a standard subdev sensor driver.

Y're welcome, thanks Hans for this work, this allows us to drop our camera interface driver directly based on subdev. BR, Hugues. On 03/29/2017 03:44 PM, Hans Verkuil wrote: > On 29/03/17 15:42, Hugues FRUCHET wrote: >> Acked-by: Hugues Fruchet >> >> Tested successfully

Re: [PATCHv6 11/14] ov2640: convert from soc-camera to a standard subdev sensor driver.

On 29/03/17 15:42, Hugues FRUCHET wrote: > Acked-by: Hugues Fruchet > > Tested successfully on STM324x9I-EVAL evaluation board embedding > an OV2640 camera sensor. > > I don't understand the comment around s_power op that has been dropped > (it is there in code), and no

Re: [PATCHv6 12/14] ov2640: use standard clk and enable it.

Acked-by: Hugues Fruchet Tested successfully on STM324x9I-EVAL evaluation board embedding an OV2640 camera sensor. BR, Hugues. On 03/28/2017 10:23 AM, Hans Verkuil wrote: > From: Hans Verkuil > > Convert v4l2_clk to normal clk and enable the

Re: [PATCHv6 11/14] ov2640: convert from soc-camera to a standard subdev sensor driver.

Acked-by: Hugues Fruchet Tested successfully on STM324x9I-EVAL evaluation board embedding an OV2640 camera sensor. I don't understand the comment around s_power op that has been dropped (it is there in code), and no problem is observed doing several open/close, tell me

[PATCH v1 4/8] ARM: dts: stm32: Enable DCMI camera interface on STM32F429-EVAL board

Signed-off-by: Hugues Fruchet --- arch/arm/boot/dts/stm32429i-eval.dts | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index 3c99466..87733d3 100644 ---

[PATCH v1 8/8] ARM: configs: stm32: DCMI + OV2640 camera support

Enable DCMI camera interface and OV2640 camera sensor drivers. Signed-off-by: Hugues Fruchet --- arch/arm/configs/stm32_defconfig | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index

[PATCH v1 3/8] ARM: dts: stm32: Enable DCMI support on STM32F429 MCU

Signed-off-by: Hugues Fruchet --- arch/arm/boot/dts/stm32f429.dtsi | 37 + 1 file changed, 37 insertions(+) diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi index ee0da97..e1ff978 100644 ---

[PATCH v1 5/8] ARM: dts: stm32: Enable stmpe1600 gpio expandor of STM32F429-EVAL board

Signed-off-by: Hugues Fruchet --- arch/arm/boot/dts/stm32429i-eval.dts | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index 87733d3..7ffcf07 100644 ---

[PATCH v1 1/8] dt-bindings: Document STM32 DCMI bindings

This adds documentation of device tree bindings for the STM32 DCMI (Digital Camera Memory Interface). Signed-off-by: Hugues Fruchet --- .../devicetree/bindings/media/st,stm32-dcmi.txt| 77 ++ 1 file changed, 77 insertions(+) create mode 100644

[PATCH v1 7/8] ARM: configs: stm32: stmpe 1600 GPIO expandor

Enable STMPE1600 GPIO expandor. Signed-off-by: Hugues Fruchet --- arch/arm/configs/stm32_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index a9d8e3c..84adc88 100644 ---

[PATCH v1 0/8] Add support for DCMI camera interface of STMicroelectronics STM32 SoC series

This patchset introduces a basic support for Digital Camera Memory Interface (DCMI) of STMicroelectronics STM32 SoC series. This first basic support implements RGB565 & YUV frame grabbing. Cropping and JPEG support will be added later on. This has been tested on STM324x9I-EVAL evaluation board

Re: [PATCH 0/3] Handling of reduced FPS in V4L2

Hi Hans, On 28-03-2017 11:07, Hans Verkuil wrote: > On 27/03/17 13:58, Jose Abreu wrote: >> Hi Hans, >> >> >> On 24-03-2017 12:28, Hans Verkuil wrote: >>> On 03/24/17 13:21, Jose Abreu wrote: Hi Hans, On 24-03-2017 12:12, Hans Verkuil wrote: > On 03/24/17 12:52, Jose

[PATCH v1 6/8] ARM: dts: stm32: Enable ov2640 camera support of STM32F429-EVAL board

Signed-off-by: Hugues Fruchet --- arch/arm/boot/dts/stm32429i-eval.dts | 30 ++ 1 file changed, 30 insertions(+) diff --git a/arch/arm/boot/dts/stm32429i-eval.dts b/arch/arm/boot/dts/stm32429i-eval.dts index 7ffcf07..b7d127c 100644 ---

[PATCH v1 2/8] [media] stm32-dcmi: STM32 DCMI camera interface driver

This V4L2 subdev driver enables Digital Camera Memory Interface (DCMI) of STMicroelectronics STM32 SoC series. Signed-off-by: Yannick Fertre Signed-off-by: Hugues Fruchet --- drivers/media/platform/Kconfig| 12 +

Re: [PATCH RFC] [media] m5mols: add missing dependency on VIDEO_IR_I2C

On Wed, Mar 29, 2017 at 11:56:08AM +0200, Sylwester Nawrocki wrote: > On 12/13/2016 06:44 AM, Nicholas Mc Guire wrote: > >The Depends on: tag in Kconfig for CONFIG_VIDEO_M5MOLS does not list > >VIDEO_IR_I2C so Kconfig displays the dependencies needed so the M-5MOLS > >driver can not be found. > >

Re: [PATCH RFC] [media] m5mols: add missing dependency on VIDEO_IR_I2C

On 12/13/2016 06:44 AM, Nicholas Mc Guire wrote: The Depends on: tag in Kconfig for CONFIG_VIDEO_M5MOLS does not list VIDEO_IR_I2C so Kconfig displays the dependencies needed so the M-5MOLS driver can not be found. Fixes: commit cb7a01ac324b ("[media] move i2c files into drivers/media/i2c")

Re: [RFC PATCHv2 00/21] Ion clean in preparation for moving out of staging

2017-03-18 1:54 GMT+01:00 Laura Abbott : > > Hi, > > This is v2 of the series to do some serious Ion clean up in preparation for > moving out of staging. I got good feedback last time so this series mostly > attempts to address that feedback and do more still more cleanup.

Re: [RFC PATCHv2 02/21] cma: Introduce cma_for_each_area

2017-03-18 1:54 GMT+01:00 Laura Abbott : > > Frameworks (e.g. Ion) may want to iterate over each possible CMA area to > allow for enumeration. Introduce a function to allow a callback. even outside ION rework that could be useful Reviewed-by: Benjamin Gaignard

Re: [PATCH v7] [media] vimc: Virtual Media Controller core, capture and sensor

Hi Hans, On Wed, Mar 29, 2017 at 09:49:05AM +0200, Hans Verkuil wrote: > On 28/03/17 22:37, Sakari Ailus wrote: > > Hi Mauro, > > > > On Tue, Mar 28, 2017 at 08:38:26AM -0300, Mauro Carvalho Chehab wrote: > >> Em Tue, 28 Mar 2017 12:00:36 +0200 > >> Hans Verkuil escreveu: >

Re: [PATCH v6 02/39] [media] dt-bindings: Add bindings for i.MX media driver

On Tue, Mar 28, 2017 at 07:21:34PM -0500, Rob Herring wrote: > On Mon, Mar 27, 2017 at 7:40 PM, Steve Longerbeam > wrote: > > Add bindings documentation for the i.MX media driver. > > > > Signed-off-by: Steve Longerbeam > > --- > >

Re: [PATCH v7] [media] vimc: Virtual Media Controller core, capture and sensor

On 29/03/17 00:35, Nicolas Dufresne wrote: > > > Le 28 mars 2017 4:38 PM, "Sakari Ailus" > a écrit : > > Hi Mauro, > > On Tue, Mar 28, 2017 at 08:38:26AM -0300, Mauro Carvalho Chehab wrote: > > Em Tue, 28 Mar 2017 12:00:36 +0200 >

[PATCH] video.rst: a sensor is also considered to be a physical input

Add the line "Camera sensors are also considered to be a video input." In practice all non-MC drivers for sensors support the input ioctls, and the compliance test actually tests for the presence of these ioctls. So clarify the documentation by explicitly mentioning sensors. Signed-off-by: Hans

[PATCH] dev-capture.rst/dev-output.rst: video standards ioctls are optional

The documentation for video capture and output devices claims that the video standard ioctls are required. This is not the case, they are only required for PAL/NTSC/SECAM type inputs and outputs. Sensors do not implement this at all and e.g. HDMI inputs implement the DV Timings ioctls. Just

[PATCH v3] [media] staging: css2400: fix checkpatch error

isp_capture_defs.h: clean up ERROR: Macros with complex values should be enclosed in parentheses Signed-off-by: Haim Daniel --- .../pci/atomisp2/css2400/css_2401_csi2p_system/hrt/isp_capture_defs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v7] [media] vimc: Virtual Media Controller core, capture and sensor

On 28/03/17 22:37, Sakari Ailus wrote: > Hi Mauro, > > On Tue, Mar 28, 2017 at 08:38:26AM -0300, Mauro Carvalho Chehab wrote: >> Em Tue, 28 Mar 2017 12:00:36 +0200 >> Hans Verkuil escreveu: >> >>> On 27/03/17 20:09, Mauro Carvalho Chehab wrote: Em Mon, 27 Mar 2017

Re: [PATCH v7] [media] vimc: Virtual Media Controller core, capture and sensor

On 28/03/17 16:23, Sakari Ailus wrote: > Hi Hans, > > On Tue, Mar 28, 2017 at 12:00:36PM +0200, Hans Verkuil wrote: >> On 27/03/17 20:09, Mauro Carvalho Chehab wrote: >>> Em Mon, 27 Mar 2017 12:19:51 -0300 >>> Helen Koike escreveu: >>> Hi Sakari, On

Re: [PATCH]: staging: media: css2400: fix checkpatch error

On Wed, Mar 29, 2017 at 08:36:27AM +0300, Haim Daniel wrote: > >From 41d35b455f8eb139912909639e914469ef5e06fb Mon Sep 17 00:00:00 2001 > From: Haim Daniel > Date: Tue, 28 Mar 2017 19:27:57 +0300 > Subject: [PATCH] [media] staging: css2400: fix checkpatch error > >

Re: [PATCH v3] Revert "staging: radio-bcm2048: fixed bare use of unsigned int"

On Mon, Mar 27, 2017 at 05:20:29PM +1100, Eddie Youseph wrote: > This reverts previous changes to checkpatch warning: > WARNING: Prefer 'unsigned int' to bare use of 'unsigned' > --- > Changes in v2: > - Added changelog > > Changes in v3: > - Revert changes to using bare unsigned I

Re: [PATCH v2] [media] staging: css2400: fix checkpatch error

On Wed, Mar 29, 2017 at 10:12:28AM +0300, Haim Daniel wrote: > isp_capture_defs.h: What is this line for? > fix checkpatch ERROR: Trailing whitespace? > Macros with complex values should be enclosed in parentheses > > Signed-off-by: Haim Daniel > --- >

[PATCH v2] [media] staging: css2400: fix checkpatch error

isp_capture_defs.h: fix checkpatch ERROR: Macros with complex values should be enclosed in parentheses Signed-off-by: Haim Daniel --- .../pci/atomisp2/css2400/css_2401_csi2p_system/hrt/isp_capture_defs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] Remove atomisp/i2c style errors.

On Tue, Mar 28, 2017 at 08:31:37PM -0700, Daniel Cashman wrote: > From: Dan Cashman Please list what the issue you fixed in the subject line. Also change the subject to match others for this driver, a 'git log' will show you what to do there. > > Remove two ' , '

Re: [PATCH] staging: media: atomisp: i2c: removed unnecessary white space before comma in memset()

On Tue, Mar 28, 2017 at 11:02:45AM +0530, vaibhavd...@gmail.com wrote: > From: Vaibhav Kothari > > Removed extra space before comma in memset() as a part of > checkpatch.pl fix-up. > > Signed-off-by: Vaibhav Kothari > --- >