cron job: media_tree daily build: OK

This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Mon Mar 14 04:00:21 CET 2016 git branch: test git hash: da470473c9cf9c4ebb40d046b306c76427b6df94 gcc

Re: [PATCH] Add tw5864 driver

On Mon, Mar 14, 2016 at 03:55:14AM +0200, Andrey Utkin wrote: > From: Andrey Utkin > > Support for boards based on Techwell TW5864 chip which provides > multichannel video & audio grabbing and encoding (H.264, MJPEG, > ADPCM G.726). > > Signed-off-by: Andrey

Re: [PATCH] Add tw5864 driver

On Mon, Mar 14, 2016 at 03:55:14AM +0200, Andrey Utkin wrote: > --- a/include/linux/pci_ids.h > +++ b/include/linux/pci_ids.h > @@ -2333,6 +2333,7 @@ > #define PCI_VENDOR_ID_CAVIUM 0x177d > > #define PCI_VENDOR_ID_TECHWELL 0x1797 > +#define PCI_DEVICE_ID_TECHWELL_5864

Re: [PATCH] Add tw5864 driver

On Mon, 2016-03-14 at 03:59 +0200, Andrey Utkin wrote: > Support for boards based on Techwell TW5864 chip which provides > multichannel video & audio grabbing and encoding (H.264, MJPEG, > ADPCM G.726). trivia: Perhaps all the __used arrays could be const -- To unsubscribe from this list: send

[PATCH] Add tw5864 driver - cover letter

From: Andrey Utkin This is a driver for multimedia devices based on Techwell/Intersil TW5864 chip. It is basically written from scratch. There was an awful reference driver for 2.6 kernel, which is nearly million lines of code and requires half a dozen special

[PATCH] Add tw5864 driver - cover letter

This is a driver for multimedia devices based on Techwell/Intersil TW5864 chip. It is basically written from scratch. There was an awful reference driver for 2.6 kernel, which is nearly million lines of code and requires half a dozen special userspace libraries, and still doesn't quite work. So

Re: [PATCH v3 1/2] media: soc_camera: rcar_vin: add R-Car Gen 2 and 3 fallback compatibility strings

On Fri, Mar 11, 2016 at 09:04:14AM +0100, Geert Uytterhoeven wrote: > On Fri, Mar 11, 2016 at 4:25 AM, Simon Horman > wrote: > > From: Yoshihiro Kaneko > > > > Add fallback compatibility string for R-Car Gen 1 and 2. > > > > In the case of

Re: [RFT 1/2] [media] exynos4-is: Add missing endpoint of_node_put on error paths

On 11.03.2016 21:30, Sylwester Nawrocki wrote: > On 01/26/2016 01:41 AM, Krzysztof Kozlowski wrote: >> In fimc_md_parse_port_node() endpoint node is get with of_get_next_child() >> but it is not put on error path. > > "is get" doesn't sound right to me, how about rephrasing this to: > > "In

Re: [PATCH v3 06/22] media: Media Controller enable/disable source handler API

Hi Shuah, On Thu, Mar 10, 2016 at 07:29:59AM -0700, Shuah Khan wrote: > On 03/10/2016 12:35 AM, Sakari Ailus wrote: > > Hi Shuah, > > > > On Thu, Feb 11, 2016 at 04:41:22PM -0700, Shuah Khan wrote: > >> Add new fields to struct media_device to add enable_source, and > >> disable_source handlers,

Re: Fwd: Re: tw68 fails with motion package running more than 4 cameras on 8 channel card

On 03/13/2016 03:41 PM, Tony IBM-MAIN wrote: > Hans, > > Sorry for the long delay in responding. Only just got around to testing > qv4l2. > > All was well with qv4l2 on 4 camera's each capturing 25fps. Then when I > activated the 5th camera it all went pear shaped. > One camera dies, the image

Re: Kernel docs: muddying the waters a bit

Am 10.03.2016 um 16:21 schrieb Mauro Carvalho Chehab : > Em Thu, 10 Mar 2016 12:25:58 +0200 > Jani Nikula escreveu: > >> TL;DR? Skip to the last paragraph. >> >> On Wed, 09 Mar 2016, Mauro Carvalho Chehab wrote: >>> I

Fwd: Re: tw68 fails with motion package running more than 4 cameras on 8 channel card

Forwarded Message From: 07 2016 <> X-Mozilla-Status: 0001 X-Mozilla-Status2: 0080 X-Mozilla-Keys: Subject: Re: tw68 fails with motion package running more than 4 cameras on 8 channel card To: Hans Verkuil References:

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

Em Sat, 12 Mar 2016 18:48:09 -0700 Shuah Khan escreveu: > Add GFP flags to media_create_pad_link(), media_create_intf_link(), > media_devnode_create(), and media_add_link() that could get called > in atomic context to allow callers to pass in the right flags for > memory

Re: [PATCH] media: add dump_stack() if called in atomic context

Em Sat, 12 Mar 2016 17:37:05 -0700 Shuah Khan escreveu: > Change media_add_link() and media_devnode_create() to dump_stack when > called in atomic context. > > Signed-off-by: Shuah Khan > Suggested-by: Mauro Carvalho Chehab

Re: Can you look at this daily build warning?

Em Sun, 13 Mar 2016 08:59:38 +0100 Hans Verkuil escreveu: > Hi Shuah, > > I am getting this warning since commit > 840f5b0572ea9ddaca2bf5540a171013e92c97bd > (media: au0828 disable tuner to demod link in au0828_media_device_register()). > > Can you take a look? > > I'm

Re: [PATCH] media: add GFP flag to media_*() that could get called in atomic context

On Sat, Mar 12, 2016 at 06:48:09PM -0700, Shuah Khan wrote: > Add GFP flags to media_create_pad_link(), media_create_intf_link(), > media_devnode_create(), and media_add_link() that could get called > in atomic context to allow callers to pass in the right flags for > memory allocation. > >

Can you look at this daily build warning?

Hi Shuah, I am getting this warning since commit 840f5b0572ea9ddaca2bf5540a171013e92c97bd (media: au0828 disable tuner to demod link in au0828_media_device_register()). Can you take a look? I'm not sure whether the dtv_demod should just be removed or if some other action has to be taken.