Re: [PATCH] v4l2-core/v4l2-ctrls: Filter NOOP CH_RANGE events

On 11/11/15 12:58, Ricardo Ribalda Delgado wrote: > If modify_range is called but no range is changed, do not send the > CH_RANGE event. While not opposed to this patch, I do wonder what triggered this patch? Is it just a matter of efficiency? And since it is a driver that calls this, shouldn't

Re: Slow path and cpu lock warnings - MC Next Gen

Em Mon, 09 Nov 2015 08:55:06 -0700 Shuah Khan escreveu: > On 11/09/2015 08:51 AM, Shuah Khan wrote: > > As I mentioned on the IRC, here is the log for the problems I am seeing. > > I have to do eject HVR 950Q TV stick to see the problem. > > > > mc_next_gen.v8.4 branch

Re: PVR-250 Composite 3 unavailable [Re: ivtv driver]

Em Fri, 06 Nov 2015 10:36:08 -0700 Warren Sturm escreveu: > On Mon, 2015-10-26 at 19:49 -0400, Andy Walls wrote: > > On October 26, 2015 7:13:52 PM EDT, Warren Sturm < > > warren.st...@gmail.com> wrote: > > > Hi Andy. > > > > > > I don't know whether this was intended

Re: [RFC] Documentation: dontdiff: remove media from dontdiff

On Fri, 30 Oct 2015 01:15:39 +0800 Wang YanQing wrote: > media will hide all the changes in drivers/media. > > Signed-off-by: Wang YanQing > --- > I don't know whether it is still acceptable to patch dontdiff, > so I add Linus to CC list. As long as

[PATCH 2/2] [media] include/media: move platform driver headers to a separate dir

Let's not mix headers used by the core with those headers that are needed by some specific platform drivers. This patch was made via this script: mkdir include/media/platform for i in include/media/*.h; do n=`basename $i`; (for j in $(git grep -l $n); do dirname $j;

[PATCH] [media] hackrf: don't emit dev debug on a kfree'd or null dev

From: Colin Ian King Static analysis with smatch detected a couple of issues: drivers/media/usb/hackrf/hackrf.c:1533 hackrf_probe() error: we previously assumed 'dev' could be null (see line 1366) drivers/media/usb/hackrf/hackrf.c:1533 hackrf_probe() error:

Re: [PATCH] [media] hackrf: don't emit dev debug on a kfree'd or null dev

On 11/11/2015 05:05 PM, Colin King wrote: From: Colin Ian King Static analysis with smatch detected a couple of issues: drivers/media/usb/hackrf/hackrf.c:1533 hackrf_probe() error: we previously assumed 'dev' could be null (see line 1366)

Re: Slow path and cpu lock warnings - MC Next Gen

On 11/11/2015 08:36 AM, Mauro Carvalho Chehab wrote: > Em Wed, 11 Nov 2015 07:22:47 -0700 > Shuah Khan escreveu: > >> On 11/11/2015 05:30 AM, Mauro Carvalho Chehab wrote: >>> Em Mon, 09 Nov 2015 08:55:06 -0700 >>> Shuah Khan escreveu: >>>

Re: Slow path and cpu lock warnings - MC Next Gen

Em Wed, 11 Nov 2015 07:22:47 -0700 Shuah Khan escreveu: > On 11/11/2015 05:30 AM, Mauro Carvalho Chehab wrote: > > Em Mon, 09 Nov 2015 08:55:06 -0700 > > Shuah Khan escreveu: > > > >> On 11/09/2015 08:51 AM, Shuah Khan wrote: > >>> As I

[PATCH 2/2] [media] ivtv: avoid going past input/audio array As reported by smatch: drivers/media/pci/ivtv/ivtv-driver.c:832 ivtv_init_struct2() error: buffer overflow 'itv->card->video_inputs' 6 <=

drivers/media/pci/ivtv/ivtv-driver.c:832 ivtv_init_struct2() error: buffer overflow 'itv->card->video_inputs' 6 <= 6 Signed-off-by: Mauro Carvalho Chehab diff --git a/drivers/media/pci/ivtv/ivtv-driver.c b/drivers/media/pci/ivtv/ivtv-driver.c index

Re: [PATCH 1/1] v4l2-device: Don't unregister ACPI/Device Tree based devices

On 11/11/15 14:50, Sakari Ailus wrote: > From: Tommi Franttila > > When a V4L2 sub-device backed by a DT or ACPI based device was removed, > the device was unregistered as well which certainly was not intentional, > as the client device would not be re-created by

Re: Slow path and cpu lock warnings - MC Next Gen

On 11/11/2015 05:30 AM, Mauro Carvalho Chehab wrote: > Em Mon, 09 Nov 2015 08:55:06 -0700 > Shuah Khan escreveu: > >> On 11/09/2015 08:51 AM, Shuah Khan wrote: >>> As I mentioned on the IRC, here is the log for the problems I am seeing. >>> I have to do eject HVR 950Q TV

Re: [PATCH] v4l2-core/v4l2-ctrls: Filter NOOP CH_RANGE events

On 11/11/15 13:20, Ricardo Ribalda Delgado wrote: > Hello Hans > > On my cameras, the framerate can be controlled in very fine steps (so > you can be in sync with the conveyor belt). The exposure time is > dependent on the framerate. I was calling modify_range every time > there was a change on

[PATCH 1/1] v4l2-device: Don't unregister ACPI/Device Tree based devices

From: Tommi Franttila When a V4L2 sub-device backed by a DT or ACPI based device was removed, the device was unregistered as well which certainly was not intentional, as the client device would not be re-created by simply reinstating the V4L2 sub-device (indeed the

[PATCH 2/2 v2] [media] ivtv: avoid going past input/audio array

As reported by smatch: drivers/media/pci/ivtv/ivtv-driver.c:832 ivtv_init_struct2() error: buffer overflow 'itv->card->video_inputs' 6 <= 6 drivers/media/pci/ivtv/ivtv-driver.c:832 ivtv_init_struct2() error: buffer overflow 'itv->card->video_inputs' 6 <= 6 Signed-off-by: Mauro Carvalho

Re: [PATCH] v4l2-core/v4l2-ctrls: Filter NOOP CH_RANGE events

Hello Hans On my cameras, the framerate can be controlled in very fine steps (so you can be in sync with the conveyor belt). The exposure time is dependent on the framerate. I was calling modify_range every time there was a change on the framerate on all the different heads. Leading to

[PATCH] v4l2-core/v4l2-ctrls: Filter NOOP CH_RANGE events

If modify_range is called but no range is changed, do not send the CH_RANGE event. Reported-by: Dimitrios Katsaros Signed-off-by: Ricardo Ribalda Delgado --- drivers/media/v4l2-core/v4l2-ctrls.c | 23 ++- 1 file changed, 14

Re: Slow path and cpu lock warnings - MC Next Gen

On 11/11/2015 05:25 PM, Shuah Khan wrote: > On 11/11/2015 08:49 AM, Shuah Khan wrote: >> On 11/11/2015 08:36 AM, Mauro Carvalho Chehab wrote: >>> Em Wed, 11 Nov 2015 07:22:47 -0700 >>> Shuah Khan escreveu: >>> On 11/11/2015 05:30 AM, Mauro Carvalho Chehab wrote:

[no subject]

Hi, I sent a patch named "[PATCH] tv tuner max2165 driver: extend frequency range" two weeks ago (22/10). Is it being reviewed? Thank you. Walter Cheuk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo

Re: Slow path and cpu lock warnings - MC Next Gen

On 11/11/2015 08:49 AM, Shuah Khan wrote: > On 11/11/2015 08:36 AM, Mauro Carvalho Chehab wrote: >> Em Wed, 11 Nov 2015 07:22:47 -0700 >> Shuah Khan escreveu: >> >>> On 11/11/2015 05:30 AM, Mauro Carvalho Chehab wrote: Em Mon, 09 Nov 2015 08:55:06 -0700 Shuah

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 Nov 12 04:00:17 CET 2015 git branch: test git hash: 79f5b6ae960d380c829fb67d5dadcd1d025d2775 gcc

Re: v4l vs. dpdk

On 11/12/2015 07:54 AM, Ran Shalit wrote: > Hello, > > I hope you can assist me on the following debate. > > I need to develop a driver/application which capture and output video > frames from PCIe device , and is using Intel cpu (i7), and Intel's > media sdk server framework for the video

v4l vs. dpdk

Hello, I hope you can assist me on the following debate. I need to develop a driver/application which capture and output video frames from PCIe device , and is using Intel cpu (i7), and Intel's media sdk server framework for the video compression. I am not sure what will be a better choice

[PATCH 2/3] ARM64: add tegra-vi support in T210 device-tree

Following device tree support for Tegra VI now: - "vi" node which might have 6 ports/endpoints - in TPG mode, "vi" node don't need to define any ports/endpoints - ports/endpoints defines the link between VI and external sensors. Signed-off-by: Bryan Wu ---

[PATCH 3/3] Documentation: DT bindings: add VI and CSI bindings

Signed-off-by: Bryan Wu --- .../display/tegra/nvidia,tegra20-host1x.txt| 211 - 1 file changed, 205 insertions(+), 6 deletions(-) diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt

[PATCH 0/3 RFC v5] media: platform: add NVIDIA Tegra VI driver

This patchset add and enable V4L2 driver for latest NVIDIA Tegra Video Input hardware controller. It's based on the staging/work branch of Thierry Reding Tegra upstream kernel github repo, which is based on 4.3.0-next-20151106. (https://github.com/thierryreding/linux/tree/staging/work) v5: -

[PATCH 1/3] [media] v4l: tegra: Add NVIDIA Tegra VI driver

NVIDIA Tegra processor contains a powerful Video Input (VI) hardware controller which can support up to 6 MIPI CSI camera sensors. This patch adds a V4L2 media controller and capture driver to support Tegra VI hardware. It's verified with Tegra built-in test pattern generator. Signed-off-by:

Re: [PATCH 4/4] v4l2-mem2mem: allow reqbufs(0) with "in use" MMAP buffers

Hi, 2015-11-02 19:31 GMT+01:00 Nicolas Dufresne : > Le mardi 08 avril 2014 à 12:51 +0200, Marek Szyprowski a écrit : >> Hello, >> >> On 2014-04-07 16:41, Kamil Debski wrote: >> > Pawel, Marek, >> > >> > Before taking this to my tree I wanted to get an ACK from one

Re: [PATCH 2/2] [media] include/media: move platform driver headers to a separate dir

On Wednesday 11 November 2015 15:14:48 Mauro Carvalho Chehab wrote: > rename include/media/{ => platform}/exynos-fimc.h (100%) > rename include/media/{ => platform}/mmp-camera.h (100%) > rename include/media/{ => platform}/omap1_camera.h (100%) > rename include/media/{ => platform}/omap4iss.h

Re: [PATCH 1/1] omap3isp: preview: Mark output buffer done first

Hi Sakari, Thank you for the patch. On Wednesday 11 November 2015 01:34:18 Sakari Ailus wrote: > The sequence number counter is incremented on each output buffer, and that > incremented value is used as the sequence number of that buffer. The input > buffer sequence numbering is based just on

Re: [PATCH] media: adv7180: increase delay after reset to 5ms

Hi Ulrich, (CC'ing Lars-Peter Clausen) Thank you for the patch. On Tuesday 10 November 2015 14:39:00 Ulrich Hecht wrote: > Initialization of the ADV7180 chip fails on the Renesas R8A7790-based > Lager board about 50% of the time. This patch resolves the issue by > increasing the minimum delay

[PATCH 1/1] smiapp: Move include/media/smiapp.h under include/media/i2c

Signed-off-by: Sakari Ailus --- Hi Mauro, Your script appears to miss smiapp as it's in a separate directory. Could you either change the script, or apply this patch, please? Kind regards, Sakari MAINTAINERS | 2 +- drivers/media/i2c/smiapp/smiapp.h