Re: [PATCH v2 1/1] media: Use common test pattern menu entries

Em Tue, 4 Dec 2018 15:40:42 +0200 Sakari Ailus escreveu: > While the test pattern menu itself is not standardised, many devices > support the same test patterns. Aligning the menu entries helps the user > space to use the interface, and adding macros for the menu entry strings > h

Re: [PATCH 1/1] media: Use common test pattern menu entries

On Tue, Nov 27, 2018 at 07:19:52PM +0800, Bingbu Cao wrote: > > On 11/27/2018 05:33 PM, Sakari Ailus wrote: > > diff --git a/include/uapi/linux/v4l2-controls.h > > b/include/uapi/linux/v4l2-controls.h > > index 998983a6e6b7..a74ff6f1ac88 100644 > > --- a/include/uapi/linux/v4l2-controls.h > >

[PATCH v2 1/1] media: Use common test pattern menu entries

While the test pattern menu itself is not standardised, many devices support the same test patterns. Aligning the menu entries helps the user space to use the interface, and adding macros for the menu entry strings helps to keep them aligned. Signed-off-by: Sakari Ailus --- since v1: - Fix

Re: [RESEND PATCH 1/1] media: Use common test pattern menu entries

On Tue, Nov 27, 2018 at 01:11:42PM +0100, Luca Ceresoli wrote: > Hi Sakari, Bingbu, > > On 27/11/18 10:34, Sakari Ailus wrote: > > While the test pattern menu itself is not standardised, many devices > > support the same test patterns. Aligning the menu entries helps the

Re: [RESEND PATCH 1/1] media: Use common test pattern menu entries

Hi Sakari, Bingbu, On 27/11/18 10:34, Sakari Ailus wrote: > While the test pattern menu itself is not standardised, many devices > support the same test patterns. Aligning the menu entries helps the user > space to use the interface, and adding macros for the menu entry strings > h

Re: [PATCH 1/1] media: Use common test pattern menu entries

On 11/27/2018 05:33 PM, Sakari Ailus wrote: While the test pattern menu itself is not standardised, many devices support the same test patterns. Aligning the menu entries helps the user space to use the interface, and adding macros for the menu entry strings helps to keep them aligned. I like

[RESEND PATCH 1/1] media: Use common test pattern menu entries

While the test pattern menu itself is not standardised, many devices support the same test patterns. Aligning the menu entries helps the user space to use the interface, and adding macros for the menu entry strings helps to keep them aligned. Signed-off-by: Sakari Ailus --- Fixed Andy's email

[PATCH 1/1] media: Use common test pattern menu entries

While the test pattern menu itself is not standardised, many devices support the same test patterns. Aligning the menu entries helps the user space to use the interface, and adding macros for the menu entry strings helps to keep them aligned. Signed-off-by: Sakari Ailus --- drivers/media/i2c

Re: [PATCH 2/2] media: imx355: fix wrong order in test pattern menus

On Tue, Nov 27, 2018 at 10:45:02AM +0800, Bingbu Cao wrote: > > > On 11/26/2018 04:57 PM, Sakari Ailus wrote: > > Hi Bing Bu, > > > > On Mon, Nov 26, 2018 at 03:43:34PM +0800, bingbu@intel.com wrote: > > > From: Bingbu Cao > > > > &g

Re: [PATCH 2/2] media: imx355: fix wrong order in test pattern menus

On 11/26/2018 04:57 PM, Sakari Ailus wrote: Hi Bing Bu, On Mon, Nov 26, 2018 at 03:43:34PM +0800, bingbu@intel.com wrote: From: Bingbu Cao current imx355 test pattern order in ctrl menu is not correct, this patch fixes it. Signed-off-by: Bingbu Cao --- drivers/media/i2c/imx355.c

Re: [PATCH 2/2] media: imx355: fix wrong order in test pattern menus

On 11/26/2018 04:57 PM, Sakari Ailus wrote: Hi Bing Bu, On Mon, Nov 26, 2018 at 03:43:34PM +0800, bingbu@intel.com wrote: From: Bingbu Cao current imx355 test pattern order in ctrl menu is not correct, this patch fixes it. Signed-off-by: Bingbu Cao --- drivers/media/i2c/imx355.c

Re: [PATCH 2/2] media: imx355: fix wrong order in test pattern menus

Hi Bing Bu, On Mon, Nov 26, 2018 at 03:43:34PM +0800, bingbu@intel.com wrote: > From: Bingbu Cao > > current imx355 test pattern order in ctrl menu > is not correct, this patch fixes it. > > Signed-off-by: Bingbu Cao > --- > drivers/media/i2c/imx355.c | 2

[PATCH 1/2] media: imx319: fix wrong order in test pattern menus

From: Bingbu Cao current imx319 test pattern order in ctrl menu is not correct, this patch fixes it. Signed-off-by: Bingbu Cao --- drivers/media/i2c/imx319.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/i2c/imx319.c b/drivers/media/i2c/imx319.c index

[PATCH 2/2] media: imx355: fix wrong order in test pattern menus

From: Bingbu Cao current imx355 test pattern order in ctrl menu is not correct, this patch fixes it. Signed-off-by: Bingbu Cao --- drivers/media/i2c/imx355.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/i2c/imx355.c b/drivers/media/i2c/imx355.c index

[RFCv4 PATCH 3/3] vimc: add property test code

From: Hans Verkuil Add properties to entities and pads to be able to test the properties API. Signed-off-by: Hans Verkuil --- drivers/media/platform/vimc/vimc-common.c | 50 +++ 1 file changed, 50 insertions(+) diff --git a/drivers/media/platform/vimc/vimc-common.c b

[PATCH v2] v4l2-compliance: test orphaned buffer support

Test that V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS is reported equally for both MMAP and DMABUF memory types. If supported, try to orphan buffers by calling reqbufs(0) before unmapping or closing DMABUF fds. Also close exported DMABUF fds and free buffers in testDmaBuf if orphaned buffers

Re: [PATCH v4l-utils] v4l2-compliance: test orphaned buffer support

On 11/15/18 13:52, Philipp Zabel wrote: > On Thu, 2018-11-15 at 11:21 +0100, Hans Verkuil wrote: >> On 11/14/18 15:38, Philipp Zabel wrote: >>> Test that V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS is reported equally for >>> both MMAP and DMABUF memory types. If suppo

Re: [PATCH v4l-utils] v4l2-compliance: test orphaned buffer support

On Thu, 2018-11-15 at 11:21 +0100, Hans Verkuil wrote: > On 11/14/18 15:38, Philipp Zabel wrote: > > Test that V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS is reported equally for > > both MMAP and DMABUF memory types. If supported, try to orphan buffers > > by calling reqbuf

Re: [PATCH v4l-utils] v4l2-compliance: test orphaned buffer support

On 11/14/18 15:38, Philipp Zabel wrote: > Test that V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS is reported equally for > both MMAP and DMABUF memory types. If supported, try to orphan buffers > by calling reqbufs(0) before unmapping or closing DMABUF fds. > > Also close exported DMAB

[PATCH v4l-utils] v4l2-compliance: limit acceptable width/height to 65536 in VIDIOC_SUBDEV_G/S_FMT test

Fail if the driver returns unrealistically large frame sizes. Signed-off-by: Philipp Zabel --- utils/v4l2-compliance/v4l2-test-subdevs.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/utils/v4l2-compliance/v4l2-test-subdevs.cpp b/utils/v4l2-compliance/v4l2-test

[PATCH v4l-utils] v4l2-compliance: test orphaned buffer support

Test that V4L2_BUF_CAP_SUPPORTS_ORPHANED_BUFS is reported equally for both MMAP and DMABUF memory types. If supported, try to orphan buffers by calling reqbufs(0) before unmapping or closing DMABUF fds. Also close exported DMABUF fds and free buffers in testDmaBuf if orphaned buffers

RE: [PATCH] media: imx258: remove test pattern map from driver

Subject: Re: [PATCH] media: imx258: remove test pattern map from driver Hi Jason, Thanks for the patch. On Wed, Nov 07, 2018 at 03:22:23PM +0800, jasonx.z.c...@intel.com wrote: > From: "Chen, JasonX Z" > > Test Pattern mode be picked at HAL instead of driver. > do a FLIP w

[PATCH] media: imx258: remove test pattern map from driver

From: "Chen, JasonX Z" change bayer order when using test pattern mode. remove test pattern mapping method Signed-off-by: Chen, JasonX Z --- drivers/media/i2c/imx258.c | 23 --- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/drivers/media/i2c/

Re: [RFC] Create test script(s?) for regression testing

t;>>> On Tuesday, 6 November 2018 15:56:34 EET Hans Verkuil wrote: >>>>> On 11/06/18 14:12, Laurent Pinchart wrote: >>>>>> On Tuesday, 6 November 2018 13:36:55 EET Sakari Ailus wrote: >>>>>>> On Tue, Nov 06, 2018 at 09:37:07AM

Re: [RFC] Create test script(s?) for regression testing

Hi Mauro, On Wednesday, 7 November 2018 21:53:20 EET Mauro Carvalho Chehab wrote: > Em Wed, 07 Nov 2018 21:35:32 +0200 Laurent Pinchart escreveu: > > On Wednesday, 7 November 2018 21:10:35 EET Mauro Carvalho Chehab wrote: [snip] > >> I'm with Hans on that matter: better to start with an

Re: [RFC] Create test script(s?) for regression testing

018 13:36:55 EET Sakari Ailus wrote: > > >>>>>> On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: > > >>>>>>> Hi all, > > >>>>>>> > > >>>>>>> After the media summit (heavy on

Re: [RFC] Create test script(s?) for regression testing

6 November 2018 13:36:55 EET Sakari Ailus wrote: > > > > > On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: > > > > > > Hi all, > > > > > > > > > > > > After the media summit (heavy on test discussio

Re: [RFC] Create test script(s?) for regression testing

Verkuil wrote: > >>>>>>> Hi all, > >>>>>>> > >>>>>>> After the media summit (heavy on test discussions) and the V4L2 > >>>>>>> event regression we just found it is clear we need to do a better > &g

Re: [RFC] Create test script(s?) for regression testing

> > >> On 11/06/18 14:12, Laurent Pinchart wrote: > > >>> On Tuesday, 6 November 2018 13:36:55 EET Sakari Ailus wrote: > > >>>> On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: > > >>>>> Hi all, > > >>>&g

Re: [PATCH] media: imx258: remove test pattern map from driver

Hi Jason, Thanks for the patch. On Wed, Nov 07, 2018 at 03:22:23PM +0800, jasonx.z.c...@intel.com wrote: > From: "Chen, JasonX Z" > > Test Pattern mode be picked at HAL instead of driver. > do a FLIP when userspace use test pattern mode. > add entity_ops for validating

Re: [RFC] Create test script(s?) for regression testing

2018 13:36:55 EET Sakari Ailus wrote: > >>>> On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: > >>>>> Hi all, > >>>>> > >>>>> After the media summit (heavy on test discussions) and the V4L2 event > >>&g

Re: [RFC] Create test script(s?) for regression testing

18 at 09:37:07AM +0100, Hans Verkuil wrote: >>>>> Hi all, >>>>> >>>>> After the media summit (heavy on test discussions) and the V4L2 event >>>>> regression we just found it is clear we need to do a better job with >>>>>

[PATCH] media: imx258: remove test pattern map from driver

From: "Chen, JasonX Z" Test Pattern mode be picked at HAL instead of driver. do a FLIP when userspace use test pattern mode. add entity_ops for validating imx258 link. Signed-off-by: Chen, JasonX Z --- drivers/media/i2c/imx258.c | 28 1 file changed, 8

Re: [RFC] Create test script(s?) for regression testing

>>> > >>> After the media summit (heavy on test discussions) and the V4L2 event > >>> regression we just found it is clear we need to do a better job with > >>> testing. > >>> > >>> All the pieces are in place, so what is n

Re: [RFC] Create test script(s?) for regression testing

On 11/06/18 14:12, Laurent Pinchart wrote: > Hello, > > On Tuesday, 6 November 2018 13:36:55 EET Sakari Ailus wrote: >> On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: >>> Hi all, >>> >>> After the media summit (heavy on test discussions)

Re: [RFC] Create test script(s?) for regression testing

On Tue, 2018-11-06 at 09:37 +0100, Hans Verkuil wrote: > Hi all, > > After the media summit (heavy on test discussions) and the V4L2 event > regression > we just found it is clear we need to do a better job with testing. > > All the pieces are in place, so what is

Re: [RFC] Create test script(s?) for regression testing

Hello, On Tuesday, 6 November 2018 13:36:55 EET Sakari Ailus wrote: > On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: > > Hi all, > > > > After the media summit (heavy on test discussions) and the V4L2 event > > regression we just found it is clear

Re: [RFC] Create test script(s?) for regression testing

Hi Hans, On Tue, Nov 06, 2018 at 09:37:07AM +0100, Hans Verkuil wrote: > Hi all, > > After the media summit (heavy on test discussions) and the V4L2 event > regression > we just found it is clear we need to do a better job with testing. > > All the pieces are in pla

[RFC] Create test script(s?) for regression testing

Hi all, After the media summit (heavy on test discussions) and the V4L2 event regression we just found it is clear we need to do a better job with testing. All the pieces are in place, so what is needed is to combine it and create a script that anyone of us as core developers can run to check

Re: [PATCH] media: rc: self test for IR encoders and decoders

check IR transmission between two rc devices. Using rc-loopback, > > we use it to check the IR encoders and decoders themselves. > > > > No hardware is required for this test. > > > > Signed-off-by: Sean Young > > Cc: Shuah Khan > > Hi Sean, > > This

Re: [PATCH] media: rc: self test for IR encoders and decoders

IR encoders and decoders themselves. > > No hardware is required for this test. > > Signed-off-by: Sean Young > Cc: Shuah Khan Hi Sean, This looks good. I will get this into the next release. It will show up in linux-kselftest next after 4.20-rc1 comes out. thanks, -- Shuah

Re: RFC: kernelCI media subsystem pilot (Test results for gtucker/kernelci-media - gtucker-kernelci-media-001-6-g1b2c6e5844d8)

r those new to kernelci, see > > https://github.com/kernelci/kernelci-doc/wiki/KernelCI > > and https://kernelci.org/. > > > > The goal is to lay down the infrastructure required to make > > automated test coverage an integral part of our feature > > and

Re: RFC: kernelCI media subsystem pilot (Test results for gtucker/kernelci-media - gtucker-kernelci-media-001-6-g1b2c6e5844d8)

KernelCI > and https://kernelci.org/. > > The goal is to lay down the infrastructure required to make > automated test coverage an integral part of our feature > and bugfix development process. > > So, as a first attempt, we've decided to extend kernelci test > v4l2 plan

RFC: kernelCI media subsystem pilot (Test results for gtucker/kernelci-media - gtucker-kernelci-media-001-6-g1b2c6e5844d8)

to make automated test coverage an integral part of our feature and bugfix development process. So, as a first attempt, we've decided to extend kernelci test v4l2 plan support, leading the way to extending other subsystems' test plans. Currently, kernelci looks for a list of branches every hour

[PATCH] media: rc: self test for IR encoders and decoders

for this test. Signed-off-by: Sean Young Cc: Shuah Khan --- tools/testing/selftests/Makefile | 1 + tools/testing/selftests/ir/.gitignore | 1 + tools/testing/selftests/ir/Makefile | 5 + tools/testing/selftests/ir/ir_loopback.c | 199 ++ tools/testing

Working test 5

Did you get my email from last week? Let me know if you have photos for cutting out or retouching? We are an image team who can do editing for your the web store photos, industry photos or portrait photos. Send photos, we will do testing for you to check quality. Waiting for your reply soon.

Working test 3

Did you get my email from last week? Let me know if you have photos for cutting out or retouching? We are an image team who can do editing for your the web store photos, industry photos or portrait photos. Send photos, we will do testing for you to check quality. Waiting for your reply soon.

Working test 3

Did you get my email from last week? Let me know if you have photos for cutting out or retouching? We are an image team who can do editing for your the web store photos, industry photos or portrait photos. Send photos, we will do testing for you to check quality. Waiting for your reply soon.

Working test 4

Did you get my email from last week? Let me know if you have photos for cutting out or retouching? We are an image team who can do editing for your the web store photos, industry photos or portrait photos. Send photos, we will do testing for you to check quality. Waiting for your reply soon.

Re: [PATCH 2/2] media: rc: self test for IR encoders and decoders

git a/tools/testing/selftests/Makefile > > b/tools/testing/selftests/Makefile > > index f1fe492c8e17..995034ea5546 100644 > > --- a/tools/testing/selftests/Makefile > > +++ b/tools/testing/selftests/Makefile > > @@ -15,6 +15,7 @@ TARGETS += futex > > TARGETS

Re: [PATCH 2/2] media: rc: self test for IR encoders and decoders

100644 > --- a/tools/testing/selftests/Makefile > +++ b/tools/testing/selftests/Makefile > @@ -15,6 +15,7 @@ TARGETS += futex > TARGETS += gpio > TARGETS += intel_pstate > TARGETS += ipc > +TARGETS += ir Does this test depend on any hardware being present in the system? >

[RFCv3 PATCH 3/3] vimc: add property test code

From: Hans Verkuil Add properties to entities and pads to be able to test the properties API. Signed-off-by: Hans Verkuil --- drivers/media/platform/vimc/vimc-common.c | 50 +++ 1 file changed, 50 insertions(+) diff --git a/drivers/media/platform/vimc/vimc-common.c b

[RFCv2 PATCH 3/3] vimc: add test properties

From: Hans Verkuil Signed-off-by: Hans Verkuil --- drivers/media/platform/vimc/vimc-common.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/media/platform/vimc/vimc-common.c b/drivers/media/platform/vimc/vimc-common.c index 617415c224fe..db8a8d1eca54 100644

[RFC PATCH 3/3] vimc: add test properties

From: Hans Verkuil Signed-off-by: Hans Verkuil --- drivers/media/platform/vimc/vimc-common.c | 18 ++ drivers/media/platform/vimc/vimc-core.c | 6 +++--- 2 files changed, 21 insertions(+), 3 deletions(-) diff --git a/drivers/media/platform/vimc/vimc-common.c

Re: [PATCH v3 4/4] selftests: media_tests: Add a memory-to-memory concurrent stress test

Hi Ezequiel, On 01/08/18 22:50, Ezequiel Garcia wrote: Add a test for the memory-to-memory framework, to exercise the scheduling of concurrent jobs, using multiple contexts. This test needs to be run using the vim2m virtual driver, and so needs no hardware. While here, rework the media_tests

[PATCH v4 6/6] selftests: media_tests: Add a memory-to-memory concurrent stress test

Add a test for the memory-to-memory framework, to exercise the scheduling of concurrent jobs, using multiple contexts. This test needs to be run using the vim2m virtual driver, and so needs no hardware. While here, rework the media_tests suite in order to make it useful for automatic tools

Re: [PATCH] media: imx258: remove test pattern map from driver

Hi Jason, On Thu, Aug 02, 2018 at 04:17:00PM +0800, jasonx.z.c...@intel.com wrote: > From: "Chen, JasonX Z" > > Test Pattern mode be picked at HAL instead of driver. > do a FLIP when userspace use test pattern mode. > add entity_ops for validating imx258 link.

[PATCH] media: imx258: remove test pattern map from driver

From: "Chen, JasonX Z" Test Pattern mode be picked at HAL instead of driver. do a FLIP when userspace use test pattern mode. add entity_ops for validating imx258 link. Signed-off-by: Chen, JasonX Z --- drivers/media/i2c/imx258.c | 28 1 file changed, 8

[PATCH v3 4/4] selftests: media_tests: Add a memory-to-memory concurrent stress test

Add a test for the memory-to-memory framework, to exercise the scheduling of concurrent jobs, using multiple contexts. This test needs to be run using the vim2m virtual driver, and so needs no hardware. While here, rework the media_tests suite in order to make it useful for automatic tools

[PATCH v2 5/5] selftests: media_tests: Add a memory-to-memory concurrent stress test

Add a test for the memory-to-memory framework, to exercise the scheduling of concurrent jobs, using multiple contexts. This test needs to be run using the vim2m virtual driver, and so needs no hardware. Signed-off-by: Ezequiel Garcia --- tools/testing/selftests/media_tests/Makefile | 4

[PATCH 2/2] media: rc: self test for IR encoders and decoders

ier: GPL-2.0 +// test ir decoder +// +// Copyright (C) 2018 Sean Young + +// When sending LIRC_MODE_SCANCODE, the IR will be encoded. rc-loopback +// will send this IR to the receiver side, where we try to read the decoded +// IR. Decoding happens in a separate kernel thread, so we will need to +// w

Re: [PATCH 07/16] media: exymos4-is: allow compile test for EXYNOS FIMC-LITE

On 04/05/2018 07:54 PM, Mauro Carvalho Chehab wrote: > There's nothing that prevents building this driver with > COMPILE_TEST. So, enable it. > > While here, make the Kconfig dependency cleaner by removing > the unneeded if block. > > Signed-off-by: Mauro Carvalho Chehab

[PATCH v2 07/19] media: exymos4-is: allow compile test for EXYNOS FIMC-LITE

There's nothing that prevents building this driver with COMPILE_TEST. So, enable it. While here, make the Kconfig dependency cleaner by removing the unneeded if block. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/platform/exynos4-is/Kconfig | 4 +--- 1 file

[PATCH 07/16] media: exymos4-is: allow compile test for EXYNOS FIMC-LITE

There's nothing that prevents building this driver with COMPILE_TEST. So, enable it. While here, make the Kconfig dependency cleaner by removing the unneeded if block. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/platform/exynos4-is/Kconfig | 4 +--- 1 file

[v4l-utils RFC 0/6] Mediatext test program for request API tests

Hi folks, Here's a refreshed RFC set to add the mediatext test program. It is well suited for testing requests, as it can work with multiple devices simultaneously as well as is easy to control through a bash script. Only buffers are supported with requests, controls are not yet; still adding

[PATCH v4l-utils] v4l2-compliance/v4l2-test-formats: fix typo

When using planar formats, we want to check pix_mp, not pix. Signed-off-by: Alexandre Courbot <acour...@chromium.org> --- utils/v4l2-compliance/v4l2-test-formats.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/v4l2-compliance/v4l2-test-formats.cpp b/util

Re: Please help test the new v4l-subdev support in v4l2-compliance

eb 3, 2018 at 7:56 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: >> >>>> >>>> With regards to the 3 failures: >>>> >>>> 1. test VIDIOC_G/S_EDID: FAIL >>>> This is a valid catch where I was returning -EINVAL when the caller >

Re: Please help test the new v4l-subdev support in v4l2-compliance

On 02/06/2018 07:48 PM, Tim Harvey wrote: > On Mon, Feb 5, 2018 at 11:34 PM, Hans Verkuil <hverk...@xs4all.nl> wrote: >> On 02/06/2018 08:16 AM, Tim Harvey wrote: >>> On Sat, Feb 3, 2018 at 7:56 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: > >>> >>&

Re: Please help test the new v4l-subdev support in v4l2-compliance

On Mon, Feb 5, 2018 at 11:34 PM, Hans Verkuil <hverk...@xs4all.nl> wrote: > On 02/06/2018 08:16 AM, Tim Harvey wrote: >> On Sat, Feb 3, 2018 at 7:56 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: >> >> With regards to the 3 failures: >> >> 1. test V

Re: Please help test the new v4l-subdev support in v4l2-compliance

On 02/06/2018 08:16 AM, Tim Harvey wrote: > On Sat, Feb 3, 2018 at 7:56 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: >> Hi Tim, Jacopo, >> >> I have now finished writing the v4l2-compliance tests for the various >> v4l-subdev >> ioctls. I ma

Re: Please help test the new v4l-subdev support in v4l2-compliance

On Sat, Feb 3, 2018 at 7:56 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: > Hi Tim, Jacopo, > > I have now finished writing the v4l2-compliance tests for the various > v4l-subdev > ioctls. I managed to test some with the vimc driver, but that doesn't > implement all >

Re: Please help test the new v4l-subdev support in v4l2-compliance

Em Mon, 5 Feb 2018 18:01:34 +0100 Hans Verkuil escreveu: > On 02/05/2018 05:59 PM, Hans Verkuil wrote: > > On 02/05/2018 05:55 PM, Mauro Carvalho Chehab wrote: > >> Em Mon, 5 Feb 2018 14:37:29 -0200 > >> Mauro Carvalho Chehab escreveu: > >> > >>> Em

Re: Please help test the new v4l-subdev support in v4l2-compliance

On 02/05/2018 05:59 PM, Hans Verkuil wrote: > On 02/05/2018 05:55 PM, Mauro Carvalho Chehab wrote: >> Em Mon, 5 Feb 2018 14:37:29 -0200 >> Mauro Carvalho Chehab escreveu: >> >>> Em Mon, 5 Feb 2018 08:21:54 -0800 >>> Tim Harvey escreveu: >>> Hans,

Re: Please help test the new v4l-subdev support in v4l2-compliance

On 02/05/2018 05:55 PM, Mauro Carvalho Chehab wrote: > Em Mon, 5 Feb 2018 14:37:29 -0200 > Mauro Carvalho Chehab escreveu: > >> Em Mon, 5 Feb 2018 08:21:54 -0800 >> Tim Harvey escreveu: >> >>> Hans, >>> >>> I'm failing compile (of master 4ee9911) with:

Re: Please help test the new v4l-subdev support in v4l2-compliance

On 02/05/2018 05:37 PM, Mauro Carvalho Chehab wrote: > Em Mon, 5 Feb 2018 08:21:54 -0800 > Tim Harvey escreveu: > >> Hans, >> >> I'm failing compile (of master 4ee9911) with: >> >> CXX v4l2_compliance-media-info.o >> media-info.cpp: In function ‘media_type

Re: Please help test the new v4l-subdev support in v4l2-compliance

Em Mon, 5 Feb 2018 14:37:29 -0200 Mauro Carvalho Chehab escreveu: > Em Mon, 5 Feb 2018 08:21:54 -0800 > Tim Harvey escreveu: > > > Hans, > > > > I'm failing compile (of master 4ee9911) with: > > > > CXX v4l2_compliance-media-info.o > >

Re: Please help test the new v4l-subdev support in v4l2-compliance

On Mon, Feb 5, 2018 at 8:27 AM, Hans Verkuil wrote: > On 02/05/2018 05:21 PM, Tim Harvey wrote: > > > >> >> I ran a 'make distclean; ./bootstrap.sh && ./configure && make' >> >> last version I built successfully was '1bb8c70 v4l2-ctl: mention that >> --set-subdev-fps is for

Re: Please help test the new v4l-subdev support in v4l2-compliance

Em Mon, 5 Feb 2018 08:21:54 -0800 Tim Harvey escreveu: > Hans, > > I'm failing compile (of master 4ee9911) with: > > CXX v4l2_compliance-media-info.o > media-info.cpp: In function ‘media_type media_detect_type(const char*)’: > media-info.cpp:79:39: error: no

Re: Please help test the new v4l-subdev support in v4l2-compliance

On 02/05/2018 05:21 PM, Tim Harvey wrote: > > I ran a 'make distclean; ./bootstrap.sh && ./configure && make' > > last version I built successfully was '1bb8c70 v4l2-ctl: mention that > --set-subdev-fps is for testing only' That's a lot of revisions ago. I've been busy last weekend :-) Do a

Re: Please help test the new v4l-subdev support in v4l2-compliance

On Sat, Feb 3, 2018 at 7:56 AM, Hans Verkuil <hverk...@xs4all.nl> wrote: > Hi Tim, Jacopo, > > I have now finished writing the v4l2-compliance tests for the various > v4l-subdev > ioctls. I managed to test some with the vimc driver, but that doesn't > implement all >

Please help test the new v4l-subdev support in v4l2-compliance

Hi Tim, Jacopo, I have now finished writing the v4l2-compliance tests for the various v4l-subdev ioctls. I managed to test some with the vimc driver, but that doesn't implement all ioctls, so I could use some help testing my test code :-) To test you first need to apply these patches to your

Re: [PATCH] sh: clk: Relax clk rate match test

Hi Jacopo, On Friday, 26 January 2018 18:24:54 EET jacopo mondi wrote: > On Thu, Jan 25, 2018 at 03:39:32PM +0100, Geert Uytterhoeven wrote: > > Hi Jacopo, > > [snip] > > --- > > drivers/sh/clk/core.c | 9 ++--- > 1 file changed, 6 insertions(+), 3 deletions(-) >

Re: [PATCH] sh: clk: Relax clk rate match test

Hi Geert, On Thu, Jan 25, 2018 at 03:39:32PM +0100, Geert Uytterhoeven wrote: > Hi Jacopo, [snip] > >> > --- > >> > drivers/sh/clk/core.c | 9 ++--- > >> > 1 file changed, 6 insertions(+), 3 deletions(-) > >> > > >> > diff --git a/drivers/sh/clk/core.c b/drivers/sh/clk/core.c > >> > index

Re: [PATCH] sh: clk: Relax clk rate match test

>> >> On Thu, Jan 25, 2018 at 12:24 PM, Jacopo Mondi >> <jacopo+rene...@jmondi.org> wrote: >> > When asking for a clk rate to be set, the sh core clock matches only >> > exact rate values against the calculated frequency table entries. If the >>

Re: [PATCH] sh: clk: Relax clk rate match test

ene...@jmondi.org> wrote: > > When asking for a clk rate to be set, the sh core clock matches only > > exact rate values against the calculated frequency table entries. If the > > rate does not match exactly the test fails, and the whole frequency > > table is walked, resu

Re: [PATCH] sh: clk: Relax clk rate match test

rate values against the calculated frequency table entries. If the > rate does not match exactly the test fails, and the whole frequency > table is walked, resulting in selection of the last entry, corresponding to > the lowest available clock rate. IIUIC, the code does not select the la

[PATCH] sh: clk: Relax clk rate match test

When asking for a clk rate to be set, the sh core clock matches only exact rate values against the calculated frequency table entries. If the rate does not match exactly the test fails, and the whole frequency table is walked, resulting in selection of the last entry, corresponding to the lowest

Re: [patch] libv4l2: SDL test application

On Mon 2017-10-30 17:30:53, Hans Verkuil wrote: > Hi Pavel, > > On 10/28/2017 09:57 PM, Pavel Machek wrote: > > Add support for simple SDL test application. Allows taking jpeg > > snapshots, and is meant to run on phone with touchscreen. Not > > particulary useful on

Re: [patch] libv4l2: SDL test application

On 10/30/2017 05:41 PM, Pali Rohár wrote: > On Monday 30 October 2017 17:30:53 Hans Verkuil wrote: >> Hi Pavel, >> >> On 10/28/2017 09:57 PM, Pavel Machek wrote: >>> Add support for simple SDL test application. Allows taking jpeg >>> snapshots, and is

Re: [patch] libv4l2: SDL test application

On Monday 30 October 2017 17:30:53 Hans Verkuil wrote: > Hi Pavel, > > On 10/28/2017 09:57 PM, Pavel Machek wrote: > > Add support for simple SDL test application. Allows taking jpeg > > snapshots, and is meant to run on phone with touchscreen. Not > > particula

Re: [patch] libv4l2: SDL test application

Hi Pavel, On 10/28/2017 09:57 PM, Pavel Machek wrote: > Add support for simple SDL test application. Allows taking jpeg > snapshots, and is meant to run on phone with touchscreen. Not > particulary useful on PC with webcam, but should work. When I try to build this I get: make[3]:

[patch] libv4l2: SDL test application

Add support for simple SDL test application. Allows taking jpeg snapshots, and is meant to run on phone with touchscreen. Not particulary useful on PC with webcam, but should work. Signed-off-by: Pavel Machek <pa...@ucw.cz> diff --git a/configure.ac b/configure.ac index f3691be..f6540c2

[PATCH 5/5] keytable: show lirc device and make test show lirc scancodes

fprintf(stderr, _("\tLirc device: %s\n"), + rc_dev->lirc_name); fprintf(stderr, _("\tSupported protocols: ")); write_sysfs_protocols(rc_dev->supported, stder

[PATCH 3/4] venus: fix compile-test build on non-qcom ARM platform

/venus-core.ko] undefined! This changes the 'select' statement again, so we only try to enable those symbols when the drivers will actually get built, and explicitly test for QCOM_MDT_LOADER to be enabled before calling into it. Fixes: 76724b30f222 ("[media] media: venus: enable building with COM

[PATCH v2] [media] venus: fix compile-test build on non-qcom ARM platform

ect' statement again, so we only try to enable those symbols when the drivers will actually get built, and explicitly test for QCOM_MDT_LOADER to be enabled before calling into it. Fixes: 76724b30f222 ("[media] media: venus: enable building with COMPILE_TEST") Signed-off-by: Arnd Bergma

Re: [PATCH 3/3] [media] venus: fix compile-test build on non-qcom ARM platform

st came after me as well, as I hit another corner case, we need this fixup on top, I'll send a replacement: Subject: [PATCH] fixup! [media] venus: fix compile-test build on non-qcom ARM platform Signed-off-by: Arnd Bergmann <a...@arndb.de> diff --git a/drivers/media/platform/qcom/venus

Re: [PATCH 3/3] [media] venus: fix compile-test build on non-qcom ARM platform

Hi Arnd, On 27.06.2017 18:02, Arnd Bergmann wrote: If QCOM_MDT_LOADER is enabled, but ARCH_QCOM is not, we run into a build error: ERROR: "qcom_mdt_load" [drivers/media/platform/qcom/venus/venus-core.ko] undefined! ERROR: "qcom_mdt_get_size" [drivers/media/platform/qcom/venus/venus-core.ko]

[PATCH 3/3] [media] venus: fix compile-test build on non-qcom ARM platform

If QCOM_MDT_LOADER is enabled, but ARCH_QCOM is not, we run into a build error: ERROR: "qcom_mdt_load" [drivers/media/platform/qcom/venus/venus-core.ko] undefined! ERROR: "qcom_mdt_get_size" [drivers/media/platform/qcom/venus/venus-core.ko] undefined! This changes the 'select' statement again,

Re: [[media] rc] e662671619: BUG: kernel hang in test stage

On Mon, May 08, 2017 at 08:13:37PM +0800, kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > commit e66267161971155a8b4

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

  1   2   3   4   5   >