Re: [PATCH v2 0/15] [dt-bindings] [media] Add document file and driver for Sony CXD2880 DVB-T2/T tuner + demodulator

On 2017/04/14 10:50, Takiguchi, Yasunari wrote: > From: Yasunari Takiguchi > > Hi, > > This is the patch series (version 2) of Sony CXD2880 DVB-T2/T tuner + > demodulator driver. > The driver supports DVB-API and interfaces through SPI. > > We have tested the

Re: [PATCH v2 01/15] [dt-bindings] [media] Add document file for CXD2880 SPI I/F

> From: Yasunari Takiguchi > > This is the document file for Sony CXD2880 DVB-T2/T tuner + demodulator. > It contains the description of the SPI adapter binding. > > Signed-off-by: Yasunari Takiguchi > Signed-off-by: Masayuki Yamamoto

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: Mon Apr 17 05:00:17 CEST 2017 media-tree git hash:f2fe89061d79706eca5c47e4efdc09bbc171e74a media_build

Re: HauppaugeTV-quadHD DVB-T mpeg risc op code errors

Just a follow up on this. I had a bit more time to dig deeper into this today. Enabling debug output for the cx23885 driver *fixes* the issue. I added this to my kernel command line: cx23885.debug=8 With debug mode enabled, `w_scan` can find channels and TVheadend can successfully tune to and

Re: em28xx i2c writing error

Em Sat, 15 Apr 2017 20:28:20 +0200 Anders Eriksson escreveu: > Hi Mauro, > > I've two devices using this driver, and whenever I have them both in > use I eventually (between 10K and 100K secs uptime) i2c write errors > such as in the log below. If only have one of the

Re: Camera resolution question

Em Fri, 14 Apr 2017 21:31:48 +0530 Ryan escreveu: > Hi, > > I have a display of 720P and a 8MP camera. > > Do i need to capture 8MP image or an image 720P from the camera as the > i need to display it on the LCD. > > Where does the scaling take place? Should i

Re: [PATCH] arm: dma: fix sharing of coherent DMA memory without struct page

On 04/14/2017 03:46 AM, Russell King - ARM Linux wrote: > On Fri, Apr 14, 2017 at 09:56:07AM +0200, Marek Szyprowski wrote: This would be however quite large task, especially taking into account all current users of DMA-buf framework... >>> Yeah it will be a large task. >> >> Maybe once

Re: em28xx i2c writing error

Am 15.04.2017 um 20:28 schrieb Anders Eriksson: > Hi Mauro, > > I've two devices using this driver, and whenever I have them both in > use I eventually (between 10K and 100K secs uptime) i2c write errors > such as in the log below. If only have one of the devices in use, the > machine is stable.

Re: Looking for device driver advice

Hi, On 2017-04-16 13:51:21 +0300, Sakari Ailus wrote: > Hi Hans and Patrick, > > On Wed, Apr 12, 2017 at 01:37:33PM +0200, Hans Verkuil wrote: > > Hi Patrick, > > > > On 04/10/2017 10:13 PM, Patrick Doyle wrote: > > > I am looking for advice regarding the construction of a device driver > > >

[PATCH v2] em28xx: simplify ID-reading from Micron sensors

Use i2c_smbus_read_word_data() instead of i2c_master_send() and i2c_master_recv() for reading the ID of Micorn sensors. i2c_smbus_read_word_data() assumes that byes are in little-endian, so, it uses: data->word = msgbuf1[0] | (msgbuf1[1] << 8); However, Micron datasheet describes the ID

[PATCH 5/7] ov2640: fix duplicate width+height returning from ov2640_select_win()

ov2640_select_win() returns height and width values as part of struct ov2640_win_size, so there is no point in modifying the passed height and width parameters, too. Signed-off-by: Frank Schäfer --- drivers/media/i2c/ov2640.c | 18 +++--- 1 file

[PATCH 7/7] ov2640: add support for MEDIA_BUS_FMT_YVYU8_2X8 and MEDIA_BUS_FMT_VYUY8_2X8

Signed-off-by: Frank Schäfer --- drivers/media/i2c/ov2640.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/media/i2c/ov2640.c b/drivers/media/i2c/ov2640.c index 6aba0ffe486d..618230e782e7 100644 --- a/drivers/media/i2c/ov2640.c +++

[PATCH 6/7] ov2640: fix vflip control

Enabling vflip currently causes wrong colors. It seems that (at least with the current sensor setup) REG04_VFLIP_IMG only changes the vertical readout direction. Because pixels are arranged RGRG... in odd lines and GBGB... in even lines, either a one line shift or even/odd line swap is required,

[PATCH 4/7] ov2640: add missing write to size change preamble

HSIZE and VSIZE bits 0 to 2 and HSIZE bit 11 are encoded in DSP register SIZEL. Signed-off-by: Frank Schäfer --- drivers/media/i2c/ov2640.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/media/i2c/ov2640.c b/drivers/media/i2c/ov2640.c index

[PATCH 3/7] ov2640: add information about DSP register 0xc7

According to ov2640 software application notes, there are two Automatic White Balance (AWB) modes, which are selected by DSP register 0xc7: 1) Simple AWB: assumes the average color is gray + independent from lens - doesn't work well if captured area contains unbalanced colors (e.g.

[PATCH 2/7] ov2640: improve banding filter register definitions/documentation

- add missing initialisation of sensor register COM25 (2 MSBs of banding filter AEC values) - add macros for setting the banding filter AEC values - add definitions for sensor register 0x5a, which is documented in Omnivisions software application notes Signed-off-by: Frank Schäfer

[PATCH 0/7] ov2640 fixes and improvements

First 5 patches are minor fixes/cleanups/improvements which I came across while testing Hans Verkuils patches and trying to figure out what's going wrong with vflip control. Patch 6 finally fixes the vflip bug. Patch 7 adds support for 2 new pixel formats. Frank Schäfer (7): ov2640: fix init

[PATCH 1/7] ov2640: fix init sequence alignment

While we are at it, remove a misleading comment (copy/paste mistake) Signed-off-by: Frank Schäfer --- drivers/media/i2c/ov2640.c | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/media/i2c/ov2640.c

Re: uvcvideo logging kernel warnings on device disconnect

Hi Greg, On Wednesday 21 Dec 2016 10:59:54 Greg KH wrote: > On Tue, Dec 20, 2016 at 11:19:23AM +, Dave Stevenson wrote: > > On 09/12/16 09:43, Greg KH wrote: > >> On Fri, Dec 09, 2016 at 11:14:41AM +0200, Laurent Pinchart wrote: > >>> On Friday 09 Dec 2016 10:11:13 Greg KH wrote: > On

Re: Looking for device driver advice

Hi Hans and Patrick, On Wed, Apr 12, 2017 at 01:37:33PM +0200, Hans Verkuil wrote: > Hi Patrick, > > On 04/10/2017 10:13 PM, Patrick Doyle wrote: > > I am looking for advice regarding the construction of a device driver > > for a MIPI CSI2 imager (a Sony IMX241) that is connected to a > >

Re: [PATCH v3 1/2] v4l: Add camera voice coil lens control class, current control

Hi Mauro, On Fri, Apr 14, 2017 at 11:23:32PM -0300, Mauro Carvalho Chehab wrote: > Hi Sakari, > > Em Tue, 14 Feb 2017 14:20:22 +0200 > Sakari Ailus escreveu: > > > Add a V4L2 control class for voice coil lens driver devices. These are > > simple devices that are

[PATCH RESEND2] [media] usbtv: add a new usbid

A new usbid of UTV007 is found in a newly bought device. The usbid is 1f71:3301. The ID on the chip is: UTV007 A89029.1 1520L18K1 Both video and audio is tested with the modified usbtv driver. Signed-off-by: Icenowy Zheng Acked-by: Lubomir Rintel --- Added