cron job: media_tree daily build: OK

2018-06-06 Thread Hans Verkuil
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 Jun 7 05:00:24 CEST 2018 media-tree git hash:f2809d20b9250c675fca8268a0f6274277cca7ff media_build gi

[PATCH v4 1/2] dt-bindings: Add bindings for AKM ak7375 voice coil lens

2018-06-06 Thread bingbu . cao
From: Bingbu Cao Add device tree bindings for AKM ak7375 voice coil lens driver. This chip is used to drive a lens in a camera module. Signed-off-by: Tianshu Qiu Signed-off-by: Bingbu Cao --- Changes since v1: - add the MAINTAINERS change - correct the vendor prefix from akm to asahi-

[PATCH v4 2/2] media: ak7375: Add ak7375 lens voice coil driver

2018-06-06 Thread bingbu . cao
From: Bingbu Cao Add a v4l2 sub-device driver for the ak7375 lens voice coil. This is a voice coil module using the i2c bus to control the focus position. ak7375 can write multiple bytes of data at a time. If more data is received instead of the stop condition after receiving one byte of data, t

Re: [PATCH v2 04/10] media: imx: interweave only for sequential input/interlaced output fields

2018-06-06 Thread Steve Longerbeam
Hi Philipp, I think now I understand your interpretation of  the v4l2_field enums: SEQ_BT/TB is specifying both field order and field dominance. But the TB/BT in INTERLACED_TB/BT has a different interpretation, in this case it is specifying _only_ field dominance, and top field is first in memo

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Pavel Machek
Hi! > > > > I don't think that kind of legacy apps is in use any more. I'd prefer > > > > not to deal with them. > > > > > > In another thread ("[ANN v2] Complex Camera Workshop - Tokyo - Jun, > > > 19"), Mauro has mentioned a number of those: > > > > > > "open source ones (Camorama, Cheese, X

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Pavel Machek
Hi! > > Thanks for thread pointer... I may be able to get in using hangouts. > > > > Anyway, there's big difference between open("/dev/video0") and > > v4l2_open("/dev/video0"). I don't care about the first one, but yes we > > should be able to support the second one eventually. > > > > And I don'

Re: [PATCH] lirc.4: remove ioctls and feature bits which were never implemented

2018-06-06 Thread Sean Young
Hi Alec, On Sat, May 19, 2018 at 08:38:11AM +0200, Alec Leamas wrote: > On 18/05/18 17:25, Sean Young wrote: > > On Sun, May 06, 2018 at 12:34:53PM +0200, Michael Kerrisk (man-opages) > > wrote: > >> [CCing original author of this page] > >> > >> > >> On 04/23/2018 12:26 PM, Sean Young wrote: > >

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Mauro Carvalho Chehab
Em Wed, 6 Jun 2018 12:51:16 +0200 Pavel Machek escreveu: > > > > The scenario that I could think of is: > > > > - legacy app would call open(/dev/video?), which would be handled by > > > > libv4l open hook (v4l2_open()?), > > > > > > I don't think that kind of legacy apps is in use any more. I'

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Mauro Carvalho Chehab
Em Wed, 6 Jun 2018 12:01:50 +0200 Pavel Machek escreveu: > Hi! > > > > > Who would be calling this function? > > > > > > > > The scenario that I could think of is: > > > > - legacy app would call open(/dev/video?), which would be handled by > > > > libv4l open hook (v4l2_open()?), > > > > > >

Re: [ANN v2] Complex Camera Workshop - Tokyo - Jun, 19

2018-06-06 Thread Mauro Carvalho Chehab
Em Wed, 6 Jun 2018 13:19:39 +0900 Tomasz Figa escreveu: > On Mon, Jun 4, 2018 at 10:33 PM Mauro Carvalho Chehab > wrote: > > > > Hi all, > > > > I consolidated hopefully all comments I receive on the past announcement > > with regards to the complex camera workshop we're planning to happen in >

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Tomasz Figa
On Wed, Jun 6, 2018 at 7:51 PM Pavel Machek wrote: > > HI! > > > > > Thanks for coming up with this proposal. Please see my comments below. > > > > > > > > > Ok, can I get any comments on this one? > > > > > v4l2_open_complex("/file/with/descriptor", 0) can be used to open > > > > > whole pipeline

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Pavel Machek
HI! > > > Thanks for coming up with this proposal. Please see my comments below. > > > > > > > Ok, can I get any comments on this one? > > > > v4l2_open_complex("/file/with/descriptor", 0) can be used to open > > > > whole pipeline at once, and work if it as if it was one device. > > > > > > I'm n

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Pavel Machek
Hi! > > + while (lo < hi) { > > + int i = (lo + hi) / 2; > > + if (map->map[i].control == control) { > > + return map->map[i].fd; > > + } > > + if (map->map[i].control > control) { > > + hi =

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Pavel Machek
Hi! > > > Who would be calling this function? > > > > > > The scenario that I could think of is: > > > - legacy app would call open(/dev/video?), which would be handled by > > > libv4l open hook (v4l2_open()?), > > > > I don't think that kind of legacy apps is in use any more. I'd prefer > > not t

Re: [PATCH v2 04/10] media: imx: interweave only for sequential input/interlaced output fields

2018-06-06 Thread Philipp Zabel
Hi Steve, On Tue, 2018-06-05 at 12:00 -0700, Steve Longerbeam wrote: > > I'm probably misunderstanding you, so at the risk of overexplaining: > > There is no way we can ever produce a correct interlaced-tb frame in > > memory from a seq-bt frame output by the CSI, as the interweaving step > > only

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Tomasz Figa
On Wed, Jun 6, 2018 at 5:46 PM Pavel Machek wrote: > > Hi! > > > Thanks for coming up with this proposal. Please see my comments below. > > > > > Ok, can I get any comments on this one? > > > v4l2_open_complex("/file/with/descriptor", 0) can be used to open > > > whole pipeline at once, and work i

Re: [RFC, libv4l]: Make libv4l2 usable on devices with complex pipeline

2018-06-06 Thread Pavel Machek
Hi! > Thanks for coming up with this proposal. Please see my comments below. > > > Ok, can I get any comments on this one? > > v4l2_open_complex("/file/with/descriptor", 0) can be used to open > > whole pipeline at once, and work if it as if it was one device. > > I'm not convinced if we should

Re: [ANN v2] Complex Camera Workshop - Tokyo - Jun, 19

2018-06-06 Thread Javier Martinez Canillas
[adding Wim Taymans and Mario Limonciello to CC who said that they may also join via Hangous] On Wed, Jun 6, 2018 at 6:19 AM, Tomasz Figa wrote: > On Mon, Jun 4, 2018 at 10:33 PM Mauro Carvalho Chehab > wrote: >> >> Hi all, >> >> I consolidated hopefully all comments I receive on the past announ