drivers/media/dvb-frontends/cxd2841er.c:2393:1: warning: the frame size of 2992 bytes is larger than 2048 bytes

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 72714841b705a5b9bccf37ee85a62352bee3a3ef commit: a6dc60ff1209df29ee4668024e93d31f31421932 [media] cxd2841er: Sony CXD2841ER DVB-S/S2/T/T2/C demodulator driver date: 5 weeks ago config:

Re: [PATCH] [media] omap3isp: Fix module autoloading

On Thursday 17 September 2015 01:31:38 Javier Martinez Canillas wrote: > Platform drivers needs to export the OF id table and this be built > into the module or udev will not have the necessary information to > autoload the driver module when the device is registered via OF. > > Signed-off-by:

[PATCH 1/3] media: dvb-core: fix kernel-doc warnings in dvbdev.h

Fix the following 'make htmldocs' warnings: .//drivers/media/dvb-core/dvbdev.h:199: warning: Excess function parameter 'device' description in 'dvb_register_device' .//drivers/media/dvb-core/dvbdev.h:199: warning: Excess function parameter 'adapter_nums' description in 'dvb_register_device'

[PATCH] v4l2-compat-ioctl32: add missing SDR support

Add the missing support for v4l2_sdr_format (V4L2_BUF_TYPE_SDR_CAPTURE). Signed-off-by: Hans Verkuil diff --git a/drivers/media/v4l2-core/v4l2-compat-ioctl32.c b/drivers/media/v4l2-core/v4l2-compat-ioctl32.c index af63543..0f1d632 100644 ---

[PATCH] [media] c8sectpfe: fix return of garbage

The variable err was never initialized, that means we had been checking a garbage value in the for loop. Moreover if the segment is not outside the firmware file then also we have been returning the garbage. Initialize it to 0 so that on success we return the value and no need to check in the for

Re: [RFC PATCH] v4l2-ctrls: fix NEXT_COMPOUND support

Hello Hans I tried this patch on my platform and v4l2compliance now works ok. I would suggest to add this definition to the userland header for clarity #define V4L2_CTRL_FLAG_NEXT_COMPOUND_OR_ARRAY V4L2_CTRL_FLAG_NEXT_COMPOUND Thanks! On Wed, Sep 16, 2015 at 2:13 PM, Hans Verkuil

Re: [PATCH 04/13] v4l2: add support for SDR transmitter

Hi Antti, On 09/01/15 23:59, Antti Palosaari wrote: > New IOCTL ops: > vidioc_enum_fmt_sdr_out > vidioc_g_fmt_sdr_out > vidioc_s_fmt_sdr_out > vidioc_try_fmt_sdr_out > > New vb2 buffertype: > V4L2_BUF_TYPE_SDR_OUTPUT I just realized that you need to add support for this in v4l2-compat-ioctl32.c

Re: [PATCH v2 06/10] usb/uvc: Support for V4L2_CTRL_WHICH_DEF_VAL

On 09/04/15 12:56, Hans Verkuil wrote: > Laurent, can you review this? Ping! If I have an Ack on Monday at the latest, then I can make a pull request for this series before I leave for 2 1/2 weeks. Regards, Hans > > Regards, > > Hans > > On 08/21/2015 03:19 PM, Ricardo Ribalda

[PATCH v2 7/9] [media] v4l2: introduce v4l2_timeval

The v4l2 API uses a 'struct timeval' to communicate time stamps to user space. This is broken on 32-bit architectures as soon as we have a C library that defines time_t as 64 bit, which then changes the structure layout of struct v4l2_buffer. Since existing user space source code relies on the

[PATCH v2 2/9] [media] dvb: remove unused systime() function

The systime function uses struct timespec, which we want to stop using in the kernel because it overflows in 2038. Fortunately, this use in dibx000_common is in a function that is never called, so we can just remove it. Signed-off-by: Arnd Bergmann ---

[PATCH v2 6/9] [media] use v4l2_get_timestamp where possible

This is a preparation for a change to the type of v4l2 timestamps. v4l2_get_timestamp() is a helper function that reads the monotonic time and stores it into a 'struct timeval'. Multiple drivers implement the same thing themselves for historic reasons. Changing them all to use

[PATCH v2 9/9] [media] omap3isp: support 64-bit version of omap3isp_stat_data

C libraries with 64-bit time_t use an incompatible format for struct omap3isp_stat_data. This changes the kernel code to support either version, by moving over the normal handling to the 64-bit variant, and adding compatiblity code to handle the old binary format with the existing ioctl command

[PATCH v2 4/9] [media] exynos4-is: use monotonic timestamps as advertized

The exynos4 fimc capture driver claims to use monotonic timestamps but calls ktime_get_real_ts(). This is both an incorrect API use, and a bad idea because of the y2038 problem and the fact that the wall clock time is not reliable for timestamps across suspend or settimeofday(). This changes the

[PATCH v2 0/9] [media] y2038 conversion for subsystem

This is my second attempt to convert subsystem-wide code in v4l for y2038 changes, removing uses of time_t in common files and adding support for user space that defines time_t as 64 bit. Based on the initial feedback from Hans Verkuil, I've changed the ioctl handling to remain 100% compatible

[PATCH v2 3/9] [media] dvb: don't use 'time_t' in event ioctl

'struct video_event' is used for the VIDEO_GET_EVENT ioctl, implemented by drivers/media/pci/ivtv/ivtv-ioctl.c and drivers/media/pci/ttpci/av7110_av.c. The structure contains a 'time_t', which will be redefined in the future to be 64-bit wide, causing an incompatible ABI change for this ioctl. As

[PATCH v2 8/9] [media] handle 64-bit time_t in v4l2_buffer

This is the final change to enable user space with 64-bit time_t in the core v4l2 code. Four ioctls are affected here: VIDIOC_QUERYBUF, VIDIOC_QBUF, VIDIOC_DQBUF, and VIDIOC_PREPARE_BUF. All of them pass a struct v4l2_buffer, which can either contain a 32-bit time_t or a 64-bit time on 32-bit

[PATCH v2 5/9] [media] make VIDIOC_DQEVENT work with 64-bit time_t

The v4l2 event queue uses a 'struct timespec' to pass monotonic timestamps. This is not a problem by itself, but it breaks when user space redefines timespec to use 'long long' on 32-bit systems. This is the second approach on fixing the problem, by changing the kernel to internally use 64-bit

[PATCH v2 1/9] [media] dvb: use ktime_t for internal timeout

The dvb demuxer code uses a 'struct timespec' to pass a timeout as absolute time. This will cause problems on 32-bit architectures in 2038 when time_t overflows, and it is racy with a concurrent settimeofday() call. This patch changes the code to use ktime_get() instead, using the monotonic time

Re: Renesas Lager: Device Tree entries for VIN HDMI input, version 2

Hi William, On Thu, Aug 13, 2015 at 12:36:48PM +0100, William Towle wrote: > Version 2 ... removes some redundant configuration from device nodes, > and provides some supplementary logic for automatic initialisation of > state->pdata.default_input based on the hardware present. > >

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 Sep 18 04:00:20 CEST 2015 git branch: test git hash: 9ddf9071ea17b83954358b2dac42b34e5857a9af gcc