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: Wed Oct 19 05:00:12 CEST 2016 media-tree git hash:43ea43b9d8b27b7acd443ec59319faa3cdb8a616 media_build

[PATCH] media: s5p-mfc collapse two error message into one

s5p_mfc_alloc_priv_buf() prints two message to report invalid memory configuration error. Collapse them into a single message. Signed-off-by: Shuah Khan --- drivers/media/platform/s5p-mfc/s5p_mfc_opr.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

Re: [PATCH v2 53/58] firewire: don't break long lines

Hi, On Oct 19 2016 05:46, Mauro Carvalho Chehab wrote: > Due to the 80-cols restrictions, and latter due to checkpatch > warnings, several strings were broken into multiple lines. This > is not considered a good practice anymore, as it makes harder > to grep for strings at the source code. > >

em28xx WinTV dualHD in Raspbian

Hi there, I am running an updated raspbian image with kernel 4.4.23-v7+, matching linux-headers-4.4.23-v7+_4.4.23-v7+-2_armhf from here: https://www.niksula.hut.fi/~mhiienka/Rpi/linux-headers-rpi/ and dvb-demod-si2168-b40-01.fw (see linuxtv-wiki). Before the last apt-get upgrade this works

[PATCH v2 39/58] hdpvr: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 41/58] pwc: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 19/58] tw68: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 16/58] saa7164: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 35/58] dvb-usb: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 37/58] em28xx: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 15/58] saa7134: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 36/58] dvb-usb-v2: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 21/58] exynos4-is: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 38/58] gspca: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 18/58] ttpci: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 17/58] solo6x10: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 25/58] s5p-mfc: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 33/58] cpia2: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 14/58] pt1: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 22/58] marvell-ccic: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 20/58] davinci: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 40/58] pvrusb2: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 26/58] c8sectpfe: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 43/58] stkwebcam: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 48/58] uvc: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 45/58] ttusb-budget: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 31/58] au0828: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 23/58] omap: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 46/58] ttusb-dec: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 42/58] siano: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 11/58] dm1105: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 10/58] ddbridge: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 44/58] tm6000: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 30/58] wl128x: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 27/58] ti-vpe: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 24/58] omap3isp: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 29/58] si4713: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 47/58] usbvision: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 12/58] ivtv: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 32/58] b2c2: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 13/58] meye: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 53/58] firewire: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 56/58] radio: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 57/58] rc: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 58/58] tuners: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 28/58] si470x: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 34/58] cx231xx: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 49/58] zr364xx: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 02/58] cx25840: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 05/58] b2c2: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 00/58] don't break long lines on strings

There are lots of drivers on media that breaks long line strings in order to fit into 80 columns. This was an usual practice to make checkpatch happy. However, it makes harder to detect where the strings are with grep. As we're right now fixing other drivers due to KERN_CONT, we need to be able

[PATCH v2 51/58] dvb-frontends: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 55/58] platform: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 08/58] cx23885: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 06/58] bt8xx: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 54/58] i2c: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 01/58] b2c2: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 07/58] cx18: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 03/58] smiapp: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 09/58] cx88: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 52/58] common: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

[PATCH v2 04/58] soc_camera: don't break long lines

Due to the 80-cols restrictions, and latter due to checkpatch warnings, several strings were broken into multiple lines. This is not considered a good practice anymore, as it makes harder to grep for strings at the source code. As we're right now fixing other drivers due to KERN_CONT, we need to

Re: [RFC 1/5] media: i2c: max2175: Add MAX2175 support

Hi Ramesh, Thank you for the patch. On Wednesday 12 Oct 2016 15:10:25 Ramesh Shanmugasundaram wrote: > This patch adds driver support for MAX2175 chip. This is Maxim > Integrated's RF to Bits tuner front end chip designed for software-defined > radio solutions. This driver exposes the tuner as a

Re: [RFC 5/5] doc_rst: media: New SDR formats SC16, SC18 & SC20

Hi Ramesh, Thank you for the patch. On Wednesday 12 Oct 2016 15:10:29 Ramesh Shanmugasundaram wrote: > This patch adds documentation for the three new SDR formats > > V4L2_SDR_FMT_SCU16BE > V4L2_SDR_FMT_SCU18BE > V4L2_SDR_FMT_SCU20BE > > Signed-off-by: Ramesh Shanmugasundaram >

Re: [PATCH v3 2/2] Add support for Omnivision OV5647

Hi! > +/* > + * A V4L2 driver for OmniVision OV5647 cameras. > + * > + * Based on Samsung S5K6AAFX SXGA 1/6" 1.3M CMOS Image Sensor driver > + * Copyright (C) 2011 Sylwester Nawrocki > + * > + * Based on Omnivision OV7670 Camera Driver > + * Copyright (C) 2006-7 Jonathan

Re: [RFC 3/5] media: platform: rcar_drif: Add DRIF support

Hello, On Tuesday 18 Oct 2016 16:29:24 Geert Uytterhoeven wrote: > On Wed, Oct 12, 2016 at 4:10 PM, Ramesh Shanmugasundaram wrote: > > This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 SoCs. > > The driver exposes each instance of DRIF as a V4L2 SDR device. A DRIF > > device

[PATCH] kernel-cmd and tabs

Hi Mauro, this patch adress the problems you reported with the kernel-cmd directive [1]. The problem was, that my nested parse didn't handled tabs well (sorry for being slow-witted this morning ;-). The patch is based on your git.linuxtv.org/mchehab/experimental.git lkml-books branch. [1]

[PATCH] doc-rst: reST-directive kernel-cmd parse with tabs

Add a 'tab-width' option to the kernel-cmd, and convert whitespace (tabs) well. The default 'tab-width' is 8. This is also a bugfix, since without this patch, tabs in command's output are not handled. Signed-off-by: Markus Heiser ---

Re: [PATCH 22/57] [media] davinci: don't break long lines

Hi Mauro, Thanks for the patch. On Fri, Oct 14, 2016 at 9:20 PM, Mauro Carvalho Chehab wrote: > Due to the 80-cols checkpatch warnings, several strings > were broken into multiple lines. This is not considered > a good practice anymore, as it makes harder to grep for >

Re: [PATCH 2/2] [media] vb2: Add support for use_dma_bidirectional queue flag

Hi Sakari, On 17/10/2016 12:06, Sakari Ailus wrote: Hi Thierry, Thanks for the set. A few comments below. On Fri, Oct 14, 2016 at 02:08:14PM +0200, Thierry Escande wrote: From: Pawel Osciak When this flag is set for CAPTURE queues by the driver on calling

Re: [PATCH v2 3/3] ARM: dts: gose: add composite video input

Hi Ulrich, (CC'ing the device tree mailing list - for real this time) Thank you for the patch. On Tuesday 18 Oct 2016 17:02:23 Ulrich Hecht wrote: > Signed-off-by: Ulrich Hecht > --- > arch/arm/boot/dts/r8a7793-gose.dts | 36 ++ >

Re: [PATCH v2 3/3] ARM: dts: gose: add composite video input

Hi Ulrich, (CC'ing the device tree mailing list) Thank you for the patch. On Tuesday 18 Oct 2016 17:02:23 Ulrich Hecht wrote: > Signed-off-by: Ulrich Hecht > --- > arch/arm/boot/dts/r8a7793-gose.dts | 36 ++ > 1 file changed, 36

Re: [PATCH 00/10] mm: adjust get_user_pages* functions to explicitly pass FOLL_* flags

On Thu 13-10-16 01:20:10, Lorenzo Stoakes wrote: > This patch series adjusts functions in the get_user_pages* family such that > desired FOLL_* flags are passed as an argument rather than implied by flags. > > The purpose of this change is to make the use of FOLL_FORCE explicit so it is > easier

Re: [PATCH v2 2/3] ARM: dts: gose: add HDMI input

Hi Ulrich, Thank you for the patch. On Tuesday 18 Oct 2016 17:02:22 Ulrich Hecht wrote: > Identical to the setup on Lager. You probably mean on Koelsch ? > Signed-off-by: Ulrich Hecht > --- > arch/arm/boot/dts/r8a7793-gose.dts | 64

Re: [PATCH v2 1/3] ARM: dts: r8a7793: Enable VIN0-VIN2

Hi Ulrich, Thank you for the patch. On Tuesday 18 Oct 2016 17:02:21 Ulrich Hecht wrote: > Signed-off-by: Ulrich Hecht Reviewed-by: Laurent Pinchart > --- > arch/arm/boot/dts/r8a7793.dtsi | 27 +++ > 1

Re: [PATCH v2 0/2] Renesas Lager/Koelsch HDMI input

Hi Ulrich, Thank you for the patches. For the whole series, Reviewed-by: Laurent Pinchart On Tuesday 18 Oct 2016 17:01:32 Ulrich Hecht wrote: > Hi! > > This series enables HDMI input on the Lager and Koelsch boards. > It sits on

RE: [RFC 3/5] media: platform: rcar_drif: Add DRIF support

Hi Rob, Thank you for the review comments. > Subject: Re: [RFC 3/5] media: platform: rcar_drif: Add DRIF support > > On Wed, Oct 12, 2016 at 03:10:27PM +0100, Ramesh Shanmugasundaram wrote: > > This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 > SoCs. > > The driver exposes

[PATCH 1/1] doc-rst: v4l: Add documentation on CSI-2 bus configuration

Document the interface between the CSI-2 transmitter and receiver drivers. Signed-off-by: Sakari Ailus --- Hi folks, We've got multiple CSI-2 tranmitter and receiver drivers currently in the kernel. Some receivers require information on dynamic bus parameters and

RE: [RFC 1/5] media: i2c: max2175: Add MAX2175 support

Hi Geert, Thank you for the review. > Subject: Re: [RFC 1/5] media: i2c: max2175: Add MAX2175 support > [...] > > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/media/i2c/max2175.txt > > @@ -0,0 +1,60 @@ > > +Maxim Integrated MAX2175 RF to Bits tuner > >

[PATCH v2 0/3] r8a7793 Gose video input support

Hi! This is a by-the-datasheet implementation of analog and digital video input on the Gose board. I have tried to address all concerns raised by reviewers, with the exception of the composite input patch, which has been left as is for now. CU Uli Changes since v1: - r8a7793.dtsi: added VIN2

[PATCH v2 2/3] ARM: dts: gose: add HDMI input

Identical to the setup on Lager. Signed-off-by: Ulrich Hecht --- arch/arm/boot/dts/r8a7793-gose.dts | 64 ++ 1 file changed, 64 insertions(+) diff --git a/arch/arm/boot/dts/r8a7793-gose.dts

[PATCH v2 1/3] ARM: dts: r8a7793: Enable VIN0-VIN2

Signed-off-by: Ulrich Hecht --- arch/arm/boot/dts/r8a7793.dtsi | 27 +++ 1 file changed, 27 insertions(+) diff --git a/arch/arm/boot/dts/r8a7793.dtsi b/arch/arm/boot/dts/r8a7793.dtsi index a7d11b9..629d3d6 100644 ---

[PATCH v2 3/3] ARM: dts: gose: add composite video input

Signed-off-by: Ulrich Hecht --- arch/arm/boot/dts/r8a7793-gose.dts | 36 1 file changed, 36 insertions(+) diff --git a/arch/arm/boot/dts/r8a7793-gose.dts b/arch/arm/boot/dts/r8a7793-gose.dts index a47ea4b..2606021 100644 ---

[PATCH v2 0/2] Renesas Lager/Koelsch HDMI input

Hi! This series enables HDMI input on the Lager and Koelsch boards. It sits on renesas-next-20161017-v4.9-rc1. I have tried to address all concerns raised by reviewers (correctly, I hope), see below for details. CU Uli Changes since v1: - modeled decoder inputs/outputs and connectors -

[PATCH v2 1/2] ARM: dts: lager: Add entries for VIN HDMI input support

From: William Towle Add DT entries for vin0, vin0_pins, and adv7612. Sets the 'default-input' property for ADV7612, enabling image and video capture without the need to have userspace specifying routing. Signed-off-by: William Towle

[PATCH v2 2/2] ARM: dts: koelsch: add HDMI input

From: Hans Verkuil Add support in the dts for the HDMI input. Based on the Lager dts patch from Ultich Hecht. Signed-off-by: Hans Verkuil [uli: removed "renesas," prefixes from pfc nodes] Signed-off-by: Ulrich Hecht

Re: [RFC 3/5] media: platform: rcar_drif: Add DRIF support

Hi Ramesh, On Wed, Oct 12, 2016 at 4:10 PM, Ramesh Shanmugasundaram wrote: > This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 SoCs. > The driver exposes each instance of DRIF as a V4L2 SDR device. A DRIF > device represents a channel

Re: [PATCH] [media] v4l: rcar-fcp: Don't force users to check for disabled FCP support

Hi Greg, On Tuesday 18 Oct 2016 16:05:21 Greg KH wrote: > On Tue, Oct 18, 2016 at 04:24:20PM +0300, Laurent Pinchart wrote: > > commit fd44aa9a254b18176ec3792a18e7de6977030ca8 upstream. > > > > The rcar_fcp_enable() function immediately returns successfully when the > > FCP device pointer is

Re: [PATCH] [media] v4l: rcar-fcp: Don't force users to check for disabled FCP support

On Tue, Oct 18, 2016 at 04:24:20PM +0300, Laurent Pinchart wrote: > commit fd44aa9a254b18176ec3792a18e7de6977030ca8 upstream. > > The rcar_fcp_enable() function immediately returns successfully when the > FCP device pointer is NULL to avoid forcing the users to check the FCP > device manually

Re: [PATCH 04/10] mm: replace get_user_pages_locked() write/force parameters with gup_flags

On Tue, Oct 18, 2016 at 02:54:25PM +0200, Jan Kara wrote: > > @@ -1282,7 +1282,7 @@ long get_user_pages(unsigned long start, unsigned > > long nr_pages, > > int write, int force, struct page **pages, > > struct vm_area_struct **vmas); > > long

Re: [PATCH v3 1/2] Add OV5647 device tree documentation

On 10/18/2016 2:14 PM, Rob Herring wrote: > On Wed, Oct 12, 2016 at 05:02:21PM +0100, Ramiro Oliveira wrote: >> Signed-off-by: Ramiro Oliveira >> --- >> .../devicetree/bindings/media/i2c/ov5647.txt | 19 >> +++ >> 1 file changed, 19 insertions(+)

[PATCH] [media] v4l: rcar-fcp: Don't force users to check for disabled FCP support

commit fd44aa9a254b18176ec3792a18e7de6977030ca8 upstream. The rcar_fcp_enable() function immediately returns successfully when the FCP device pointer is NULL to avoid forcing the users to check the FCP device manually before every call. However, the stub version of the function used when the FCP

[PATCH v2 1/1] v4l: Document that m2m devices have a file handle specific context

Memory-to-memory V4L2 devices all have file handle specific context. Say this in the API documentation so that the user space may rely on it being the case. Signed-off-by: Sakari Ailus --- since v1: - Added a note to struct v4l2_m2m_queue_ctx documentation as well.

DVB-T2 with H.265 (HEVC) ?

Hi, does anyone know (or has experiences) about a DVB-T2 device with H.265? -- Markus -- -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v3 1/2] Add OV5647 device tree documentation

On Wed, Oct 12, 2016 at 05:02:21PM +0100, Ramiro Oliveira wrote: > Signed-off-by: Ramiro Oliveira > --- > .../devicetree/bindings/media/i2c/ov5647.txt | 19 > +++ > 1 file changed, 19 insertions(+) > create mode 100644

Re: [RFC 3/5] media: platform: rcar_drif: Add DRIF support

On Wed, Oct 12, 2016 at 03:10:27PM +0100, Ramesh Shanmugasundaram wrote: > This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 SoCs. > The driver exposes each instance of DRIF as a V4L2 SDR device. A DRIF > device represents a channel and each channel can have one or two >

Re: [PATCH 04/10] mm: replace get_user_pages_locked() write/force parameters with gup_flags

On Thu 13-10-16 01:20:14, Lorenzo Stoakes wrote: > This patch removes the write and force parameters from get_user_pages_locked() > and replaces them with a gup_flags parameter to make the use of FOLL_FORCE > explicit in callers as use of this flag can result in surprising behaviour > (and >

[PATCH 1/1] v4l: Document that m2m devices have a file handle specific context

Memory-to-memory V4L2 devices all have file handle specific context. Say this in the API documentation so that the user space may rely on it being the case. Signed-off-by: Sakari Ailus --- Documentation/media/uapi/v4l/dev-codec.rst | 2 +- 1 file changed, 1

Re: [PATCH 03/10] mm: replace get_user_pages_unlocked() write/force parameters with gup_flags

On Thu 13-10-16 01:20:13, Lorenzo Stoakes wrote: > This patch removes the write and force parameters from > get_user_pages_unlocked() > and replaces them with a gup_flags parameter to make the use of FOLL_FORCE > explicit in callers as use of this flag can result in surprising behaviour > (and >

Re: [PATCH 02/10] mm: remove write/force parameters from __get_user_pages_unlocked()

On Thu 13-10-16 01:20:12, Lorenzo Stoakes wrote: > This patch removes the write and force parameters from > __get_user_pages_unlocked() to make the use of FOLL_FORCE explicit in callers > as > use of this flag can result in surprising behaviour (and hence bugs) within > the > mm subsystem. > >

  1   2   >