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 Aug 19 05:00:16 CEST 2017
media-tree git hash:ec0c3ec497cabbf3bfa03a9eb5edcc252190a4e0
media_build gi
The V4L2_BUF_TYPE_META_OUTPUT mirrors the V4L2_BUF_TYPE_META_CAPTURE with
the exception that it is an OUTPUT type. The use case for this is to pass
buffers to the device that are not image data but metadata. The formats,
just as the metadata capture formats, are typically device specific and
highly
Document the interface for metadata output, including
V4L2_BUF_TYPE_META_OUTPUT buffer type and V4L2_CAP_META_OUTPUT capability
bits.
Signed-off-by: Sakari Ailus
Acked-by: Hans Verkuil
---
Documentation/media/uapi/v4l/buffer.rst | 3 +++
Documentation/media/uapi/v4l/dev-meta.rst
Hi folks,
Here's a non-RFC version of the META_OUTPUT buffer type patches.
The V4L2_BUF_TYPE_META_OUTPUT buffer type complements the metadata buffer
types support for OUTPUT buffers, capture being already supported. This is
intended for similar cases than V4L2_BUF_TYPE_META_CAPTURE but for output
On Fri, Aug 18, 2017 at 11:16:33AM +0300, Todor Tomov wrote:
> Add explanations for VFE's PIX and RDI interfaces.
>
> Signed-off-by: Todor Tomov
For both:
Acked-by: Sakari Ailus
--
Sakari Ailus
e-mail: sakari.ai...@iki.fi
Call function v4l2_m2m_dst_buf_remove_by_buf() instead of
v4l2_m2m_src_buf_remove_by_buf()
Addresses-Coverity-ID: 1415317
Cc: Stanimir Varbanov
Cc: Hans Verkuil
Signed-off-by: Gustavo A. R. Silva
---
Changes in v2:
Stanimir Varbanov confirmed this is a bug. The correct fix is to call
function
Hi Stanimir,
On 08/18/2017 02:52 AM, Stanimir Varbanov wrote:
Hi Gustavo,
On 08/18/2017 02:12 AM, Gustavo A. R. Silva wrote:
Refactor code in order to avoid identical code for different branches.
This issue was detected with the help of Coccinelle.
Addresses-Coverity-ID: 1415317
Signed-off-b
Make these const.
Bhumika Goyal (2):
i2c: busses: make i2c_algorithm const
[media] usb: make i2c_algorithm const
drivers/i2c/busses/i2c-pnx.c | 2 +-
drivers/i2c/busses/i2c-puv3.c| 2 +-
drivers/media/usb/au0828/au0828-i2c.c| 2 +-
drivers/media/usb/pv
Make these const as they are only stored in the algo field of
i2c_adapter structure, which is const.
Signed-off-by: Bhumika Goyal
---
drivers/i2c/busses/i2c-pnx.c | 2 +-
drivers/i2c/busses/i2c-puv3.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-
Make these const as they are only used in a copy operation or
are stored in the algo field of i2c_adapter structure, which is const.
Signed-off-by: Bhumika Goyal
---
drivers/media/usb/au0828/au0828-i2c.c| 2 +-
drivers/media/usb/pvrusb2/pvrusb2-i2c-core.c | 2 +-
2 files changed, 2 inser
Hi Hans,
On 08/18/2017 05:30 PM, Hans Verkuil wrote:
> On 08/18/17 16:16, Stanimir Varbanov wrote:
>> This change is intended to give to the v4l2 drivers a choice to
>> change the default behavior of the v4l2-core DMA mapping direction
>> from DMA_TO/FROM_DEVICE (depending on the buffer type CAPTU
On 08/18/17 16:16, Stanimir Varbanov wrote:
> This change is intended to give to the v4l2 drivers a choice to
> change the default behavior of the v4l2-core DMA mapping direction
> from DMA_TO/FROM_DEVICE (depending on the buffer type CAPTURE or
> OUTPUT) to DMA_BIDIRECTIONAL during queue_init time
Hello,
Patch 1/7 has been sent already as an RFC but in this patchset
it can be found as a regular patch. The RFC version can be found
at [1] and also to prove its need look at [2]. Patch 2/7 fixes
Venus encoder issue with help of 1/7.
The other patches 3/7 to 7/7 can be treated as updates for
v4
This change is intended to give to the v4l2 drivers a choice to
change the default behavior of the v4l2-core DMA mapping direction
from DMA_TO/FROM_DEVICE (depending on the buffer type CAPTURE or
OUTPUT) to DMA_BIDIRECTIONAL during queue_init time.
Initially the issue with DMA mapping direction ha
This fills missing (forgotten) video device name with
appropriate string so that udev can distinguishes between
decoder and encoder devices.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/vdec.c | 1 +
drivers/media/platform/qcom/venus/venc.c | 1 +
2 files changed, 2 ins
This change the alignment restriction for output type of buffers
only, also set corect input resolution and fill bidirectional
vb2 queue flag in order to map output type buffers read/write.
The last is needed by encoder firmware to add padding at the
bottom of output (input buffers).
Signed-off-by
Without PM support gcc could warns about unused functions, thus
mark runtime_suspend/resume as __maybe_unused.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/vdec.c | 6 ++
drivers/media/platform/qcom/venus/venc.c | 6 ++
2 files changed, 4 insertions(+), 8 deleti
Adds a helper function to runtime check supported encoder and
decoder codecs depending on venus version and platform.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/helpers.c | 49 +
drivers/media/platform/qcom/venus/helpers.h | 1 +
2 files c
Use the helper function in decoder and encoder find_format
to runtime check supported codecs.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/vdec.c | 24 +---
drivers/media/platform/qcom/venus/venc.c | 28 +++-
2 files changed,
No one of the supported Venus version has implemented VP9 codec
for enconding, so drop it from the list of codecs.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/venc.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/media/platform/qcom/venus/venc.c
b/driv
On Fri, Aug 18, 2017 at 02:23:14PM +0300, Sakari Ailus wrote:
> Hi folks,
>
> We have a large influx of new, unmerged, drivers that are now parsing
> fwnode endpoints and each one of them is doing this a little bit
> differently. The needs are still exactly the same for the graph data
> structure
On Fri, Aug 18, 2017 at 03:42:07PM +0200, Niklas Söderlund wrote:
> Hi,
>
> On 2017-08-18 14:15:26 +0300, Laurent Pinchart wrote:
> > Hi Sakari,
> >
> > On Tuesday 15 Aug 2017 19:16:14 Sakari Ailus wrote:
> > > On Mon, Jul 31, 2017 at 12:31:55AM +0200, Niklas Söderlund wrote:
> > > > The call to
Hi Sakari and Laurent,
Thanks for your feedback.
On 2017-08-18 14:20:08 +0300, Laurent Pinchart wrote:
> Hello,
>
> On Tuesday 15 Aug 2017 19:09:33 Sakari Ailus wrote:
> > On Mon, Jul 31, 2017 at 12:31:58AM +0200, Niklas Söderlund wrote:
> > > The re-probing of subdevices when unregistering a no
Hi,
On 2017-08-18 14:15:26 +0300, Laurent Pinchart wrote:
> Hi Sakari,
>
> On Tuesday 15 Aug 2017 19:16:14 Sakari Ailus wrote:
> > On Mon, Jul 31, 2017 at 12:31:55AM +0200, Niklas Söderlund wrote:
> > > The call to v4l2_async_cleanup() will set sd->asd to NULL so passing it
> > > to notifier->unb
Note from Laurent: the series merges cleanly with Dave's drm-next branch
(git://people.freedesktop.org/~airlied/linux) that contains a large series of
VSP patches. There should thus be no merge conflict (at least none that git
won't solve automatically) when merging upstream.
Regards,
Han
Camera flash drivers (and LEDs) are separate from the sensor devices in
DT. In order to make an association between the two, provide the
association information to the software.
Signed-off-by: Sakari Ailus
---
Hi Rob and Jacek, others,
I know I've submitted previous versions of this patch that I
On Sun, Jul 30, 2017 at 09:23:10PM +0800, Shawn Guo wrote:
> From: Shawn Guo
>
> The series adds dt-bindings and remote control driver for IRDEC block
> found on ZTE ZX family SoCs.
>
> Changes for v2:
> - Add one patch to move generic NEC scancode composing and protocol
>type detection cod
Hi,
the patch below adds the entries to the config arrays for a capture-only
board distributed by MAGIX [0]. The hardware itself (EM2860, SAA7113,
EMP202) is already supported.
This patch lacks the configuration for the GPIO pin, because I had/have
no time yet to figure out how it works. Video and
The current practice is that drivers iterate over their endpoints and
parse each endpoint separately. This is very similar in a number of
drivers, implement a generic function for the job. Driver specific matters
can be taken into account in the driver specific callback.
Convert the omap3isp as an
Hi folks,
We have a large influx of new, unmerged, drivers that are now parsing
fwnode endpoints and each one of them is doing this a little bit
differently. The needs are still exactly the same for the graph data
structure is device independent. This is still a non-trivial task and the
majority o
This is the preferred way to parse the endpoints.
Signed-off-by: Sakari Ailus
---
drivers/media/v4l2-core/v4l2-fwnode.c | 51 +++
include/media/v4l2-fwnode.h | 7 +
2 files changed, 58 insertions(+)
diff --git a/drivers/media/v4l2-core/v4l2-fwnode.
struct omap3isp.subdevs field and ISP_MAX_SUBDEVS macro are both unused.
Remove them.
Signed-off-by: Sakari Ailus
---
drivers/media/platform/omap3isp/isp.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/media/platform/omap3isp/isp.h
b/drivers/media/platform/omap3isp/isp.h
index e
Hello,
On Tuesday 15 Aug 2017 19:09:33 Sakari Ailus wrote:
> On Mon, Jul 31, 2017 at 12:31:58AM +0200, Niklas Söderlund wrote:
> > The re-probing of subdevices when unregistering a notifier is tricky to
> > understand, and implemented somewhat as a hack. Add a comment trying to
> > explain why the
Hi Sakari,
On Tuesday 15 Aug 2017 19:16:14 Sakari Ailus wrote:
> On Mon, Jul 31, 2017 at 12:31:55AM +0200, Niklas Söderlund wrote:
> > The call to v4l2_async_cleanup() will set sd->asd to NULL so passing it
> > to notifier->unbind() have no effect and leaves the notifier confused.
> > Call the unb
Hi Niklas,
Thank you for the patch.
On Monday 31 Jul 2017 00:31:55 Niklas Söderlund wrote:
> The call to v4l2_async_cleanup() will set sd->asd to NULL so passing it
> to notifier->unbind() have no effect and leaves the notifier confused.
> Call the unbind() callback prior to cleaning up the subde
Hi Mauro,
These are just fixes to ir-keytable and ir-ctl. Please let me know if you
have any ideas for improving them.
Thanks,
Sean
The following changes since commit 16c3764b636d647a8b41bc34d34722678220a9ff:
cec-ctl: refactor: split the monitor code off into its own function
(2017-08-01
On 08/18/17 11:02, Tomi Valkeinen wrote:
> Hi Hans,
>
>
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>
> On 11/08/17 13:57, Tomi Valkeinen wrote:
>
>> I'm doing some testing with this series on my panda. One
Use flags the device exposes for UVC controls.
This allows the device to define which property flags are set.
Since some cameras offer auto-adjustments for properties (e.g. auto-gain),
the values of other properties (e.g. gain) can change in the camera.
Examining the flags ensures that the driver
Hi Mauro,
Here are more sensor driver patches for 4.14.
Please pull.
The following changes since commit ec0c3ec497cabbf3bfa03a9eb5edcc252190a4e0:
media: ddbridge: split code into multiple files (2017-08-09 12:17:01 -0400)
are available in the git repository at:
ssh://linuxtv.org/git/sail
Hi Rohit,
Thank you for the patch.
On Wednesday 09 Aug 2017 11:27:54 Rohit Athavale wrote:
> This commit adds the custom Xilinx IP specific 8-bit YCbCr 4:2:0
> to the custom formats area in the subdev-formats documentation.
>
> Signed-off-by: Rohit Athavale
> ---
> Documentation/media/uapi/v4l
Hi Rohit,
Thank you for the patch.
On Wednesday 09 Aug 2017 11:27:52 Rohit Athavale wrote:
> This commit adds Xilinx Video IP specific 8-bit color depth YCbCr 4:2:0
> to the media bus format uapi.
>
> Signed-off-by: Rohit Athavale
> ---
> include/uapi/linux/media-bus-format.h | 4 +++-
> 1 fil
Hi Rohit,
Thank you for the patch.
On Wednesday 09 Aug 2017 11:27:53 Rohit Athavale wrote:
> Add Xilinx YCbCr 4:2:0 to xvip formats table. This commit
> will allow driver to setup media pad codes to YUV 420
> via DT properties.
>
> Signed-off-by: Rohit Athavale
> ---
> drivers/media/platform/x
Hi Hans,
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 11/08/17 13:57, Tomi Valkeinen wrote:
> I'm doing some testing with this series on my panda. One issue I see is
> that when I unload the display modules,
On Thu, Aug 17, 2017 at 11:38:43PM +0200, Pavel Machek wrote:
> On Wed 2017-08-16 10:33:45, Sakari Ailus wrote:
> > The et8ek8 driver combines I²C register writes to a single array that it
> > passes to i2c_transfer(). The maximum number of writes is 48 at once,
> > decrease it to 8 and make more t
Add explanations for VFE's PIX and RDI interfaces.
Signed-off-by: Todor Tomov
---
Documentation/media/v4l-drivers/qcom_camss.rst | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/media/v4l-drivers/qcom_camss.rst
b/Documentation/media/v4l-drivers/qcom_
Add abbreviations explanation at the top header blocks in source files.
Signed-off-by: Todor Tomov
---
drivers/media/platform/qcom/camss-8x16/camss-csid.c | 2 +-
drivers/media/platform/qcom/camss-8x16/camss-csid.h | 2 +-
drivers/media/platform/qcom/camss-8x16/camss-ispif.c | 2 +-
drivers/me
Hi Hans,
On 18.08.2017 10:45, Hans Verkuil wrote:
> Hi Todor,
>
> A few small comments below:
>
> On 08/08/2017 03:30 PM, Todor Tomov wrote:
>> Add a document to describe Qualcomm Camera Subsystem driver.
>>
>> Signed-off-by: Todor Tomov
>> ---
>> Documentation/media/v4l-drivers/qcom_camss.rst
Hi Gustavo,
On 08/18/2017 02:12 AM, Gustavo A. R. Silva wrote:
> Refactor code in order to avoid identical code for different branches.
>
> This issue was detected with the help of Coccinelle.
>
> Addresses-Coverity-ID: 1415317
> Signed-off-by: Gustavo A. R. Silva
> ---
> This code was reported
Hi Todor,
A few small comments below:
On 08/08/2017 03:30 PM, Todor Tomov wrote:
> Add a document to describe Qualcomm Camera Subsystem driver.
>
> Signed-off-by: Todor Tomov
> ---
> Documentation/media/v4l-drivers/qcom_camss.rst | 124
> +
> 1 file changed, 124 insert
Hi Fabio,
On Thu, 2017-08-17 at 18:12 -0300, Fabio Estevam wrote:
> From: Fabio Estevam
>
> platform_get_irq() may fail, so we should better check its return
> value and propagate it in the case of error.
>
> Signed-off-by: Fabio Estevam
> ---
> drivers/media/platform/mx2_emmaprp.c | 2 ++
>
Hi Fabio,
On Wed, 2017-08-16 at 21:14 -0300, Fabio Estevam wrote:
> > From: Fabio Estevam
>
> platform_get_resource() may fail and in this case a NULL dereference
> will occur.
>
> Prevent this from happening by returning an error on
> platform_get_resource() failure.
>
> Fixes: b0444f18e0b18
Lots of constify stuff, some random other fixes.
The following changes since commit ec0c3ec497cabbf3bfa03a9eb5edcc252190a4e0:
media: ddbridge: split code into multiple files (2017-08-09 12:17:01 -0400)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git for-v4.
Some cameras post inaccurate frame where next frame data overlap
it. this results in screen flicker, and it need to be prevented.
So this patch marks the buffer error to discard the frame where
buffer overflow.
Signed-off-by: Baoyou Xie
---
drivers/media/usb/uvc/uvc_video.c | 1 +
1 file change
53 matches
Mail list logo
