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: Sat Mar 24 05:00:13 CET 2018
media-tree git hash:6ccd228e0cfce2a4f44558422d25c60fcb1a6710
media_build git
On Fri, 2018-03-23 at 11:44 +0800, Ryder Lee wrote:
> The error return value should be fixed as it may return EPROBE_DEFER.
>
> Cc: Rick Chang
> Cc: Bin Liu
> Signed-off-by: Ryder Lee
> ---
> drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletio
Hi Hans,
Could you take this patch it not too late.
On 20.03.2018 15:42, Stanimir Varbanov wrote:
Hi Alex,
Thanks!
On 03/19/2018 11:32 AM, Alexandre Courbot wrote:
find_format_by_index() stops enumerating formats as soon as the index
matches, and returns NULL if venus_helper_check_codec() fi
Hi Hans,
Thanks for writing this. I generally agree with the RFC to the level of
detail available here; a few comments below.
On Fri, Mar 23, 2018 at 09:46:00AM +0100, Hans Verkuil wrote:
> RFC Request API, version 2
> --
>
> This document proposes the public API for hand
Hi Mauro,
On Fri, Mar 23, 2018 at 07:56:54AM -0400, Mauro Carvalho Chehab wrote:
> While the code there is right, it produces three false positives:
> drivers/media/v4l2-core/v4l2-ioctl.c:2868 video_usercopy() error:
> copy_from_user() 'parg' too small (128 vs 16383)
> drivers/media/v
On Fri, Mar 23, 2018 at 07:56:52AM -0400, Mauro Carvalho Chehab wrote:
> There are some troubles on this driver with respect to the usage
> of __be16 and __b32 macros:
>
> drivers/media/i2c/ov5670.c:1857:27: warning: incorrect type in
> initializer (different base types)
> drivers/med
Associate a buffer to a request when it is queued and disassociate when it
is done.
Signed-off-by: Sakari Ailus
---
drivers/media/common/videobuf2/videobuf2-core.c | 43 -
drivers/media/common/videobuf2/videobuf2-v4l2.c | 40 ++-
include/media/videobuf
Initialise the V4L2 mem2mem framework before creating the video device.
Referencing ctx->m2m_dev isn't allowed before that as it is NULL.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/vim2m.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --g
From: Laurent Pinchart
The request API allows bundling media device parameters with request
objects and queueing them to be executed atomically.
Signed-off-by: Laurent Pinchart
Signed-off-by: Sakari Ailus
Signed-off-by: Alexandre Courbot
---
drivers/media/Makefile| 3 +-
drivers/me
Signed-off-by: Sakari Ailus
---
drivers/media/platform/vim2m.c | 49 --
1 file changed, 43 insertions(+), 6 deletions(-)
diff --git a/drivers/media/platform/vim2m.c b/drivers/media/platform/vim2m.c
index 9b6b456..a8fe3ea 100644
--- a/drivers/media/platform
From: Hans Verkuil
When queuing buffers allow for passing the request that should
be associated with this buffer.
Signed-off-by: Hans Verkuil
[acour...@chromium.org: make request ID 32-bit]
Signed-off-by: Alexandre Courbot
[Sakari Ailus: requests fds are int; use assign_in_user in get_v4l2_buf
Hi folks,
This preliminary RFC patchset prepares for the request API. What's new
here is support for binding arbitrary configuration or resources to
requests.
There are a few new concepts here:
Class --- a type of configuration or resource a driver (or e.g. the V4L2
framework) can attach to a re
From: Alexandre Courbot
Allow to specify a request to be used with the S_EXT_CTRLS and
G_EXT_CTRLS operations.
Signed-off-by: Alexandre Courbot
[Sakari Ailus: reserved no longer an array, add compat32 code]
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 9
The atomisp driver used to use the reserved2 field in struct v4l2_buffer
for picking a particular ISP configuration for the buffer. As reserved2
field will have new use soon, remove this hack.
Signed-off-by: Sakari Ailus
---
.../staging/media/atomisp/pci/atomisp2/atomisp_ioctl.c | 17 +++---
Maintain a list of supported IOCTL argument sizes and allow only those in
the list.
As an additional bonus, IOCTL handlers will be able to check whether the
caller actually set (using the argument size) the field vs. assigning it
to zero. Separate macro can be provided for that.
This will be easi
Enable supporting requests on V4L2 buffer queues on M2M devices. This
requires Media controller.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-mem2mem.c | 109 +
include/media/v4l2-mem2mem.h | 28 +
2 files changed, 137 insertions
The v4l2_m2m_try_schedule function acquires and releases multiple
spinlocks; simplify unlocking the job lock by adding a label to unlock the
job lock and exit the function.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-mem2mem.c | 22 --
1 file changed, 12 inse
Hi Simon,
On 23/03/18 08:51, Simon Horman wrote:
> On Thu, Mar 22, 2018 at 09:30:40PM +, Kieran Bingham wrote:
>> The r8a7792 Wheat board has two ADV7513 devices sharing a single I2C
>> bus, however in low power mode the ADV7513 will reset it's slave maps to
>> use the hardware defined default
Messages expected during device probe were being marked as errors.
Signed-off-by: Chris Mayo
---
drivers/media/usb/em28xx/em28xx-cards.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/media/usb/em28xx/em28xx-cards.c
b/drivers/media/usb/em28xx/em28xx-car
Hi Mauro,
Just one patch here, to add the size of the array of the modes for
v4l2_find_nearest_size.
Please pull.
The following changes since commit 238f694e1b7f8297f1256c57e41f69c39576c9b4:
media: v4l2-common: fix a compilation breakage (2018-03-21 16:07:01 -0400)
are available in the git
On 03/23/2018 04:44 AM, Ryder Lee wrote:
> The error return value should be fixed as it may return EPROBE_DEFER.
>
> Cc: Rick Chang
> Cc: Bin Liu
> Signed-off-by: Ryder Lee
Reviewed-by: Matthias Brugger
> ---
> drivers/media/platform/mtk-jpeg/mtk_jpeg_core.c | 4 ++--
> 1 file changed, 2
Em Fri, 23 Mar 2018 17:31:53 +0200
Sakari Ailus escreveu:
> On Fri, Mar 23, 2018 at 11:08:55AM -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 23 Mar 2018 11:07:42 -0300
> > Mauro Carvalho Chehab escreveu:
> >
> > > Em Fri, 23 Mar 2018 15:48:41 +0200
> > > Sakari Ailus escreveu:
> > >
> >
An older version of the driver patches were merged accidentally which
resulted in missing the array_size parameter that tells the length of the
array that contains the different supported sizes.
Bring it back to v4l2_find_nearest size and make the corresponding change
for the drivers using it as w
On Fri, Mar 23, 2018 at 11:08:55AM -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 23 Mar 2018 11:07:42 -0300
> Mauro Carvalho Chehab escreveu:
>
> > Em Fri, 23 Mar 2018 15:48:41 +0200
> > Sakari Ailus escreveu:
> >
> > > An older version of the driver patches were merged accidentally which
> > >
Hi Hans,
On Fri, Mar 23, 2018 at 5:46 PM, Hans Verkuil wrote:
> RFC Request API, version 2
> --
>
> This document proposes the public API for handling requests.
>
> There has been some confusion about how to do this, so this summarizes the
> current approach based on conve
On Fri, Mar 23, 2018 at 6:33 PM, Sakari Ailus wrote:
>> >>> An alternative, maybe a bit crazy, idea would be to allow adding
>> >>> MEDIA_REQUEST_IOC_QUEUE ioctl to the request itself. This would be
>> >>> similar to the idea of indirect command buffers in the graphics (GPU)
>> >>> land. It could
On Fri, Mar 23, 2018 at 11:08:11PM +0900, Tomasz Figa wrote:
> On Fri, Mar 23, 2018 at 10:50 PM, Sakari Ailus
> wrote:
> > Hi Tomasz,
> >
> > On Fri, Mar 23, 2018 at 08:43:50PM +0900, Tomasz Figa wrote:
> >> Hi Andy,
> >>
> >> Some issues found when reviewing cherry pick of this patch to Chrome
>
Em Fri, 23 Mar 2018 11:07:42 -0300
Mauro Carvalho Chehab escreveu:
> Em Fri, 23 Mar 2018 15:48:41 +0200
> Sakari Ailus escreveu:
>
> > An older version of the driver patches were merged accidentally which
> > resulted in missing the array_size parameter that tells the length of the
> > array th
On Fri, Mar 23, 2018 at 10:50 PM, Sakari Ailus
wrote:
> Hi Tomasz,
>
> On Fri, Mar 23, 2018 at 08:43:50PM +0900, Tomasz Figa wrote:
>> Hi Andy,
>>
>> Some issues found when reviewing cherry pick of this patch to Chrome
>> OS kernel. Please see inline.
>>
>> On Sat, Mar 17, 2018 at 1:38 AM, Andy Ye
Em Fri, 23 Mar 2018 15:48:41 +0200
Sakari Ailus escreveu:
> An older version of the driver patches were merged accidentally which
> resulted in missing the array_size parameter that tells the length of the
> array that contains the different supported sizes.
>
> Bring it back to v4l2_find_neares
Hi Tomasz,
On Fri, Mar 23, 2018 at 08:43:50PM +0900, Tomasz Figa wrote:
> Hi Andy,
>
> Some issues found when reviewing cherry pick of this patch to Chrome
> OS kernel. Please see inline.
>
> On Sat, Mar 17, 2018 at 1:38 AM, Andy Yeh wrote:
>
> [snip]
>
> > + case V4L2_CID_VBLANK:
> > +
An older version of the driver patches were merged accidentally which
resulted in missing the array_size parameter that tells the length of the
array that contains the different supported sizes.
Bring it back to v4l2_find_nearest size and make the corresponding change
for the drivers using it as w
Hi Todor,
thanks for the patch.
When running checkpatch --strict I see a few warning you can easily
close (braces indentation mostly, and one additional empty line at
line 1048).
A few more nits below.
On Fri, Mar 23, 2018 at 12:14:20PM +0800, Todor Tomov wrote:
> The ov7251 sensor is a 1/7.5
Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v4.16-4
For 3 fixes:
- dvb: fix a Kconfig typo on a help text
- tegra-cec: reset rx_buf_cnt when start bit detected
- rc: lirc does not use LIRC_CAN_SEND_SCANCODE feature
T
On 03/23/18 14:03, Fabio Estevam wrote:
> Hi Mauro and Hans,
>
> On Sat, Mar 10, 2018 at 12:53 PM, Fabio Estevam wrote:
>> Hi,
>>
>> On Sat, Mar 3, 2018 at 9:56 AM, Fabio Estevam wrote:
>>> From: Fabio Estevam
>>>
>>> Since commit 52e17089d185 ("media: imx: Don't initialize vars that
>>> won't
Hi Mauro and Hans,
On Sat, Mar 10, 2018 at 12:53 PM, Fabio Estevam wrote:
> Hi,
>
> On Sat, Mar 3, 2018 at 9:56 AM, Fabio Estevam wrote:
>> From: Fabio Estevam
>>
>> Since commit 52e17089d185 ("media: imx: Don't initialize vars that
>> won't be used") imx_csi_probe() fails to probe after propag
From: Hans Verkuil
The meson-gx boards have two CEC controllers: the DesignWare controller
and a meson-specific controller. Disable the DW controller since the
CEC line is hooked up to the meson controller.
Signed-off-by: Hans Verkuil
Acked-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/m
From: Hans Verkuil
Some boards (amlogic) have two CEC controllers: the DesignWare controller
and their own CEC controller (meson ao-cec).
Since the CEC line is not hooked up to the DW controller we need a way
to disable that controller. This patch series adds the cec-disable
property for that pu
From: Hans Verkuil
Some boards have both a DesignWare and their own CEC controller.
The CEC pin is only hooked up to their own CEC controller and not
to the DW controller.
Add the cec-disable property to disable the DW CEC controller.
This particular situation happens on Amlogic boards that hav
From: Hans Verkuil
If the cec-disable property was set, then disable the DW CEC
controller. This is needed for boards that have their own
CEC controller.
Signed-off-by: Hans Verkuil
Reviewed-by: Neil Armstrong
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 3 ++-
1 file changed, 2 insertions
Smatch produces two warnings when building this file:
./arch/x86/include/asm/bitops.h:433:22: warning: asm output is not an
lvalue
./arch/x86/include/asm/bitops.h:433:22: warning: asm output is not an
lvalue
On some asm instructions.
I suspect that those asm instructions might n
Now that af9015 requires I2C_MUX, all drivers that select
it should also depend on it.
drivers/media/dvb-frontends/af9013.o: In function `af9013_remove':
>> drivers/media/dvb-frontends/af9013.c:1560: undefined reference to
>> `i2c_mux_del_adapters'
drivers/media/dvb-frontends/af9013.o: In f
On 03/23/18 12:56, Mauro Carvalho Chehab wrote:
> Fix the following warnings:
> drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:1146 gen_twopix() error:
> buffer overflow 'buf[1]' 8 <= 8
> drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:1152 gen_twopix() error:
> buffer overflow 'buf[1]'
While the logic there is correct, it tricks both humans and
machines, a the check if "i" var is not zero is actually to
validate if the "frames" var was initialized when the loop
ran for the first time.
That produces the following warning:
drivers/media/usb/uvc/uvc_v4l2.c:1192 uvc_ioctl_en
On 03/23/18 12:57, Mauro Carvalho Chehab wrote:
> If the adapter doesn't have error_inj_parse_line() ops, the
> write() logic won't return -EINVAL, but, instead, it will keep
> looping, because "count" is a non-negative number.
>
> Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Hans Verkuil
On Fri, Mar 23, 2018 at 07:56:48AM -0400, Mauro Carvalho Chehab wrote:
> The logic at find_format() is a little bit confusing even for
> humans, and it tricks static code analyzers:
>
> drivers/staging/media/imx/imx-media-utils.c:259 find_format() error:
> buffer overflow 'array' 14 <= 20
The error handling logic at tvaudio is broken on several ways,
as it doesn't really check right when an error occurs.
Change it to return the proper error code from read/write
routines and fix the errors on reads.
Shuts up the following warnings:
drivers/media/i2c/tvaudio.c:222 chip_read(
There are some troubles on this driver with respect to the usage
of __be16 and __b32 macros:
drivers/media/i2c/ov5670.c:1857:27: warning: incorrect type in
initializer (different base types)
drivers/media/i2c/ov5670.c:1857:27:expected unsigned short
[unsigned] [usertype] reg_
drivers/media/dvb-frontends/sp887x.c:179 sp887x_initial_setup() error: memcpy()
'&buf[2]' too small (30 vs 16384)
This is actually a false alarm, but reverting the check order
makes not only for humans to review the code, but also cleans
the warning.
Signed-off-by: Mauro Carvalho Chehab
---
dr
Just use %p. Fixes this warning:
drivers/media/v4l2-core/videobuf-dma-sg.c:247
videobuf_dma_init_kernel() warn: argument 2 to %08lx specifier is cast from
pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/v4l2-core/videobuf-dma-sg.c | 5 ++---
1 file changed, 2 insertions(
The current I2C error handling logic makes static analyzers
confused, and it doesn't follow the coding style we're using:
drivers/media/i2c/ir-kbd-i2c.c:180 get_key_pixelview() error:
uninitialized symbol 'b'.
drivers/media/i2c/ir-kbd-i2c.c:224 get_key_knc1() error: uninitialized
drivers/media/pci/ivtv/ivtvfb.c:349 ivtvfb_prep_frame() warn: argument 3 to
%08lx specifier is cast from pointer
drivers/media/pci/ivtv/ivtvfb.c:360 ivtvfb_prep_frame() warn: argument 3 to
%08lx specifier is cast from pointer
drivers/media/pci/ivtv/ivtvfb.c:363 ivtvfb_prep_frame() warn: argument
The logic at find_format() is a little bit confusing even for
humans, and it tricks static code analyzers:
drivers/staging/media/imx/imx-media-utils.c:259 find_format() error:
buffer overflow 'array' 14 <= 20
Rewrite the logic in a way that it makes it clearer to understand,
while preven
The logic with gets a p2m_id is more complex than needed,
causing false positives with static analyzers:
drivers/media/pci/solo6x10/solo6x10-p2m.c:81 solo_p2m_dma_desc() error:
buffer overflow 'solo_dev->p2m_dev' 4 <= s32max
Make it simpler and use unsigned int.
Signed-off-by: Mauro Car
Fix those warnings:
drivers/media/platform/davinci/vpss.c:510:25: warning: incorrect type
in argument 1 (different address spaces)
drivers/media/platform/davinci/vpss.c:510:25:expected void volatile
[noderef] *addr
drivers/media/platform/davinci/vpss.c:510:25:got
There's a false positive warning there:
drivers/media/i2c/tda9840.c:79 tda9840_status() error: uninitialized
symbol 'byte'.
Change the code to match our coding style, in order to fix it.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/i2c/tda9840.c | 6 +-
1 file changed, 5
If allocation of struct board_info fails, return NULL from
dvb_module_probe().
Fix this warning:
drivers/media/dvb-core/dvbdev.c:958 dvb_module_probe() error: potential
null dereference 'board_info'. (kzalloc returns null)
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-cor
The current I2C error handling logic makes static analyzers
confused:
drivers/media/usb/em28xx/em28xx-input.c:96 em28xx_get_key_terratec()
error: uninitialized symbol 'b'.
Change it to match the coding style we're using elsewhere.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media
While the code is correct, it produces this warning:
drivers/media/i2c/ir-kbd-i2c.c:593 zilog_ir_format() error: buffer
overflow 'code_block->codes' 61 <= 173
As static analyzers may be tricked by arithmetic expressions on
comparisions. So, change the order, in order to shut up this
false
drivers/media/pci/zoran/zoran_driver.c:242 v4l_fbuffer_alloc() warn: argument 5
to %lx specifier is cast from pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/pci/zoran/zoran_driver.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/pci/zoran/z
Fix the following warnings:
drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:1146 gen_twopix() error:
buffer overflow 'buf[1]' 8 <= 8
drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:1152 gen_twopix() error:
buffer overflow 'buf[1]' 8 <= 8
Signed-off-by: Mauro Carvalho Chehab
---
dri
The logic at vivid_radio_rx_g_tuner() is producint an overflow
warning:
drivers/media/platform/vivid/vivid-radio-rx.c:250
vivid_radio_rx_g_tuner() warn: potential negative subtraction from max '65535 -
(__builtin_choose_expr( == || == , , __builtin_choose_expr( == || == , ,
__builti
drivers/media/platform/soc_camera/soc_camera.c:790 soc_camera_mmap() warn:
argument 4 to %08lx specifier is cast from pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/platform/soc_camera/soc_camera.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media
drivers/media/pci/cx88/cx88-alsa.c:295 cx88_alsa_dma_init() warn: argument 3 to
%08lx specifier is cast from pointer
drivers/media/pci/cx88/cx88-alsa.c:669 snd_cx88_wm8775_volume_put() warn:
potential negative subtraction from max '65535 - (32768 * left) / right'
Signed-off-by: Mauro Carvalho Ch
Currently, the code produces those false-positives:
drivers/media/pci/saa7134/saa7134-input.c:203
get_key_msi_tvanywhere_plus() error: uninitialized symbol 'b'.
drivers/media/pci/saa7134/saa7134-input.c:251 get_key_kworld_pc150u()
error: uninitialized symbol 'b'.
drivers/m
Solves those warnings:
drivers/media/dvb-core/dvb_frontend.c:2297:39: warning: incorrect type
in argument 1 (different address spaces)
drivers/media/dvb-core/dvb_frontend.c:2297:39:expected void const
[noderef] *
drivers/media/dvb-core/dvb_frontend.c:2297:39:got st
Instead of casting, just use %p.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/zr364xx/zr364xx.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/usb/zr364xx/zr364xx.c
b/drivers/media/usb/zr364xx/zr364xx.c
index 8b7c19943d46..b8886102c5ed 10064
The error handling logic at get_key_pv951() is a little bit
akward, with produces this false positive warning:
drivers/media/pci/bt8xx/bttv-input.c:344 get_key_pv951() error:
uninitialized symbol 'b'.
Do a cleanup. As a side effect, it also improves its coding
style.
Signed-off-by: Maur
While the code there is right, it produces three false positives:
drivers/media/v4l2-core/v4l2-ioctl.c:2868 video_usercopy() error:
copy_from_user() 'parg' too small (128 vs 16383)
drivers/media/v4l2-core/v4l2-ioctl.c:2868 video_usercopy() error:
copy_from_user() 'parg' too small
As warned:
drivers/media/platform/rockchip/rga/rga.c:210:16: warning: symbol
'formats' was not declared. Should it be static?
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/platform/rockchip/rga/rga.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/me
Instead of using an ancillary function to avoid duplicating
a small portion of code that copies data either to kernelspace
or between userspace-kernelspace, duplicate the code,
as it prevents static analyzers to complain about it:
drivers/media/pci/solo6x10/solo6x10-g723.c:260:46: warning:
drivers/media/usb/s2255/s2255drv.c:651 s2255_fillbuff() warn: argument 3 to
%08lx specifier is cast from pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/s2255/s2255drv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/usb/s2255/s2255drv.c
Instead of casting, just use %p.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/usb/tm6000/tm6000-video.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/usb/tm6000/tm6000-video.c
b/drivers/media/usb/tm6000/tm6000-video.c
index 8314d3fa9241..b2399d
Change the logic there to avoid casting, solving this warning:
drivers/media/pci/saa7134/saa7134-alsa.c:276 saa7134_alsa_dma_init()
warn: argument 3 to %08lx specifier is cast from pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/pci/saa7134/saa7134-alsa.c | 5 ++---
1 fil
If the adapter doesn't have error_inj_parse_line() ops, the
write() logic won't return -EINVAL, but, instead, it will keep
looping, because "count" is a non-negative number.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/cec/cec-core.c | 6 +++---
1 file changed, 3 insertions(+), 3 delet
drivers/media/pci/cx23885/cx23885-alsa.c:92 cx23885_alsa_dma_init() warn:
argument 3 to %08lx specifier is cast from pointer
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/pci/cx23885/cx23885-alsa.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/p
Hi Andy,
Some issues found when reviewing cherry pick of this patch to Chrome
OS kernel. Please see inline.
On Sat, Mar 17, 2018 at 1:38 AM, Andy Yeh wrote:
[snip]
> + case V4L2_CID_VBLANK:
> + /*
> +* Auto Frame Length Line Control is enabled by default.
>
Hi Guennadi,
Thank you for the patch.
On Friday, 23 March 2018 11:24:00 EET Laurent Pinchart wrote:
> From: Guennadi Liakhovetski
>
> UVC defines a method of handling asynchronous controls, which sends a
> USB packet over the interrupt pipe. This patch implements support for
> such packets by s
Signed-off-by: Sean Young
---
utils/common/ir-encode.c | 1 +
utils/keytable/keytable.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/utils/common/ir-encode.c b/utils/common/ir-encode.c
index e6b65b5b..c7e319eb 100644
--- a/utils/common/ir-encode.c
+++ b/utils/common/ir-encode.c
@@ -376
Hi Hans and Tomasz,
On Fri, Mar 23, 2018 at 08:38:54AM +0100, Hans Verkuil wrote:
...
> >>>
> >>> Perhaps we need to consider few separate cases here:
> >>>
> >>> 1) Query control value within a request. Would return the value that
> >>> was earlier set to that particular request (and maybe -EBUS
From: Guennadi Liakhovetski
When a command ends up in a STALL on the control pipe, use the Request
Error Code control to provide a more precise error information to the
user.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/usb/uvc/uvc_video.c | 59 +++
From: Guennadi Liakhovetski
UVC defines a method of handling asynchronous controls, which sends a
USB packet over the interrupt pipe. This patch implements support for
such packets by sending a control event to the user. Since this can
involve USB traffic and, therefore, scheduling, this has to b
Hi Guennadi,
As your v7 of this patch series conflicted with the current version of
the uvcvideo driver, I thought it would be easier to rebase it myself
before reviewing, instead of asking you to do so. Here's the result,
I'll send my review comments as replies.
Guennadi Liakhovetski (2):
uvcv
Hi Mauro,
It's probably a bug fix that unveils the link errors.
tree: git://git.ragnatech.se/linux media-tree
head: f67449fdba3b9dbdd340d8cbf17dfa711d5bd2fb
commit: 238f694e1b7f8297f1256c57e41f69c39576c9b4 [369/405] media: v4l2-common:
fix a compilation breakage
config: x86_64-randconfig-s4-
On Thu, Mar 22, 2018 at 09:30:40PM +, Kieran Bingham wrote:
> The r8a7792 Wheat board has two ADV7513 devices sharing a single I2C
> bus, however in low power mode the ADV7513 will reset it's slave maps to
> use the hardware defined default addresses.
>
> The ADV7511 driver was adapted to allo
RFC Request API, version 2
--
This document proposes the public API for handling requests.
There has been some confusion about how to do this, so this summarizes the
current approach based on conversations with the various stakeholders today
(Sakari, Alexandre Courbot, Tho
On 03/23/2018 05:02 AM, Tomasz Figa wrote:
> On Fri, Mar 23, 2018 at 1:28 AM, Hans Verkuil wrote:
>> On 03/22/18 15:47, Tomasz Figa wrote:
>>> Hi Hans,
>>>
>>> On Thu, Mar 22, 2018 at 11:18 PM, Hans Verkuil wrote:
Requests only contain the changes since the previously queued request
87 matches
Mail list logo
