[PATCH] media: rc-main: clean-up two warnings

While correct, the code is too complex for smatch to undersdand that protocol will always be initialized: drivers/media/rc/rc-main.c:1531 store_wakeup_protocols() error: uninitialized symbol 'protocol'. drivers/media/rc/rc-main.c:1541 store_wakeup_protocols() error: uninitialized

[PATCH 3/3] media: dt-bindings: media: i2c: Add bindings for ov02a10

From: Dongchun Zhu Add device tree binding documentation for the OV02A10 CMOS image sensor. Signed-off-by: Dongchun Zhu --- .../devicetree/bindings/media/i2c/ov02a10.txt | 43 ++ 1 file changed, 43 insertions(+) create mode 100644 Documentation/devicetree/bindings/med

[PATCH 2/3] media: i2c: ov02a10: Add CONFIG_VIDEO_OV02A10

From: Dongchun Zhu Add CONFIG_VIDEO_OV02A10 to the Kconfig entry. Signed-off-by: Dongchun Zhu --- drivers/media/i2c/Kconfig | 12 1 file changed, 12 insertions(+) diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig index 7793358..480aa42 100644 --- a/drivers/media/

[PATCH 0/3] media: suppport ov02a10 sensor driver

From: Dongchun Zhu Hello, This is the OV02A10 sensor driver, which would be used in camera features on CrOS application. The driver is implemented wth V4L2 framework. 1. Async registered as a V4L2 I2C sub-device. 2. A media entity that can provide several source pads and sink pads to link wit

[PATCH 1/3] media: i2c: ov02a10: Add ov02a10 camera sensor driver

From: Dongchun Zhu Add a V4L2 sub-device driver for the OmniVision image sensor. This is a camera sensor using the I2C bus for control and the CSI-2 bus for data. Signed-off-by: Dongchun Zhu --- drivers/media/i2c/Makefile |1 + drivers/media/i2c/ov02a10.c | 1067 ++

Re: [PATCH] media: rc-main: clean-up two warnings

On Thu, May 23, 2019 at 05:27:30AM -0400, Mauro Carvalho Chehab wrote: > While correct, the code is too complex for smatch to undersdand > that protocol will always be initialized: > > drivers/media/rc/rc-main.c:1531 store_wakeup_protocols() error: > uninitialized symbol 'protocol'. >

FW: AW: Kontakt.

Sehr geehrte Damen und Herren, nach unserem Besuch Ihrer Homepage möchten wir Ihnen ein Angebot von Produkten vorstellen, das Ihnen ermöglichen wird, den Verkauf Ihrer Produkte sowie Dienstleistungen deutlich zu erhöhen. Die Datenbanken der Firmen sind in für Sie interessante und relevante Zie

Re: [GIT PULL v2] SAA716x DVB driver

@Mauro: What's keeping you from pulling this driver? As far as I can see, Soeren Moch did in fact resolve all of your prior objections regarding this driver, including the api changes. I get that your opinion regarding these api changes differs from Soeren Moch's opinion, but there is no evid

[PATCH 3/3] media: em28xx: use usb_to_input_id() rather than handrolling it

This also populates the version member correctly. Signed-off-by: Sean Young --- drivers/media/usb/em28xx/em28xx-input.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/media/usb/em28xx/em28xx-input.c b/drivers/media/usb/em28xx/em28xx-input.c index 6e43da5

[PATCH 2/3] media: em28xx: use common code for decoding nec scancodes

Tested on WinTV-HVR-930C. Signed-off-by: Sean Young --- drivers/media/usb/em28xx/em28xx-input.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git a/drivers/media/usb/em28xx/em28xx-input.c b/drivers/media/usb/em28xx/em28xx-input.c index e757a71d247f..6e43da5f6c

[PATCH 1/3] media: em28xx: give RC device proper name

Give the RC device the name of the board rather than "1-2:1.0 IR". Signed-off-by: Sean Young --- drivers/media/usb/em28xx/em28xx-input.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/media/usb/em28xx/em28xx-input.c b/drivers/media/usb/em28xx/em28xx-input.c in

Re: [RFC PATCH V1 6/6] platform: mtk-isp: Add Mediatek DIP driver

Dear Tomasz, Thank you for your comments. On Wed, 2019-05-22 at 19:25 +0900, Tomasz Figa wrote: > Hi Frederic, > > On Wed, May 22, 2019 at 03:14:15AM +0800, Frederic Chen wrote: > > Dear Tomasz, > > > > I appreciate your comment. It is very helpful for us. > > > > You're welcome. Thanks for

Re: [RFC PATCH V1 6/6] platform: mtk-isp: Add Mediatek DIP driver

Hi Shilk, I appreciate your comments. On Wed, 2019-05-22 at 17:51 +0800, Shik Chen wrote: > Hi Frederic, > > Most reviews are already covered by Tomasz, here are some small missing > pieces. > Please see my comments inline. > > On Wed, Apr 17, 2019 at 06:45:11PM +0800, Frederic Chen wrote: >

Linux 5.2 - vimc streaming fails with format error

Hi Hans and Helen, vimc streaming fails on Linux 5.2-rc1 vimc: format doesn't match in link Scaler->RGB/YUV Capture You can reproduce this easily with v4l2-ctl Streaming works fine on Linux 5.1 I narrowed it to the following commit. commit b6c61a6c37317efd7327199bfe24770af3d7e799 Author: Hele

Re: Proposed updates and guidelines for MPEG-2, H.264 and H.265 stateless support

On 2019-05-15 12:09, Paul Kocialkowski wrote: > Hi, > > With the Rockchip stateless VPU driver in the works, we now have a > better idea of what the situation is like on platforms other than > Allwinner. This email shares my conclusions about the situation and how > we should update the MPEG-2, H.2

[linuxtv-media:master 51/52] drivers/media/media-device.c:521:9: sparse: sparse: incorrect type in argument 1 (different address spaces)

tree: git://linuxtv.org/media_tree.git master head: 3d3515312f97582136644a7327ed262c7bb7ea31 commit: f49308878d7202e07d8761238e01bd0e5fce2750 [51/52] media: media_device_enum_links32: clean a reserved field reproduce: # apt-get install sparse # sparse version: v0.6.1-rc1-7-g2b9

media/master v4l2-compliance on vivid: 236 tests, 0 regressions (v5.2-rc1-52-g3d3515312f97)

media/master v4l2-compliance on vivid: 236 tests, 0 regressions (v5.2-rc1-52-g3d3515312f97) Test results summary V4L2 Compliance on the vivid driver. This test ran "v4l2-compliance -s" from v4l-utils: https://www.linuxtv.org/wiki/index.php/V4l2-utils See each detailed

Linux 5.2-rc1 rmmod on vimc_capture panics

Hi Hans, vimc isn't happy on Linux 5,2-rc1 When I do rmmod vimc_capture it panics. Just fine on Linux 5.1 commit 3650a23eda89 might be the problem. [ 302.974433] general protection fault: [#1] SMP PTI [ 302.974441] CPU: 3 PID: 1469 Comm: rmmod Not tainted 5.2.0-rc1+ #6 [ 302.97] Ha

Geniatech A681 Support

Hello! I recently purchased a Geniatech A681, which is an ATSC USB device and found that it didn't seem to work with Linux. I found this old thread about the same device but unfortunately the person emailing didn't respond to requests for information. https://www.spinics.net/lists/linux-media/

cron job: media_tree daily build: OK

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: Fri May 24 05:00:10 CEST 2019 media-tree git hash:3d3515312f97582136644a7327ed262c7bb7ea31 media_build gi

rc rc0: two consecutive events of type space & strange ir-keytable behaviour

Good day, Information on the system: - Raspberry 3b+ - Updated yesterday to 4.19.42-v7+ Before the update the remote control was working well with: - gpio-rc-recv    rc-rc6-mce    kodi (into the file rc_maps.cfg) - And the following data into /etc/rc_keymaps/kodi: # table kodi, type: NEC 0

Re: rc rc0: two consecutive events of type space & strange ir-keytable behaviour

Probably related to this issue; ir-keytable -a /etc/rc_maps.conf -v gives: /sys/class/rc/rc0/protocols protocol rc-5 (disabled) /sys/class/rc/rc0/protocols protocol nec (disabled) /sys/class/rc/rc0/protocols protocol rc-6 (enabled) /sys/class/rc/rc0/protocols protocol jvc (disabled) /sys/class/rc