[PATCH v4] media: v4l: ctrls: Add debug messages

Currently, the v4l2 control code is a bit silent on errors. Add debug messages on (hopefully) most of the error paths. Signed-off-by: Ezequiel Garcia --- Changes from v3: * Fix checkpatch.pl warnings about long lines. Changes from v2: * Check and noisy-warn if vdev is NULL. Changes from v1: * D

Re: [PATCH v3] media: v4l: ctrls: Add debug messages

On Thu, 2019-06-27 at 09:38 +0200, Hans Verkuil wrote: > Hi Ezequiel, > > 'checkpatch.pl --strict' finds way too many issues. > > I'm pretty certain you didn't run it. > Shame on me, I did run it and skipped fixing the long lines :-( > Please fix the issues and post a v4. > > A lot (but not a

Re: MyGica T230 dvb-t2 data corruption since commit 5fa8815

dvbsky: add MyGica T230. Moved from cxusb driver as that driver can't handle FX2 FIFO issue. Signed-off-by: Jan Pieter van Woerkom --- diff -ru a/drivers/media/usb/dvb-usb-v2/dvbsky.c b/drivers/media/usb/dvb-usb-v2/dvbsky.c --- a/drivers/media/usb/dvb-usb-v2/dvbsky.c 2019-07-08 00:41:56.

Re: Issues with ov5640 camera on i.MX6Q

Hi Loic, Thanks for your reply. On 7/19/19 8:56 AM, Loic Poulain wrote: Hi Laura, On Thu, 18 Jul 2019 at 15:03, Laura Nao > wrote: Hello Loic, I'm having some issues with RAW8 mode on the OV5640 camera and I'd like to kindly ask for your advice, a

scancodes identified as invalid

I have POWER_KEY scancodes, that work as RAW data with ir-ctl -s [file], but are not working with ir-ctl -S:     0x20df10ef (POWER_KEY for my LG tv)     0x02FD48B7 (POWER_KEY for my Toshiba tv) rc6_mce:0x800f0410 works, as does nec32:0x800f0410 (though not nec:0x800f0410), so it doesn't seem t

Re: [PATCH 3/4] rcar-vin: Add support for V4L2_FIELD_ALTERNATE

Hi Niklas, On 05/07/2019 05:55, Niklas Söderlund wrote: > The hardware is capable to passing V4L2_FIELD_ALTERNATE to user-space. > Allow users to request this field format but still default to using the > hardware interlacer if alternating is not explicitly requested. I'm afraid I have found this

Re: [RFC PATCH 0/5] Add enum_fmt flag for coded formats with dynamic resolution switching

On 7/19/19 4:45 AM, Tomasz Figa wrote: > On Mon, Jul 15, 2019 at 9:37 PM Hans Verkuil wrote: >> >> On 6/11/19 10:13 AM, Hans Verkuil wrote: >>> On 6/9/19 4:38 PM, Maxime Jourdan wrote: Hello, This RFC proposes a new format flag - V4L2_FMT_FLAG_DYN_RESOLUTION - used to tag coded

Re: [PATCH] media/i2c: don't return ENOTTY if SUBDEV_API is not set

Hi Hans, On Wed 17 Jul 2019 at 10:24, Hans Verkuil wrote: > If CONFIG_VIDEO_V4L2_SUBDEV_API is not set, then it is still possible > to call set_fmt for V4L2_SUBDEV_FORMAT_TRY, the result is just not > stored. So return 0 instead of -ENOTTY. > > Calling get_fmt with V4L2_SUBDEV_FORMAT_TRY should ret

Re: [PATCH] media/i2c: don't return ENOTTY if SUBDEV_API is not set

Hi Hans, Thank you for the patch. On Wed, Jul 17, 2019 at 10:24 AM Hans Verkuil wrote: > > If CONFIG_VIDEO_V4L2_SUBDEV_API is not set, then it is still possible > to call set_fmt for V4L2_SUBDEV_FORMAT_TRY, the result is just not > stored. So return 0 instead of -ENOTTY. > > Calling get_fmt with

Re: [PATCH] media:dvb-frontends:Return if Max devices are added in dvb_pll_attach().

On 19/07/19 7:11 AM, Akihiro TSUKADA wrote: >> Will it be better, if dvb_pll_devcount is decremented in dvb_pll_release(),  >> instead of removing module params? > But you cannot know deterministically which device corrensponds to > what "id" (when you have multiple dvb_pll devices), > since "id