Re: [PATCH 03/16] rcar-vin: fix how pads are handled for v4l2 subdevice operations

Hello! On 3/14/2017 9:59 PM, Niklas Söderlund wrote: The rcar-vin driver only uses one pad, pad number 0. - All v4l2 operations that did not check that the requested operation was for pad 0 have been updated with a check to enforce this. - All v4l2 operations that stored (and later

Re: media / v4l2-mc: wishlist for complex cameras (was Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline)

On Tue, Mar 14, 2017 at 09:54:31PM -0300, Mauro Carvalho Chehab wrote: > Em Tue, 14 Mar 2017 23:32:54 +0100 > Pavel Machek escreveu: > > > > > Well, I believe first question is: what applications would we want to > > run on complex devices? Will sending control from video to

[PATCH v2 05/14] [media] rc: sunxi-cir: simplify optional reset handling

As of commit bb475230b8e5 ("reset: make optional functions really optional"), the reset framework API calls use NULL pointers to describe optional, non-present reset controls. This allows to return errors from devm_reset_control_get_optional and to call reset_control_(de)assert unconditionally.

[PATCH v2 00/15] Exynos MFC v6+ - remove the need for the reserved memory

Hi, After testing these patches, encoding using MFC fails when requesting buffers for capture (it works for output) with ENOMEM (it complains it cannot allocate memory on bank1). Did anyone else test encoding? Thanks, Marian Either I've been missing something or nothing has been going on. (K.

Re: [PATCH v3 06/27] rcar-vin: move max width and height information to chip information

On 3/14/2017 10:02 PM, Niklas Söderlund wrote: On Gen3 the max supported width and height will be different from Gen2. Move the limits to the struct chip_info to prepare for Gen3 support. Maybe rvin_info? Signed-off-by: Niklas Söderlund ---

[PATCH] [media] doc: kapi: fix typo

Signed-off-by: Baruch Siach --- Documentation/media/kapi/v4l2-core.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/media/kapi/v4l2-core.rst b/Documentation/media/kapi/v4l2-core.rst index e9677150ed99..d8f6c46d26d5 100644 ---

Re: [PATCH v2 00/15] Exynos MFC v6+ - remove the need for the reserved memory

Thanks for the quick reply. Decoding works without issues for me too. I did not change the CMA size or used s5p_mfc.mem parameter. However, according to the Marek, the default 8M should be enough for 3 instances of H264 encoders/decoders. My test was encoding a 30 seconds 720p clip, so I

Re: [RFC][PATCH] dma-buf: Introduce dma-buf test module

On Tue, Mar 14, 2017 at 01:30:30PM -0700, Laura Abbott wrote: > On 03/14/2017 01:13 PM, Daniel Vetter wrote: > > On Tue, Mar 14, 2017 at 01:04:19PM -0700, Laura Abbott wrote: > >> > >> dma-buf is designed to share buffers. Sharing means that there needs to > >> be another subsystem to accept those

[PATCH v2 04/14] [media] st_rc: simplify optional reset handling

As of commit bb475230b8e5 ("reset: make optional functions really optional"), the reset framework API calls use NULL pointers to describe optional, non-present reset controls. This allows to return errors from reset_control_get_optional and to call reset_control_(de)assert unconditionally.

Re: [PATCH v2 00/15] Exynos MFC v6+ - remove the need for the reserved memory

Hello Marian, On Wed, Mar 15, 2017 at 8:36 AM, Marian Mihailescu wrote: > Hi, > > After testing these patches, encoding using MFC fails when requesting > buffers for capture (it works for output) with ENOMEM (it complains it > cannot allocate memory on bank1). > Did

Re: [PATCH 03/16] rcar-vin: fix how pads are handled for v4l2 subdevice operations

Hi Sergei, Thanks for your feedback. On 2017-03-15 12:12:21 +0300, Sergei Shtylyov wrote: > Hello! > > On 3/14/2017 9:59 PM, Niklas Söderlund wrote: > > > The rcar-vin driver only uses one pad, pad number 0. > > > > - All v4l2 operations that did not check that the requested operation > >

Re: [PATCH 01/16] rcar-vin: reset bytesperline and sizeimage when resetting format

Hello! On 3/14/2017 9:59 PM, Niklas Söderlund wrote: These two where forgotten when refactoring the format reset code. If s/where/were/? they are not also reset at the same time as width and height the format returned from G_FMT will not match reality. Signed-off-by: Niklas Söderlund

[PATCH v2 03/14] [media] coda: simplify optional reset handling

As of commit bb475230b8e5 ("reset: make optional functions really optional"), the reset framework API calls use NULL pointers to describe optional, non-present reset controls. This allows to return errors from devm_reset_control_get_optional without special cases and to call reset_control_reset

Re: [PATCH v2 00/15] Exynos MFC v6+ - remove the need for the reserved memory

Hello Marian, On Wed, Mar 15, 2017 at 9:00 AM, Marian Mihailescu wrote: > Thanks for the quick reply. > > Decoding works without issues for me too. > I did not change the CMA size or used s5p_mfc.mem parameter. However, > according to the Marek, the default 8M should be

Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Em Fri, 27 Jan 2017 13:54:57 -0800 Eric Anholt escreveu: > Here's my first pass at importing the camera driver. There's a bunch > of TODO left to it, most of which is documented, and the rest being > standard checkpatch fare. > > Unfortunately, when I try modprobing it on my

Re: [PATCH v3 4/7] macintosh: Only descend into directory when CONFIG_MACINTOSH_DRIVERS is set

"Andrew F. Davis" writes: > When CONFIG_MACINTOSH_DRIVERS is not set make will still descend into the > macintosh directory but nothing will be built. This produces unneeded > build artifacts and messages in addition to slowing the build. > Fix this here. > > Signed-off-by: Andrew

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 16 05:00:15 CET 2017 media-tree git hash:700ea5e0e0dd70420a04e703ff264cc133834cba media_build

Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

On Wed, 2017-03-15 at 22:08 -0300, Mauro Carvalho Chehab wrote: > No, I didn't. Thanks! Applied it but, unfortunately, didn't work. > Perhaps I'm missing some other patch. I'm compiling it from > the Greg's staging tree (branch staging-next): >

Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Mauro Carvalho Chehab writes: > Em Fri, 27 Jan 2017 13:54:57 -0800 > Eric Anholt escreveu: > >> Here's my first pass at importing the camera driver. There's a bunch >> of TODO left to it, most of which is documented, and the rest being >> standard

Re: [PATCH v10 2/2] media: i2c: Add support for OV5647 sensor.

Hi Ramiro, On Wed, Mar 15, 2017 at 04:45:16PM +, Ramiro Oliveira wrote: > Hi Sakari > > On 3/7/2017 10:45 AM, Sakari Ailus wrote: > > Hi Ramiro, > > > > On Mon, Mar 06, 2017 at 11:16:34AM +, Ramiro Oliveira wrote: > > ... > >> +static int __sensor_init(struct v4l2_subdev *sd) > >> +{ >

[PATCH 2/3] [media] af9035: init i2c already in it930x_frontend_attach

i2c bus is already needed when the frontend is probed, so init it already in it930x_frontend_attach That prevents errors like si2168: probe of 6-0067 failed with error -5 Signed-off-by: Andreas Kemnade --- drivers/media/usb/dvb-usb-v2/af9035.c | 43

[PATCH 0/3] support for Logilink VG0022a DVB-T2 stick

Hi all, here are some patches needed for supporting the Logilink VG0022A DVB-T2 stick. As the combination of chips in that stick is not uncommon, the first two patches might also fix problems for similar hardware. Andreas Kemnade (3): [media] si2157: get chip id during probing [media] af9035:

Re: [PATCH v10 2/2] media: i2c: Add support for OV5647 sensor.

Hi Sakari On 3/7/2017 10:45 AM, Sakari Ailus wrote: > Hi Ramiro, > > On Mon, Mar 06, 2017 at 11:16:34AM +, Ramiro Oliveira wrote: > ... >> +static int __sensor_init(struct v4l2_subdev *sd) >> +{ >> +int ret; >> +u8 resetval, rdval; >> +struct i2c_client *client =

Re: [PATCH v10 1/2] Documentation: DT: Add OV5647 bindings

On Wed, Mar 15, 2017 at 11:51 AM, Ramiro Oliveira wrote: > Hi Rob > > On 3/15/2017 4:42 PM, Rob Herring wrote: >> On Mon, Mar 06, 2017 at 11:16:33AM +, Ramiro Oliveira wrote: >>> Create device tree bindings documentation. >>> >>> Signed-off-by: Ramiro Oliveira

Re: [RFC PATCH 1/5] Document: Add document file for Sony CXD2880 DVB-T2/T tuner + demodulator

On Tue, Mar 07, 2017 at 10:07:45AM +0900, yasunari.takigu...@sony.com wrote: > From: Yasunari Takiguchi > > This is the driver for Sony CXD2880 DVB-T2/T tuner + demodulator. Looks like a binding, not a driver to me. For subject, use: dt-bindings: media: ... > >

Re: [PATCH v10 1/2] Documentation: DT: Add OV5647 bindings

On Mon, Mar 06, 2017 at 11:16:33AM +, Ramiro Oliveira wrote: > Create device tree bindings documentation. > > Signed-off-by: Ramiro Oliveira > --- > .../devicetree/bindings/media/i2c/ov5647.txt | 35 > ++ > 1 file changed, 35 insertions(+) >

Re: [PATCH v3] [media] adv7604: Add support for hardware reset

Hi, 2016-06-22 13:30 GMT+02:00 Dragos Bogdan : > The part can be reset by a low pulse on the RESET pin (i.e. a hardware > reset) with a minimum width of 5 ms. It is recommended to wait 5 ms > after the low pulse before an I2C write is performed to the part. > For safety

Re: [PATCH v10 1/2] Documentation: DT: Add OV5647 bindings

Hi Rob On 3/15/2017 4:42 PM, Rob Herring wrote: > On Mon, Mar 06, 2017 at 11:16:33AM +, Ramiro Oliveira wrote: >> Create device tree bindings documentation. >> >> Signed-off-by: Ramiro Oliveira >> --- >> .../devicetree/bindings/media/i2c/ov5647.txt | 35 >>

Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Em Wed, 15 Mar 2017 15:01:29 -0700 Eric Anholt escreveu: > Mauro Carvalho Chehab writes: > > > Em Fri, 27 Jan 2017 13:54:57 -0800 > > Eric Anholt escreveu: > > > >> Here's my first pass at importing the camera driver. There's a

Re: [PATCH v3 0/7] Remove unneeded build directory traversals

On Wed, Mar 15, 2017 at 10:15 PM, Andrew F. Davis wrote: > On 03/15/2017 04:03 PM, Arnd Bergmann wrote: >> On Wed, Mar 15, 2017 at 5:37 PM, Andrew F. Davis wrote: >>> Hello all, >>> >>> I was building a kernel for x86 and noticed Make still descended into >>>

Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Hi Mauro, > Mauro Carvalho Chehab hat am 15. März 2017 um > 15:01 geschrieben: > > > Em Fri, 27 Jan 2017 13:54:57 -0800 > Eric Anholt escreveu: > > > Here's my first pass at importing the camera driver. There's a bunch > > of TODO left to it, most

Re: [PATCH 3/4] Documentation: dt: Add bindings documentation for CSI-2 Host Video Platform

On Tue, Mar 07, 2017 at 02:37:50PM +, Ramiro Oliveira wrote: > Create device tree bindings documentation for the CSI-2 Host Video > platform. > > Signed-off-by: Ramiro Oliveira > --- > .../devicetree/bindings/media/snps,plat-csi2.txt | 77 > ++

Re: media / v4l2-mc: wishlist for complex cameras (was Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline)

Hi! > > Well, I believe first question is: what applications would we want to > > run on complex devices? Will sending control from video to subdevs > > actually help? > > I would say: camorama, xawtv3, zbar, google talk, skype. If it runs > with those, it will likely run with any other

Re: [PATCH v5 07/39] ARM: dts: imx6qdl-sabrelite: remove erratum ERR006687 workaround

On 03/10/2017 11:17 AM, Fabio Estevam wrote: On Fri, Mar 10, 2017 at 3:59 PM, Troy Kisky wrote: On 3/9/2017 8:52 PM, Steve Longerbeam wrote: There is a pin conflict with GPIO_6. This pin functions as a power input pin to the OV5642 camera sensor, but ENET

Re: media / v4l2-mc: wishlist for complex cameras (was Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline)

Le mercredi 15 mars 2017 à 11:50 +0100, Philippe De Muyter a écrit : > > I would say: camorama, xawtv3, zbar, google talk, skype. If it runs > > with those, it will likely run with any other application. > > > > I would like to add the 'v4l2src' plugin of gstreamer, and on the > imx6 its While

Re: [PATCH 1/4] Documentation: dt: Add bindings documentation for DW MIPI CSI-2 Host

On Tue, Mar 07, 2017 at 02:37:48PM +, Ramiro Oliveira wrote: > Create device tree bindings documentation for the Synopsys DW MIPI CSI-2 > Host. > > Signed-off-by: Ramiro Oliveira > --- > .../devicetree/bindings/media/snps,dw-mipi-csi.txt | 37 >

Re: media / v4l2-mc: wishlist for complex cameras (was Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline)

Em Wed, 15 Mar 2017 19:04:21 +0100 Pavel Machek escreveu: > Hi! > > > > Well, I believe first question is: what applications would we want to > > > run on complex devices? Will sending control from video to subdevs > > > actually help? > > > > I would say: camorama, xawtv3,

Re: mainline build: 208 builds: 0 failed, 208 passed, 422 warnings (v4.11-rc2-164-gdefc7d752265)

On Wed, Mar 15, 2017 at 6:53 PM, kernelci.org bot wrote: > > mainline build: 208 builds: 0 failed, 208 passed, 422 warnings > (v4.11-rc2-164-gdefc7d752265) The last build failure in mainline is gone now, though I don't know what fixed it. Let's hope this doesn't come back as

Re: [Patch v2 02/11] s5p-mfc: Adding initial support for MFC v10.10

On Fri, Mar 03, 2017 at 02:37:07PM +0530, Smitha T Murthy wrote: > Adding the support for MFC v10.10, with new register file and > necessary hw control, decoder, encoder and structural changes. > > Signed-off-by: Smitha T Murthy > CC: Rob Herring > CC:

Re: [PATCH] [media] v4l2-dv-timings: Introduce v4l2_calc_fps()

On 03/14/2017 08:14 PM, Jose Abreu wrote: > Hi Hans, > > > On 14-03-2017 07:24, Hans Verkuil wrote: >>> Right, I was forgetting about this ... >>> >>> So: >>> 1) Most of HDMI receivers do not have the expected precision in >>> measuring pixel clock value; >> s/Most/Some/ >> >> Newer HDMI

Re: [PATCH v3 0/7] Remove unneeded build directory traversals

On 03/15/2017 04:03 PM, Arnd Bergmann wrote: > On Wed, Mar 15, 2017 at 5:37 PM, Andrew F. Davis wrote: >> Hello all, >> >> I was building a kernel for x86 and noticed Make still descended into >> directories like drivers/gpu/drm/hisilicon, this seems kind of odd given >> nothing will

Re: [PATCH v3 0/7] Remove unneeded build directory traversals

On Wed, Mar 15, 2017 at 5:37 PM, Andrew F. Davis wrote: > Hello all, > > I was building a kernel for x86 and noticed Make still descended into > directories like drivers/gpu/drm/hisilicon, this seems kind of odd given > nothing will be built here. It looks to be due to some

[PATCH 4/4] staging: atomisp: fix "alignment should match open parenthesis"

Fix checkpatch.pl issues in atomisp_cmd.c : "CHECK: Alignment should match open parenthesis" Signed-off-by: Daeseok Youn --- .../media/atomisp/pci/atomisp2/atomisp_cmd.c | 179 +++-- 1 file changed, 90 insertions(+), 89 deletions(-) diff --git

[PATCH 2/4] staging: atomisp: fix inconsistent indenting

Fix warnings from the smatch tool atomisp_cmd.c:5698 atomisp_set_fmt_to_snr() warn: inconsistent indenting atomisp_cmd.c:5714 atomisp_set_fmt_to_snr() warn: inconsistent indenting Signed-off-by: Daeseok Youn ---

[PATCH 3/4] staging: atomisp: remove useless #ifdef ISP2401 on top of atomisp_cmd.c

There is no reason to have "#ifdef ISP2401" condition on top of atomisp_cmd.c file Signed-off-by: Daeseok Youn --- drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c | 3 --- 1 file changed, 3 deletions(-) diff --git

[PATCH 3/3] [media] af9035: add Logilink vg0022a to device id table

Ths adds the logilink VG00022a dvb-t dongle to the device table. The dongle contains (checked by removing the case) IT9303 SI2168 214730 Signed-off-by: Andreas Kemnade --- drivers/media/usb/dvb-usb-v2/af9035.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 1/3] [media] si2157: get chip id during probing

If the si2157 is behind a e.g. si2168, the si2157 will at least in some situations not be readable after the si268 got the command 0101. It still accepts commands but the answer is just ff. So read the chip id before that so the information is not lost. The following line in kernel output is