WinTV-HVR-2255 saa7164 and linux kernel 4.1.27

I recently replaced a broken WinTV-HVR-2250 with an WinTV-HVR-2255. I knew that the 2255 was supported in kernel 4.2, what I didn't know was that the latest stable version of my distro (opensuse) only used 4.1. I was on 13.2 with kernel 3.16 at the time of the upgrade. Anyway, is it possible

cron job: media_tree daily build: WARNINGS

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 Sep 22 04:00:17 CEST 2016 git branch: test git hash: 142a0e11b52c18a82c4fe55132b762005dda05c0 gcc

Supported, available Dual ATSC tuner? If not, I'll pay you to make one work!

I'm sure this is one of the most commonly asked question on this list, and for that I apologize, but I've tried reading all the information that I can find about this online, and I just can't figure it out, so here goes... Is there actually a USB or PCI, ATSC, DVB-T device with two tuners that I

[PATCH] [media] tw5864: crop picture width to 704

Previously, width of 720 was used, but it gives 16-pixel wide black bar at right side of encoded picture. Signed-off-by: Andrey Utkin --- drivers/media/pci/tw5864/tw5864-reg.h | 8 drivers/media/pci/tw5864/tw5864-video.c | 13 +++-- 2 files

[PATCH] [media] solo6x10: avoid delayed register write

This fixes a lockup at device probing which happens on some solo6010 hardware samples. This is a regression introduced by commit e1ceb25a1569 ("[media] SOLO6x10: remove unneeded register locking and barriers") The observed lockup happens in solo_set_motion_threshold() called from

Re: [PATCH v5 2/2] media: Add a driver for the ov5645 camera sensor.

Hi Todor, Todor Tomov wrote: > Hi Sakari, > > One more question below: > > On 08/25/2016 10:18 AM, Sakari Ailus wrote: > + > +static struct v4l2_subdev_core_ops ov5645_core_ops = { > + .s_power = ov5645_s_power, > +}; > + > +static struct v4l2_subdev_video_ops

[PATCH -next] [media] cx88: fix error return code in cx8802_dvb_probe()

From: Wei Yongjun Fix to return error code -ENODEV from the error handling case instead of 0(err maybe overwrited to 0 in the for loop), as done elsewhere in this function. Signed-off-by: Wei Yongjun --- drivers/media/pci/cx88/cx88-dvb.c | 1 +

[PATCH -next] [media] bdisp: fix error return code in bdisp_probe()

From: Wei Yongjun Fix to return error code -EINVAL from the platform_get_resource() error handling case instead of 0, as done elsewhere in this function. Signed-off-by: Wei Yongjun --- drivers/media/platform/sti/bdisp/bdisp-v4l2.c | 1 + 1 file

Re: g_webcam Isoch high bandwidth transfer

On Wed, Sep 21, 2016 at 08:27:02AM -0500, Bin Liu wrote: > On Wed, Sep 21, 2016 at 11:01:21AM +0300, Felipe Balbi wrote: > > > > Hi, > > > > Bin Liu writes: > > > Hi, > > > > > > I am trying to check Isoch high bandwidth transfer with g_webcam.ko in > > > high-speed connection. >

Re: [PATCH v5 2/2] media: Add a driver for the ov5645 camera sensor.

Hi Sakari, One more question below: On 08/25/2016 10:18 AM, Sakari Ailus wrote: + +static struct v4l2_subdev_core_ops ov5645_core_ops = { + .s_power = ov5645_s_power, +}; + +static struct v4l2_subdev_video_ops ov5645_video_ops = { + .s_stream =

Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression)

On Wed, Sep 21, 2016 at 03:16:57PM +0200, Krzysztof Hałasa wrote: > Hans Verkuil writes: > > > That was probably the reason for the pci_read_config_word in the reg_write > > code. Try putting that back (and just that). > > Yes. I guess a single pci_read_config_word() would

Re: [RFC PATCH 5/7] ov7670: add devicetree support

Hi Hans, On Friday 26 Aug 2016 09:45:25 Hans Verkuil wrote: > On 08/17/2016 02:44 PM, Laurent Pinchart wrote: > > On Wednesday 17 Aug 2016 08:29:41 Hans Verkuil wrote: > >> From: Hans Verkuil > >> > >> Add DT support. Use it to get the reset and pwdn pins (if there are

Re: solo6010 modprobe lockup since e1ceb25a (v4.3 regression)

Hans Verkuil writes: > That was probably the reason for the pci_read_config_word in the reg_write > code. Try putting that back (and just that). Yes. I guess a single pci_read_config_word() would suffice. Though it would obviously be much better to identify the place in the

Re: g_webcam Isoch high bandwidth transfer

On Wed, Sep 21, 2016 at 11:01:21AM +0300, Felipe Balbi wrote: > > Hi, > > Bin Liu writes: > > Hi, > > > > I am trying to check Isoch high bandwidth transfer with g_webcam.ko in > > high-speed connection. > > > > First I hacked webcam.c as follows to enable 640x480@30fps mode. > >

[PATCH -next] [media] gs1662: remove .owner field for driver

From: Wei Yongjun Remove .owner field if calls are used which set it automatically. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Wei Yongjun --- drivers/media/spi/gs1662.c | 1 - 1 file changed, 1 deletion(-)

[PATCH -next] [media] gs1662: drop kfree for memory allocated with devm_kzalloc

From: Wei Yongjun It's not necessary to free memory allocated with devm_kzalloc and using kfree leads to a double free. Fixes: 7aae6e2df127 ("[media] Add GS1662 driver, a video serializer") Signed-off-by: Wei Yongjun ---

Re: [RFC PATCH 5/7] ov7670: add devicetree support

Hello Sakari, On Wednesday 21 Sep 2016 14:33:29 Sakari Ailus wrote: > Hi Laurent, > > On Wed, Aug 17, 2016 at 03:44:00PM +0300, Laurent Pinchart wrote: > > > + assigned-clock-rates = <2400>; > > > > You should compute and set the clock rate dynamically in the driver, not > >

Re: [RFC PATCH 5/7] ov7670: add devicetree support

Hi Laurent, On Wed, Aug 17, 2016 at 03:44:00PM +0300, Laurent Pinchart wrote: > > + assigned-clock-rates = <2400>; > > You should compute and set the clock rate dynamically in the driver, not > hardcode it in DT. This frequency is typically defined by hardware engineers

Re: [RFC PATCH 4/7] ov7670: get xvclk

Hi Hans, On Wed, Aug 17, 2016 at 08:29:40AM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Get the clock for this sensor. > > Signed-off-by: Hans Verkuil > --- > drivers/media/i2c/ov7670.c | 15 +++ > 1 file changed, 15

Re: [RFC PATCH 5/7] ov7670: add devicetree support

Hi Hans, On Wed, Aug 17, 2016 at 08:29:41AM +0200, Hans Verkuil wrote: > From: Hans Verkuil > > Add DT support. Use it to get the reset and pwdn pins (if there are any). > Tested with one sensor requiring reset/pwdn and one sensor that doesn't > have reset/pwdn pins. >

Re: [RFC] Remove row numbers from tables in V4L2 documentation

Hi Markus, On Wednesday 21 Sep 2016 11:24:33 Markus Heiser wrote: > Am 21.09.2016 um 10:48 schrieb Laurent Pinchart: > > Hello, > > > > While documenting the metadata API I got annoyed by how tables were > > converted from DocBook to ReST. > > I suggested to drop them, but Mauro wanted to

[PATCH] [media] rc: split nec protocol into its three variants

Currently we do not know what variant (bit length) of the nec protocol is used, other than from guessing from the length of the scancode. Now nec will be handled the same way as the sony protocol or the rc6 protocol; one variant per bit length. In the future we might want to expose the rc

[PATCH] [media/input] rc: report rc protocol type to userspace through input

We might want to know what protocol a remote uses when we do not know. With this patch and another patch for v4l-utils (follows), you can do that with: ./ir-keytable -p rc-5,nec,rc-6,jvc,sony,sanyo,sharp,xmp -t Testing events. Please, press CTRL-C to abort. 1474415431.689685: event type

[PATCH] [media] v4l-utils: report rc protocol while testing

If you have a remote and want to see what protocol it uses, simply run the following. That's enough to write a new keymap. ./ir-keytable -p rc-5,nec,rc-6,jvc,sony,sanyo,sharp,xmp -t Testing events. Please, press CTRL-C to abort. 1474415431.689685: event type EV_MSC(0x04): protocol =

Re: [RFC] Remove row numbers from tables in V4L2 documentation

Am 21.09.2016 um 10:48 schrieb Laurent Pinchart : > Hello, > > While documenting the metadata API I got annoyed by how tables were converted > from DocBook to ReST. I suggested to drop them, but Mauro wanted to address this later:

[RFC] Remove row numbers from tables in V4L2 documentation

Hello, While documenting the metadata API I got annoyed by how tables were converted from DocBook to ReST. The table format currently used by the documentation is as follows: - .. row 1 - row 1, entry 1 - row 1, entry 2 - .. row 2 - row 2, entry 1 - row 2, entry 2 The

Re: g_webcam Isoch high bandwidth transfer

Hi, Bin Liu writes: > Hi, > > I am trying to check Isoch high bandwidth transfer with g_webcam.ko in > high-speed connection. > > First I hacked webcam.c as follows to enable 640x480@30fps mode. > > diff --git a/drivers/usb/gadget/legacy/webcam.c >

Re: [RFC PATCH 6/7] atmel-isi: remove dependency of the soc-camera framework

On 08/18/2016 07:53 AM, Wu, Songjun wrote: > Hi Hans, > > Thank you for the patch. > > On 8/17/2016 14:29, Hans Verkuil wrote: >> From: Hans Verkuil >> >> This patch converts the atmel-isi driver from a soc-camera driver to a driver >> that is stand-alone. >> >>

Re: [PATCH] pxa_camera: merge soc_mediabus.c into pxa_camera.c

On 09/21/2016 08:37 AM, Robert Jarzmik wrote: > Hans Verkuil writes: > >> Linking soc_mediabus into this driver causes multiple definition linker >> warnings >> if soc_camera is also enabled: >> >> >>

Re: [PATCH] pxa_camera: merge soc_mediabus.c into pxa_camera.c

Hans Verkuil writes: > Linking soc_mediabus into this driver causes multiple definition linker > warnings > if soc_camera is also enabled: > > > drivers/media/platform/soc_camera/built-in.o:(___ksymtab+soc_mbus_image_size+0x0): > multiple definition of

Re: [PATCH -next] [media] pxa_camera: remove duplicated include from pxa_camera.c

Wei Yongjun writes: > From: Wei Yongjun > > Remove duplicated include. > > Signed-off-by: Wei Yongjun Acked-by: Robert Jarzmik Cheers. -- Robert -- To unsubscribe from this list: send the line

Re: [PATCH -next] [media] pxa_camera: fix error return code in pxa_camera_probe()

Wei Yongjun writes: > From: Wei Yongjun > > Fix to return error code -ENODEV from dma_request_slave_channel_compat() > error handling case instead of 0, as done elsewhere in this function. > > Also fix to release resources in v4l2_clk_register() error

Re: [PATCH] [media] platform: pxa_camera: add VIDEO_V4L2 dependency

Arnd Bergmann writes: > Moving the pxa_camera driver from soc_camera lots the implied > VIDEO_V4L2 Kconfig dependency, and building the driver without > V4L2 results in a kernel that cannot link: > > drivers/media/platform/pxa_camera.o: In function `pxa_camera_remove': >