Re: [PATCH 2/4] [media] pxa_camera: Fix incorrect test in the image size generation

Dne 2.5.2017 v 16:43 Robert Jarzmik napsal(a): > Petr Cvek <petr.c...@tul.cz> writes: > >> During the transfer from the soc_camera a test in pxa_mbus_image_size() >> got removed. Without it any PXA_MBUS_LAYOUT_PACKED format causes either >> the return of a wrong val

Re: [PATCH 2/4] [media] pxa_camera: Fix incorrect test in the image size generation

Petr Cvek <petr.c...@tul.cz> writes: > During the transfer from the soc_camera a test in pxa_mbus_image_size() > got removed. Without it any PXA_MBUS_LAYOUT_PACKED format causes either > the return of a wrong value (PXA_MBUS_PACKING_2X8_PADHI doubles > the correc

[PATCH 2/4] [media] pxa_camera: Fix incorrect test in the image size generation

During the transfer from the soc_camera a test in pxa_mbus_image_size() got removed. Without it any PXA_MBUS_LAYOUT_PACKED format causes either the return of a wrong value (PXA_MBUS_PACKING_2X8_PADHI doubles the correct value) or EINVAL (PXA_MBUS_PACKING_NONE and PXA_MBUS_PACKING_EXTEND16

[GIT PULL FOR v4.12] Add vimc virtual test driver

Finally merge this for 4.12. Regards, Hans The following changes since commit 4aed35ca73f6d9cfd5f7089ba5d04f5fb8623080: [media] v4l2-tpg: don't clamp XV601/709 to lim range (2017-04-10 14:58:06 -0300) are available in the git repository at:

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

be another subsystem to accept those buffers. Introduce a simple test > >> module to act as a dummy system to accept dma_bufs from elsewhere. The > >> goal is to provide a very simple interface to validate exported buffers > >> do something reasonable. This

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

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 buffers. Introduce a simple test >> modu

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

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 buffers. Introduce a simple test > module to act as a dummy system to accept dma_bufs from elsewhere

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

dma-buf is designed to share buffers. Sharing means that there needs to be another subsystem to accept those buffers. Introduce a simple test module to act as a dummy system to accept dma_bufs from elsewhere. The goal is to provide a very simple interface to validate exported buffers do something

[PATCH v10 3/3] SMAF: add test secure module

Choose this option to enable CMA allocation within SMAF + +config SMAF_TEST_SECURE + tristate "SMAF secure module for test" + depends on SMAF + help + Choose this option to enable secure module for test purpose diff --git a/drivers/smaf/Makefile b/drivers/smaf/Makefil

[PATCH v9 3/3] SMAF: add test secure module

Choose this option to enable CMA allocation within SMAF + +config SMAF_TEST_SECURE + tristate "SMAF secure module for test" + depends on SMAF + help + Choose this option to enable secure module for test purpose diff --git a/drivers/smaf/Makefile b/drivers/smaf/Makefil

[PATCH] [media] drxd_hard: Add missing error code assignment before test

It is likely that checking the result of the 2nd 'read16' is expected here. Signed-off-by: Christophe JAILLET --- drivers/media/dvb-frontends/drxk_hard.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/dvb-frontends/drxk_hard.c

Re: [v4l-utils RFC 0/3] mediatext library and test program

ng the set the next time. > > > On 07/21/2016 05:15 PM, Sakari Ailus wrote: > > Hi everyone, > > > > We've got a number of V4L2 (and MC) test programs for about as many reasons. > > The existing programs are concentrated to work on a single device node at a > > time

Re: [v4l-utils RFC 0/3] mediatext library and test program

/21/2016 05:15 PM, Sakari Ailus wrote: > Hi everyone, > > We've got a number of V4L2 (and MC) test programs for about as many reasons. > The existing programs are concentrated to work on a single device node at a > time, and with a single interface, be that Media controller or V4L2

[v4l-utils RFC 0/3] mediatext library and test program

Hi everyone, We've got a number of V4L2 (and MC) test programs for about as many reasons. The existing programs are concentrated to work on a single device node at a time, and with a single interface, be that Media controller or V4L2. The test programs are also command line controlled, working

[PATCH 6/7] cec: fix test for unconfigured adapter in main message loop

From: Hans Verkuil The main message loop checks if the physical address was valid, and if not it is assumed that the adapter had been unconfigured. However, this check is no longer correct, instead it should check that both adap->is_configured and adap->is_configuring

Re: [PATCH] v4l2-compliance: Improve test readability when fail

the q.create_bufs is expected to should return EINVAL in > this test? The height and size are set to half of the original values, and > the type and memory doesn't seems to change. For all drivers currently in the kernel the buffer size that create_bufs wants should be >= the size of the

[PATCH v8 3/3] SMAF: add test secure module

S help Choose this option to enable CMA allocation within SMAF + +config SMAF_TEST_SECURE + tristate "SMAF secure module for test" + depends on SMAF + help + Choose this option to enable secure module for test purpose diff --git a/drivers/smaf

RE: V4L2 SDR compliance test?

d device. > > > As mentioned above, we can have the main SDR (DRIF) driver code to > direct tuner subdev if present. However, when we want to upstream the DRIF > driver we may not have a real Tuner driver/device to get the compliance > test results. Should we run the compliance

[PATCH] v4l2-compliance: Improve test readability when fail

In case of failure, print "q.create_bufs(node, 1, ) != EINVAL" instead of "ret != EINVAL" Signed-off-by: Helen Koike <helen.ko...@collabora.co.uk> --- Hello, I was wondering, why the q.create_bufs is expected to should return EINVAL in this test? The heigh

Re: V4L2 SDR compliance test?

e the filters. We have several such drivers in the Kernel, and that's the procedure used when the chipset vendor doesn't see the value of having his chipset used by a Linux-based device. > As mentioned above, we can have the main SDR (DRIF) driver code to direct > tuner subdev if present. Howev

RE: V4L2 SDR compliance test?

can have the main SDR (DRIF) driver code to direct tuner subdev if present. However, when we want to upstream the DRIF driver we may not have a real Tuner driver/device to get the compliance test results. Should we run the compliance tests with a dummy stubbed tuner subdev? Please do suggest how

V4L2 SDR compliance test?

test demands TUNER ioctls for SDR device. As a SoC controller, DRIF is independent of tuner functionality as a third party provides this device. The DRIF driver will support V4L2_CID_xxx & V4L2_SDR_FMT_xxx ioctls but not the tuner ioctls. Two possible cases: --- 1) Third p

Re: [PATCH 2/2] tw686x-video: test for 60Hz instead of 50Hz

On 21 Apr 08:50 AM, Hans Verkuil wrote: > From: Hans Verkuil <hans.verk...@cisco.com> > > When determining if the standard is 50 or 60 Hz it is standard > practice to test for 60 Hz instead of 50 Hz. > > This doesn't matter normally, except if the user specifies both

[PATCH 2/2] tw686x-video: test for 60Hz instead of 50Hz

From: Hans Verkuil <hans.verk...@cisco.com> When determining if the standard is 50 or 60 Hz it is standard practice to test for 60 Hz instead of 50 Hz. This doesn't matter normally, except if the user specifies both 60 and 50 Hz standards. Signed-off-by: Hans Verkuil <hans.verk...@

Re: [PATCH] selftests: add a new test for Media Controller API

Em Fri, 12 Feb 2016 18:39:54 -0700 Shuah Khan <shua...@osg.samsung.com> escreveu: > This test opens user specified Media Device and calls > MEDIA_IOC_DEVICE_INFO ioctl in a loop once every 10 > seconds. This test is for detecting errors in device > removal path. >

[PATCHv10 15/15] test

From: Hans Verkuil Signed-off-by: Hans Verkuil --- include/media/videobuf2-core.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/media/videobuf2-core.h b/include/media/videobuf2-core.h index ef03ae5..956604d 100644

Re: [PATCH] [media] mt9v032: Remove duplicate test for I2C_FUNC_SMBUS_WORD_DATA functionality

Hi Axel, Thank you for the patch. On Sunday 10 August 2014 17:41:49 Axel Lin wrote: > Since commit b42261078a91 ("regmap: i2c: fallback to SMBus if the adapter > does not support standard I2C"), regmap-i2c will check the > I2C_FUNC_SMBUS_[BYTE|WORD]_DATA functionality based on the regmap_config

[PATCH] go7007: fix broken test

The wrong flags field was tested for the GO7007_BOARD_HAS_AUDIO flag: that flag is in board->main_info.flags, not in board->flags. Signed-off-by: Hans Verkuil Reported-by: Dan Carpenter diff --git a/drivers/media/usb/go7007/go7007-usb.c

[PATCH] [media] test

From: valentine.bars...@cogentembedded.com test --- drivers/media/platform/soc_camera/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/media/platform/soc_camera/Kconfig b/drivers/media/platform/soc_camera/Kconfig index dddca60..6540847 100644 --- a/drivers/media/platform

[PATCH 0/2] Patches to test MC next gen patches in OMAP3 ISP

Hello, This series contains two patches that are needed to test the [PATCH v7 00/44] MC next generation patches [0] in a OMAP3 board by using the omap3isp driver. I found two issues during testing, the first one is that the media_entity_cleanup() function tries to empty the pad links list

Re: drivers/media/platform/am437x/am437x-vpfe.c:1698: bad test ?

Hi David, On Mon, Aug 3, 2015 at 3:02 PM, David Binderman dcb...@hotmail.com wrote: Hello there, drivers/media/platform/am437x/am437x-vpfe.c:1698:27: warning: self-comparison always evaluates to true [-Wtautological-compare] if (client-addr == curr_client-addr

drivers/media/platform/am437x/am437x-vpfe.c:1698: bad test ?

Hello there, drivers/media/platform/am437x/am437x-vpfe.c:1698:27: warning: self-comparison always evaluates to true [-Wtautological-compare] if (client-addr == curr_client-addr     client-adapter-nr == client-adapter-nr) { maybe if (client-addr == curr_client-addr  

[PATCH] [media] adv7604/cobalt: Allow compile test if !GPIOLIB

The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer functionality only, can still be compiled if GPIOLIB is not enabled. Relax the dependency of VIDEO_ADV7604 and VIDEO_COBALT (the latter selects the

[PATCH] v4l2-compliance: test SELECTION only for the supported buf_type

-compliance/v4l2-test-formats.cpp | 40 + 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/utils/v4l2-compliance/v4l2-test-formats.cpp b/utils/v4l2-compliance/v4l2-test-formats.cpp index 1cffd65..23107c3 100644 --- a/utils/v4l2-compliance/v4l2-test-formats.cpp

Re: [PATCH 2/4] Test for ioctl() function signature

Em Sun, 25 Jan 2015 21:36:25 +0100 Felix Janda felix.ja...@posteo.de escreveu: On glibc, ioctl has the signature ioctl(int, unsigned long int, ...). On musl, libc and according to POSIX it is ioctl(int, int, ...). Add a configure test adapted from gnulib's ioctl.m4 to make the DL_PRELOAD

[PATCH 10/27] [media] wl128x: Allow compile test of GPIO consumers if !GPIOLIB

The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer functionality only, can still be compiled if GPIOLIB is not enabled. Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where appropriate.

[PATCHv2 2/4] Test for ioctl() function signature

On glibc, ioctl has the signature ioctl(int, unsigned long int, ...). On musl, libc and according to POSIX it is ioctl(int, int, ...). Add a configure test adapted from gnulib's ioctl.m4 to make the DL_PRELOAD libraries work for both signatures. Signed-off-by: Felix Janda felix.ja...@posteo.de

Re: [PATCH 01/13] go7007: don't use vb before test if it is not NULL

On 04/29/2015 01:04 AM, Mauro Carvalho Chehab wrote: As reported by smatch: drivers/media/usb/go7007/go7007-driver.c:452 frame_boundary() warn: variable dereferenced before check 'vb' (see line 449) Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com Acked-by: Hans Verkuil

[PATCH 01/13] go7007: don't use vb before test if it is not NULL

As reported by smatch: drivers/media/usb/go7007/go7007-driver.c:452 frame_boundary() warn: variable dereferenced before check 'vb' (see line 449) Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com diff --git a/drivers/media/usb/go7007/go7007-driver.c

[PATCH] [media] fc0013: remove unneeded test

The same code is executed if ret is true or false, so this test can be removed. Fix Coverity CID 1268782. Signed-off-by: Laurent Navet laurent.na...@gmail.com --- drivers/media/tuners/fc0013.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/media/tuners/fc0013.c b/drivers/media

[PATCH 05/29] vivid: fix test pattern movement for V4L2_FIELD_ALTERNATE

From: Hans Verkuil hans.verk...@cisco.com The successive TOP/BOTTOM fields did not move as they should: only every other field actually changed position. The cause was that the tpg needs to know if it is dealing with a FIELD_ALTERNATE case since that requires slightly different handling. So

[PATCH v6 8/8] v4l: xilinx: Add Test Pattern Generator driver

The TPG generates multiple static or dynamic test patterns. The driver currently hardcodes the pattern to the moving box pattern. Signed-off-by: Christian Kohn christian.k...@xilinx.com Signed-off-by: Hyun Kwon hyun.k...@xilinx.com Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com

[PATCH v5 8/8] v4l: xilinx: Add Test Pattern Generator driver

The TPG generates multiple static or dynamic test patterns. The driver currently hardcodes the pattern to the moving box pattern. Signed-off-by: Christian Kohn christian.k...@xilinx.com Signed-off-by: Hyun Kwon hyun.k...@xilinx.com Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com

test post, just ignore

-- 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] media: vivid test device: Add NV{12,21} and Y{U,V}12 pixel format.

, effectively making that transparent. Which may not be a bad idea. However, note that the 'Noise' test pattern is broken with the new formats. Conclusion: there is a lot more work to be done here... Regards, Hans --- drivers/media/platform/vivid/vivid-kthread-cap.c | 6 +- drivers/media

Re: [PATCH] media: vivid test device: Add NV{12,21} and Y{U,V}12 pixel format.

that when printing the text you only fill in the luma and not the chroma, effectively making that transparent. Which may not be a bad idea. However, note that the 'Noise' test pattern is broken with the new formats. Conclusion: there is a lot more work to be done here... For the record, I

[PATCH] media: vivid test device: Add NV{12,21} and Y{U,V}12 pixel format.

Add support for vertical + horizontal subsampled formats to vivid and use it to generate YU12, YV12, NV12, NV21 as defined in [1,2]. These formats are tightly packed N planar, because they provide chroma(s) as a separate array, but they are not mplanar yet, as discussed in the list. The modus

Re: Vivid test device: adding YU12

rather go for YUV420M directly; perhaps cheating a bit on the TPG calculation in the first implementation: I/we could just simplify the Chroma calculation to grabbing the upper-left pixel value, ignoring the other three. Not perfect, but for a first patch of a test device

Re: Vivid test device: adding YU12

value, ignoring the other three. Not perfect, but for a first patch of a test device it should do. WDYT? I would actually pick YUV420 or NV12 as the initial implementation, since you can test that with qv4l2 (it uses libv4lconvert which understands those two formats). That way you can develop

Re: Re: Vivid test device: adding YU12

, but for a first patch of a test device it should do. WDYT? With the patch, vivid: - seems to enumerate the new triplanar format all right - vid_s_fmt_vid_cap() works as intended too, apparently - when arriving to vid_cap_queue_setup(), the size of the different sub-arrays does not look quite ok

Re: Vivid test device: adding YU12

this part is up and running, I wanted to use Vivid to test dma-buf based capture. Big thanks! -- 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

Vivid test device: adding YU12

green. I added as well a capture output dmesgs. Not much of interest here, the first few lines configure the queue -- with my few added dprintk it can be seen that the queue sizes are seemingly incorrect. If and when this part is up and running, I wanted to use Vivid to test dma-buf based capture

[PATCH 4/4] contrib/test: Add missing LIB_ARGP

v4l2gl and v4l2grab need argp. Signed-off-by: Felix Janda felix.ja...@posteo.de --- contrib/test/Makefile.am | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/contrib/test/Makefile.am b/contrib/test/Makefile.am index 0bfa33e..7f84435 100644 --- a/contrib/test/Makefile.am

[PATCH 2/4] Test for ioctl() function signature

On glibc, ioctl has the signature ioctl(int, unsigned long int, ...). On musl, libc and according to POSIX it is ioctl(int, int, ...). Add a configure test adapted from gnulib's ioctl.m4 to make the DL_PRELOAD libraries work for both signatures. Signed-off-by: Felix Janda felix.ja...@posteo.de

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 01/18/2015 09:54 AM, Jurgen Kramer wrote: I have been running the original code (because of issues with the patch) for a while with some added printks. This morning I found this NULL pointer derefence: That's what my patch fixes, so that's no surprise that you get this. I don't understand

Re: [PATCH] cx23885/vb2 regression: please test this patch

I have been running the original code (because of issues with the patch) for a while with some added printks. This morning I found this NULL pointer derefence: [47772.121968] DEBUG: vb2_thread_stop entered [47772.122014] BUG: unable to handle kernel NULL pointer dereference at (null)

Re: [PATCH] cx23885/vb2 regression: please test this patch

On Sun, 2015-01-18 at 11:40 +0100, Hans Verkuil wrote: On 01/18/2015 09:54 AM, Jurgen Kramer wrote: I have been running the original code (because of issues with the patch) for a while with some added printks. This morning I found this NULL pointer derefence: That's what my patch fixes,

Re: [PATCH] cx23885/vb2 regression: please test this patch

problem. Based on past reports there is also a possible problem with multiple frontends, but I don't have hardware like that and even if I had I am not sure I would be able to test it properly. Besides, that issue seemed to be unrelated to the vb2 conversion. It's all pretty vague, though. Regards

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 17.01.2015 13:09, Hans Verkuil wrote: Thanks. This was with one frontend? And what was the exact sequence of commands used to replicate this? Sorry, but I need precise details of how you reproduce this, especially since I can't reproduce it. This test was run on first front end. I just

Re: [PATCH] cx23885/vb2 regression: please test this patch

on past reports there is also a possible problem with multiple frontends, but I don't have hardware like that and even if I had I am not sure I would be able to test it properly. Besides, that issue seemed to be unrelated to the vb2 conversion. It's all pretty vague, though. Regards, Hans

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 01/13/2015 06:55 PM, Raimonds Cicans wrote: On 13.01.2015 16:01, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. This patch fixes a race condition in the vb2_thread that occurs when

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 01/15/2015 05:32 PM, Jurgen Kramer wrote: Hi Hans, On Tue, 2015-01-13 at 17:59 +0100, Jurgen Kramer wrote: Hi Hans, On Tue, 2015-01-13 at 15:01 +0100, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 16.01.2015 16:54, Hans Verkuil wrote: On 01/13/2015 06:55 PM, Raimonds Cicans wrote: On 13.01.2015 16:01, Hans Verkuil wrote: Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. Can you check that the function cx23885_risc_field

Re: [PATCH] cx23885/vb2 regression: please test this patch

On Fri, 2015-01-16 at 15:58 +0100, Hans Verkuil wrote: On 01/15/2015 05:32 PM, Jurgen Kramer wrote: Hi Hans, On Tue, 2015-01-13 at 17:59 +0100, Jurgen Kramer wrote: Hi Hans, On Tue, 2015-01-13 at 15:01 +0100, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch

Re: [PATCH] cx23885/vb2 regression: please test this patch

, Raimonds Cicans r...@apollo.lv wrote: On 16.01.2015 16:54, Hans Verkuil wrote: On 01/13/2015 06:55 PM, Raimonds Cicans wrote: On 13.01.2015 16:01, Hans Verkuil wrote: Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. Can you check

Re: [PATCH] cx23885/vb2 regression: please test this patch

wrote: On 01/13/2015 06:55 PM, Raimonds Cicans wrote: On 13.01.2015 16:01, Hans Verkuil wrote: Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. Can you check that the function cx23885_risc_field in drivers/media/pci/cx23885/cx23885

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 01/16/2015 05:20 PM, Raimonds Cicans wrote: On 16.01.2015 16:54, Hans Verkuil wrote: On 01/13/2015 06:55 PM, Raimonds Cicans wrote: On 13.01.2015 16:01, Hans Verkuil wrote: Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. Can you

Re: [PATCH] cx23885/vb2 regression: please test this patch

Hi Hans, On Tue, 2015-01-13 at 17:59 +0100, Jurgen Kramer wrote: Hi Hans, On Tue, 2015-01-13 at 15:01 +0100, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. This patch fixes a race

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 13.01.2015 19:55, Raimonds Cicans wrote: On 13.01.2015 16:01, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. This patch fixes a race condition in the vb2_thread that occurs when the thread

Re: [PATCH] cx23885/vb2 regression: please test this patch

On 13.01.2015 16:01, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. This patch fixes a race condition in the vb2_thread that occurs when the thread is stopped. The crucial fix is calling

[PATCH] cx23885/vb2 regression: please test this patch

Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. This patch fixes a race condition in the vb2_thread that occurs when the thread is stopped. The crucial fix is calling kthread_stop much earlier in vb2_thread_stop

Re: [PATCH] cx23885/vb2 regression: please test this patch

Hi Hans, On Tue, 2015-01-13 at 15:01 +0100, Hans Verkuil wrote: Hi Raimonds, Jurgen, Can you both test this patch? It should (I hope) solve the problems you both had with the cx23885 driver. This patch fixes a race condition in the vb2_thread that occurs when the thread is stopped

[PATCH 2/3] mtd: test: Replace timeval with ktime_t in speedtest.c and torturetest.c

This patch changes the 32-bit time type (timeval) to the 64-bit one (ktime_t), since 32-bit time types will break in the year 2038. I use ktime_t instead of timeval to define 'start' and 'finish' which are used to get the time for tow points. This patch also changes do_gettimeofday() to

[PATCH v4 10/10] v4l: xilinx: Add Test Pattern Generator driver

The TPG generates multiple static or dynamic test patterns. The driver currently hardcodes the pattern to the moving box pattern. Signed-off-by: Christian Kohn christian.k...@xilinx.com Signed-off-by: Hyun Kwon hyun.k...@xilinx.com Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com

[PATCH] vivid: add test array controls

Add array controls to test support for such controls. There is one array with just one element, one 8x16 matrix control and one 4 dimensional 2x3x4x5 control. This makes it possible to experiment with such controls without requiring hard-to-get hardware. Signed-off-by: Hans Verkuil hans.verk

[PATCH v2 13/13] v4l: xilinx: Add Test Pattern Generator driver

The TPG generates multiple static or dynamic test patterns. The driver currently hardcodes the pattern to the moving box pattern. Signed-off-by: Christian Kohn christian.k...@xilinx.com Signed-off-by: Hyun Kwon hyun.k...@xilinx.com Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com

[PATCH 0/5] Contiguous DMA buffer support for the Virtual Video Test Driver

Hi, to use vivid as test source for a hardware pipeline with elements that can only handle contiguous DMA buffers, I'd like to add support for the videobuf2-dma-contig allocator and enable VIDIOC_EXPBUF in vivid. Since DMA memory should be associated with a struct device, I have added a platform

[PATCH] [media] rc: fix hix5hd2 compile-test issue

Commit 4c255791ffd6410f (asm-generic: io: implement relaxed accessor macros as conditional wrappers) adds wrappers to asm-generic of {read,write}{b,w,l,q}_relaxed. Change CONFIG_PM to CONFIG_PM_SLEEP to solve warning: 'hix5hd2_ir_suspend' 'hix5hd2_ir_resume' defined but not used Reported-by:

[PATCH 11/11] v4l: xilinx: Add Test Pattern Generator driver

The TPG generates multiple static or dynamic test patterns. The driver currently hardcodes the pattern to the moving box pattern. Signed-off-by: Christian Kohn christian.k...@xilinx.com Signed-off-by: Hyun Kwon hyun.k...@xilinx.com Signed-off-by: Laurent Pinchart laurent.pinch...@ideasonboard.com

[PATCH] [media] rc: fix hix5hd2 compile-test issue

Add dependence to solve build error in arch like ia64 error: implicit declaration of function 'readl_relaxed' 'writel_relaxed' Change CONFIG_PM to CONFIG_PM_SLEEP to solve warning: 'hix5hd2_ir_suspend' 'hix5hd2_ir_resume' defined but not used Reported-by: Fengguang Wu fengguang...@intel.com

Re: [PATCH] [media] rc: fix hix5hd2 compile-test issue

On Fri, Sep 26, 2014 at 08:57:30PM +0800, Zhangfei Gao wrote: Add dependence to solve build error in arch like ia64 error: implicit declaration of function 'readl_relaxed' 'writel_relaxed' Change CONFIG_PM to CONFIG_PM_SLEEP to solve warning: 'hix5hd2_ir_suspend' 'hix5hd2_ir_resume'

Re: [PATCH] [media] rc: fix hix5hd2 compile-test issue

On 09/26/2014 09:12 PM, Russell King - ARM Linux wrote: On Fri, Sep 26, 2014 at 08:57:30PM +0800, Zhangfei Gao wrote: Add dependence to solve build error in arch like ia64 error: implicit declaration of function 'readl_relaxed' 'writel_relaxed' Change CONFIG_PM to CONFIG_PM_SLEEP to solve

[RFC PATCH 08/11] vivid: add test config store for the contrast control

From: Hans Verkuil hans.verk...@cisco.com Signed-off-by: Hans Verkuil hans.verk...@cisco.com --- drivers/media/platform/vivid/vivid-ctrls.c | 4 drivers/media/platform/vivid/vivid-vid-cap.c | 1 + 2 files changed, 5 insertions(+) diff --git a/drivers/media/platform/vivid/vivid-ctrls.c

[PATCH 27/46] [media] drxk_hard: simplify test logic

instead of testing if it is false or true, just use if (!foo) or if (foo). That makes the code easier to read and shorter. Also, properly initialize booleans with true or false. Signed-off-by: Mauro Carvalho Chehab m.che...@samsung.com diff --git a/drivers/media/dvb-frontends/drxk_hard.c

[PATCH 30/46] [media] omap: simplify test logic

instead of testing bools if they are false or true, just use if (!foo) or if (foo). That makes the code easier to read and shorter. Also, properly initialize booleans with true or false. Signed-off-by: Mauro Carvalho Chehab m.che...@samsung.com diff --git

[PATCH 29/46] [media] lm3560: simplify a boolean test

lml33dpatch is boolean. So, the possible values are true or false. Instead of using if (lml33dpath), just use if (!lml33dpath). That allows a faster mental parsing when analyzing the code. Signed-off-by: Mauro Carvalho Chehab m.che...@samsung.com diff --git

Re: [GIT PULL FOR v3.18] Add vivid test driver, remove old vivi test driver

capture and output code vivid: add the kthread code that controls the video rate vivid: add a simple framebuffer device for overlay testing vivid: add the Test Pattern Generator vivid: add support for radio receivers and transmitters vivid: add support

[GIT PULL FOR v3.18] Add vivid test driver, remove old vivi test driver

rate vivid: add a simple framebuffer device for overlay testing vivid: add the Test Pattern Generator vivid: add support for radio receivers and transmitters vivid: add support for software defined radio vivid: enable the vivid driver vivi: remove driver, it's

[PATCH v2 05/35] [media] gsc-core: Remove useless test

drivers/media/platform/exynos-gsc/gsc-core.c: In function 'gsc_probe': drivers/media/platform/exynos-gsc/gsc-core.c:1089:2: warning: comparison is alw ays false due to limited range of data type [-Wtype-limits] if (gsc-id 0 || gsc-id = drv_data-num_entities) { ^ gsc-id is declared as u16, so

[PATCH v2 00/35] Enable compilation test for several drivers

: declare some functions as static [media] dm355_ccdc: declare a function as static [media] gsc-core: Remove useless test [media] gsc-m2m: Remove an unused var. [media] ti-vpe: use %pad for dma address [media] ti-vpe: shut up a casting warning message [media] atmel-isi: tag dma_addr_t

[PATCHv2 00/12] vivid: Virtual Video Test Driver

test driver no longer emulates just video capture, but also video output, vbi capture/output, radio receivers/transmitters and SDR capture. There is even support for testing capture and output overlays. Up to 64 vivid instances can be created, each with up to 16 inputs and 16 outputs. Each input

[PATCHv2 09/12] vivid: add the Test Pattern Generator

From: Hans Verkuil hans.verk...@cisco.com The test patterns for video capture are generated by this code. All patterns are precalculated taking into account colorspace information, pixel and video aspect ratios and scaling information. Signed-off-by: Hans Verkuil hans.verk...@cisco.com

[PATCH] HackRF SDR driver - v4l2-compliance test report

Pix Format Compliance test for device /dev/swradio0 (not using libv4l2): Required ioctls: test VIDIOC_QUERYCAP: OK Allow for multiple opens: test second sdr open: OK test VIDIOC_QUERYCAP: OK test VIDIOC_G/S_PRIORITY: OK Debug ioctls: test VIDIOC_DBG_G

[GIT PULL FOR 3.18] Test pattern controls

Hi Mauro, This set adds V4L2 test pattern controls and support for those in the smiapp driver. This pull request is on top of the unlocked controls patches, the pull request of which can be found here: URL:http://www.spinics.net/lists/linux-media/msg79196.html Please pull. The following

[PATCH] [media] mt9v032: Remove duplicate test for I2C_FUNC_SMBUS_WORD_DATA functionality

Since commit b42261078a91 (regmap: i2c: fallback to SMBus if the adapter does not support standard I2C), regmap-i2c will check the I2C_FUNC_SMBUS_[BYTE|WORD]_DATA functionality based on the regmap_config setting if the adapter does not support standard I2C. So remove the I2C_FUNC_SMBUS_WORD_DATA

[PATCHv1 00/12] vivid: Virtual Video Test Driver

. This vivid test driver no longer emulates just video capture, but also video output, vbi capture/output, radio receivers/transmitters and SDR capture. There is even support for testing capture and output overlays. Up to 64 vivid instances can be created, each with up to 16 inputs and 16 outputs

[PATCHv1 09/12] vivid: add the Test Pattern Generator

From: Hans Verkuil hans.verk...@cisco.com The test patterns for video capture are generated by this code. All patterns are precalculated taking into account colorspace information, pixel and video aspect ratios and scaling information. Signed-off-by: Hans Verkuil hans.verk...@cisco.com

[PATCH] saa7164-dvb: Remove unnecessary null test

This patch removes the null test on dvb. dvb is initialized at the beginning of the function to port-dvb. Since port is dereferenced prior to the null test, port must be a valid pointer, and port-dvb cannot be null. The following Coccinelle script is used for detecting the change: @r@ expression

[PATCH] dib7000m: Remove unnecessary null test

This patch removes the null test on ch. ch is initialized at the beginning of the function to demod-dtv_property_cache. Since demod is dereferenced prior to the null test, demod must be a valid pointer, and demod-dtv_property_cache cannot be null. The following Coccinelle script is used

Re: [PATCH v3.1 3/3] smiapp: Implement the test pattern control

Hi Sakari, Thank you for the patch. On Thursday 29 May 2014 18:16:54 Sakari Ailus wrote: Add support for the V4L2_CID_TEST_PATTERN control. When the solid colour mode is selected, additional controls become available for setting the solid four solid colour components. Signed-off-by: Sakari

<    1   2   3   4   5   >