Free memory mapping, if fimc_is_probe is not successful.
Signed-off-by: Arvind Yadav
---
drivers/media/platform/exynos4-is/fimc-is.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/media/platform/exynos4-is/fimc-is.c
b/drivers/media/platform/exynos4-is/fim
On Mon, 05 Dec 2016 23:44:30 +0100,
Shuah Khan wrote:
>
> On 11/30/2016 03:01 PM, Shuah Khan wrote:
> > Change ALSA driver to use Media Controller API to share media resources
> > with DVB, and V4L2 drivers on a AU0828 media device.
> >
> > Media Controller specific initialization is done after s
On Wed, 30 Nov 2016 23:01:16 +0100,
Shuah Khan wrote:
>
> --- a/sound/usb/card.c
> +++ b/sound/usb/card.c
(snip)
> @@ -616,6 +617,11 @@ static int usb_audio_probe(struct usb_interface *intf,
> if (err < 0)
> goto __error;
>
> + if (quirk && quirk->media_device) {
> +
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: Tue Dec 6 05:00:14 CET 2016
media-tree git hash:365fe4e0ce218dc5ad10df17b150a366b6015499
media_build git
On 12/05/2016 04:21 PM, Laurent Pinchart wrote:
> Hi Shuah,
>
> On Monday 05 Dec 2016 15:44:30 Shuah Khan wrote:
>> On 11/30/2016 03:01 PM, Shuah Khan wrote:
>>> Change ALSA driver to use Media Controller API to share media resources
>>> with DVB, and V4L2 drivers on a AU0828 media device.
>>>
>>>
On Thu, Dec 01, 2016 at 11:03:14AM +0200, Stanimir Varbanov wrote:
> Add binding document for Venus video encoder/decoder driver
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Stanimir Varbanov
> ---
> Rob, I have removed vmem clocks, interrupts and reg
Hi Shuah,
On Monday 05 Dec 2016 15:44:30 Shuah Khan wrote:
> On 11/30/2016 03:01 PM, Shuah Khan wrote:
> > Change ALSA driver to use Media Controller API to share media resources
> > with DVB, and V4L2 drivers on a AU0828 media device.
> >
> > Media Controller specific initialization is done afte
Hello Mauro
I just noticed current em28xx driver seem to be broken. When I plug
device first time it loads correctly, but when I re-plug it, it does not
work anymore but yells a lot of noise to message log. Tested with PCTV
290e and 292e both same. Other USB DVB devices are working so it is ver
On 11/30/2016 03:01 PM, Shuah Khan wrote:
> Change ALSA driver to use Media Controller API to share media resources
> with DVB, and V4L2 drivers on a AU0828 media device.
>
> Media Controller specific initialization is done after sound card is
> registered. ALSA creates Media interface and entity
On 5 December 2016 at 18:18, Marcel Hasler wrote:
> 2016-12-05 22:06 GMT+01:00 Marcel Hasler :
>> Hello
>>
>> 2016-12-05 16:38 GMT+01:00 Ezequiel Garcia :
>>> On 5 December 2016 at 09:12, Mauro Carvalho Chehab
>>> wrote:
Em Sun, 4 Dec 2016 15:25:25 -0300
Ezequiel Garcia escreveu:
On 5 December 2016 at 18:06, Marcel Hasler wrote:
> Hello
>
> 2016-12-05 16:38 GMT+01:00 Ezequiel Garcia :
>> On 5 December 2016 at 09:12, Mauro Carvalho Chehab
>> wrote:
>>> Em Sun, 4 Dec 2016 15:25:25 -0300
>>> Ezequiel Garcia escreveu:
>>>
On 4 December 2016 at 10:01, Marcel Hasler wrot
Hi Guennadi,
On Monday 05 Dec 2016 23:13:53 Guennadi Liakhovetski wrote:
> Just one question:
>
> On Tue, 6 Dec 2016, Laurent Pinchart wrote:
> +/*
> + * Register a metadata node. TODO: shall this only be enabled
> for some
> + * cameras?
> +
On Tue, Nov 29, 2016 at 03:57:12PM -0800, Kevin Hilman wrote:
> Signed-off-by: Kevin Hilman
> ---
> .../devicetree/bindings/media/ti,da850-vpif.txt| 67
> ++
> 1 file changed, 67 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/ti,da850-vpif.txt
Just one question:
On Tue, 6 Dec 2016, Laurent Pinchart wrote:
> > >> +/*
> > >> + * Register a metadata node. TODO: shall this only be enabled
> > >> for some
> > >> + * cameras?
> > >> + */
> > >> +if (!(dev->quirks & UVC_QUIRK_BUILTIN_ISIGHT))
> > >> +
Hi Guennadi,
On Monday 05 Dec 2016 16:35:39 Guennadi Liakhovetski wrote:
> On Mon, 5 Dec 2016, Laurent Pinchart wrote:
> > On Friday 02 Dec 2016 11:53:23 Guennadi Liakhovetski wrote:
> >> Some UVC video cameras contain metadata in their payload headers. This
> >> patch extracts that data, skipping
2016-12-05 22:06 GMT+01:00 Marcel Hasler :
> Hello
>
> 2016-12-05 16:38 GMT+01:00 Ezequiel Garcia :
>> On 5 December 2016 at 09:12, Mauro Carvalho Chehab
>> wrote:
>>> Em Sun, 4 Dec 2016 15:25:25 -0300
>>> Ezequiel Garcia escreveu:
>>>
On 4 December 2016 at 10:01, Marcel Hasler wrote:
Hello
2016-12-05 16:38 GMT+01:00 Ezequiel Garcia :
> On 5 December 2016 at 09:12, Mauro Carvalho Chehab
> wrote:
>> Em Sun, 4 Dec 2016 15:25:25 -0300
>> Ezequiel Garcia escreveu:
>>
>>> On 4 December 2016 at 10:01, Marcel Hasler wrote:
>>> > Hello
>>> >
>>> > 2016-12-03 21:46 GMT+01:00 Ezequiel
On Mon, Dec 05, 2016 at 12:46:14PM -0700, Jason Gunthorpe wrote:
> In any event the allocator still needs to track which regions are in
> use and be able to hook 'free' from userspace. That does suggest it
> should be integrated into the nvme driver and not a bolt on driver..
Two totally different
On 05/12/16 12:46 PM, Jason Gunthorpe wrote:
NVMe might have to deal with pci-e hot-unplug, which is a similar
problem-class to the GPU case..
Sure, but if the NVMe device gets hot-unplugged it means that all the
CMB mappings are useless and need to be torn down. This probably means
killing
On Mon, Dec 05, 2016 at 12:27:20PM -0700, Logan Gunthorpe wrote:
>
>
> On 05/12/16 12:14 PM, Jason Gunthorpe wrote:
> >But CMB sounds much more like the GPU case where there is a
> >specialized allocator handing out the BAR to consumers, so I'm not
> >sure a general purpose chardev makes a lot of
On 05/12/16 12:14 PM, Jason Gunthorpe wrote:
But CMB sounds much more like the GPU case where there is a
specialized allocator handing out the BAR to consumers, so I'm not
sure a general purpose chardev makes a lot of sense?
I don't think it will ever need to be as complicated as the GPU case
On Mon, Dec 05, 2016 at 10:48:58AM -0800, Dan Williams wrote:
> On Mon, Dec 5, 2016 at 10:39 AM, Logan Gunthorpe wrote:
> > On 05/12/16 11:08 AM, Dan Williams wrote:
> >>
> >> I've already recommended that iopmem not be a block device and instead
> >> be a device-dax instance. I also don't think i
On Mon, Dec 5, 2016 at 10:39 AM, Logan Gunthorpe wrote:
> On 05/12/16 11:08 AM, Dan Williams wrote:
>>
>> I've already recommended that iopmem not be a block device and instead
>> be a device-dax instance. I also don't think it should claim the PCI
>> ID, rather the driver that wants to map one of
On 05/12/16 11:08 AM, Dan Williams wrote:
I've already recommended that iopmem not be a block device and instead
be a device-dax instance. I also don't think it should claim the PCI
ID, rather the driver that wants to map one of its bars this way can
register the memory region with the device-dax
On Mon, Dec 5, 2016 at 10:02 AM, Jason Gunthorpe
wrote:
> On Mon, Dec 05, 2016 at 09:40:38AM -0800, Dan Williams wrote:
>
>> > If it is kernel only with physical addresess we don't need a uAPI for
>> > it, so I'm not sure #1 is at all related to iopmem.
>> >
>> > Most people who want #1 probably c
On Mon, Dec 05, 2016 at 09:40:38AM -0800, Dan Williams wrote:
> > If it is kernel only with physical addresess we don't need a uAPI for
> > it, so I'm not sure #1 is at all related to iopmem.
> >
> > Most people who want #1 probably can just mmap
> > /sys/../pci/../resourceX to get a user handle t
On Mon, Dec 5, 2016 at 9:18 AM, Jason Gunthorpe
wrote:
> On Sun, Dec 04, 2016 at 07:23:00AM -0600, Stephen Bates wrote:
>> Hi All
>>
>> This has been a great thread (thanks to Alex for kicking it off) and I
>> wanted to jump in and maybe try and put some summary around the
>> discussion. I also wa
Add device tree documentation.
Signed-off-by: Ramiro Oliveira
---
.../devicetree/bindings/media/i2c/ov5647.txt | 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt
diff --git a/Documentation/devicetree/bin
Add support for OV5647 sensor.
Modes supported:
- 640x480 RAW 8
Signed-off-by: Ramiro Oliveira
---
MAINTAINERS| 7 +
drivers/media/i2c/Kconfig | 12 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/ov5647.c | 866 +
4 files
Hello,
This patch adds support for the Omnivision OV5647 sensor.
At the moment it only supports 640x480 in Raw 8.
This is the fifth version of the OV5647 camera driver patchset.
v5:
- Refactor code
- Change comments
- Add missing error handling in some functions
v4:
- Add correct license
On Sun, Dec 04, 2016 at 07:23:00AM -0600, Stephen Bates wrote:
> Hi All
>
> This has been a great thread (thanks to Alex for kicking it off) and I
> wanted to jump in and maybe try and put some summary around the
> discussion. I also wanted to propose we include this as a topic for LFS/MM
> becaus
Helper functions used by decoder back-ends to allocate
physically contiguous memory required by hardware video
decoder.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/sti/delta/Makefile| 2 +-
drivers/media/platform/sti/delta/delta-mem.c | 51
drivers/
Adds support of DELTA MJPEG video decoder back-end,
implemented by calling JPEG_DECODER_HW0 firmware
using RPMSG IPC communication layer.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/Kconfig | 6 +
drivers/media/platform/sti/delta/Makefile | 4 +
driv
Adds some trace points showing input compressed stream or
output decoded frame information.
Adds an unconditional trace point when streaming starts showing
the compressed stream and the decoded frame information.
Adds an unconditional trace point at instance closure summarizing
into a single line t
IPC (Inter Process Communication) support for communication with
DELTA coprocessor firmware using rpmsg kernel framework.
Based on 4 services open/set_stream/decode/close and their associated
rpmsg messages.
The messages structures are duplicated on both host and firmware
side and are packed (use o
EOS (End Of Stream) support allows user to get
all the potential decoded frames remaining in decoder
pipeline after having reached the end of video bitstream.
To do so, user calls VIDIOC_DECODER_CMD(V4L2_DEC_CMD_STOP)
which will drain the decoder and get the drained frames
that are then returned to
Add entry for the STMicroelectronics DELTA driver.
Signed-off-by: Hugues Fruchet
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7db3f7a..a96dd22 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2394,6 +2394,14 @@ W: https://linuxtv
Enables support of STMicroelectronics STiH4xx SoC series
DELTA multi-format video decoder V4L2 driver.
Signed-off-by: Hugues Fruchet
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defcon
This V4L2 driver enables DELTA multi-format video decoder
of STMicroelectronics STiH4xx SoC series.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/Kconfig| 20 +
drivers/media/platform/Makefile |2 +
drivers/media/platform/sti/delta/Makefile |
This patch adds DT binding documentation for STMicroelectronics
DELTA V4L2 video decoder.
Signed-off-by: Hugues Fruchet
---
Documentation/devicetree/bindings/media/st,st-delta.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media
This patchset introduces a basic support for DELTA multi-format video
decoder of STMicroelectronics STiH4xx SoC series.
DELTA hardware IP is controlled by a remote firmware loaded in a ST231
coprocessor. Communication with firmware is done within an IPC layer
using rpmsg kernel framework and a sha
This patch adds DT node for STMicroelectronics
DELTA V4L2 video decoder
Signed-off-by: Hugues Fruchet
---
arch/arm/boot/dts/stih410.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/stih410.dtsi b/arch/arm/boot/dts/stih410.dtsi
index a3ef734..fb03cb67 100644
On Mon, 2016-12-05 at 23:47 +0800, Icenowy Zheng wrote:
> 2016年12月5日 19:49于 Lubomir Rintel 写道：
> >
> > On Sun, 2016-12-04 at 22:59 +0800, Icenowy Zheng wrote:
> > >
> > > 04.12.2016, 22:00, "Icenowy Zheng" :
> > > > A new usbid of UTV007 is found in a newly bought device.
> > > >
> > > > The
Hi Laurent,
Thanks for the review! I'll work to address your comments. A couple of
clarifications:
On Mon, 5 Dec 2016, Laurent Pinchart wrote:
> Hi Guennadi,
>
> Thank you for the patch.
>
> On Friday 02 Dec 2016 11:53:23 Guennadi Liakhovetski wrote:
> > Some UVC video cameras contain metadat
On 5 December 2016 at 09:12, Mauro Carvalho Chehab
wrote:
> Em Sun, 4 Dec 2016 15:25:25 -0300
> Ezequiel Garcia escreveu:
>
>> On 4 December 2016 at 10:01, Marcel Hasler wrote:
>> > Hello
>> >
>> > 2016-12-03 21:46 GMT+01:00 Ezequiel Garcia :
>> >> On 2 December 2016 at 08:05, Mauro Carvalho Che
Hi Hans,
On Monday 05 Dec 2016 16:02:55 Hans Verkuil wrote:
> On 12/05/2016 03:45 PM, Laurent Pinchart wrote:
> > On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
> >> On 11/25/2016 03:57 PM, Todor Tomov wrote:
> >>> These files handle the video device nodes of the camss driver.
> >>>
> >>> Sig
Hi Todor,
Thank you for the patch.
On Friday 25 Nov 2016 16:57:20 Todor Tomov wrote:
> These files handle the video device nodes of the camss driver.
camss is a quite generic, I'm a bit concerned about claiming that acronym in
the global kernel namespace. Would it be too long if we prefixed sym
On 12/05/2016 03:45 PM, Laurent Pinchart wrote:
> Hello,
>
> On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
>> On 11/25/2016 03:57 PM, Todor Tomov wrote:
>>> These files handle the video device nodes of the camss driver.
>>>
>>> Signed-off-by: Todor Tomov
>>> ---
>>>
>>> drivers/media/platfo
Hello,
On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
> On 11/25/2016 03:57 PM, Todor Tomov wrote:
> > These files handle the video device nodes of the camss driver.
> >
> > Signed-off-by: Todor Tomov
> > ---
> >
> > drivers/media/platform/qcom/camss-8x16/video.c | 597
>
Hi Hans,
On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
> > +static int video_querycap(struct file *file, void *fh,
> > + struct v4l2_capability *cap)
> > +{
> > + strlcpy(cap->driver, "qcom-camss", sizeof(cap->driver));
> > + strlcpy(cap->card, "Qualcomm Camera S
Hi Evgeni,
On Monday 05 Dec 2016 15:24:59 evgeni.raik...@gmail.com wrote:
> From: Evgeni Raikhel
>
> Provide the frame structure and data layout of V4L2-PIX-FMT-INZI
> format utilized by Intel SR300 Depth camera.
>
> This is a complimentary patch for:
> [PATCH] UVC: Add support for Intel SR300
Hi Evgeni,
Thank you for the patch.
On Monday 05 Dec 2016 15:24:59 evgeni.raik...@gmail.com wrote:
> From: Evgeni Raikhel
>
> Provide the frame structure and data layout of V4L2-PIX-FMT-INZI
> format utilized by Intel SR300 Depth camera.
>
> This is a complimentary patch for:
> [PATCH] UVC: Ad
A few comments below:
On 11/25/2016 03:57 PM, Todor Tomov wrote:
> These files handle the video device nodes of the camss driver.
>
> Signed-off-by: Todor Tomov
> ---
> drivers/media/platform/qcom/camss-8x16/video.c | 597
> +
> drivers/media/platform/qcom/camss-8x16/vi
Hi Laurent,
Thanks for the feedback - I resubmitted the patches inline, as requested.
Regards,
Evgeni Raikhel
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Monday, December 05, 2016 13:02
To: Raikhel, Evgeni
Cc: linux-media@vger.kernel.org
S
Thanks Hans, I will change depends to select.
BR,
Hugues.
On 12/05/2016 11:47 AM, Hans Verkuil wrote:
> On 11/22/2016 04:53 PM, Hugues Fruchet wrote:
>> IPC (Inter Process Communication) support for communication with
>> DELTA coprocessor firmware using rpmsg kernel framework.
>> Based on 4 servic
From: eraikhel
*** Enable Intel RealSense™ SR300 Depth camera pixel formats to be recognized
correctly by uvc module ***
Aviv Greenberg (1):
UVC: Add support for Intel SR300 depth camera
Evgeni Raikhel (1):
Document Intel SR300 Depth camera INZI format
Documentation/media/uapi/v4l/pixfm
From: Evgeni Raikhel
Provide the frame structure and data layout of V4L2-PIX-FMT-INZI
format utilized by Intel SR300 Depth camera.
This is a complimentary patch for:
[PATCH] UVC: Add support for Intel SR300 depth camera
Signed-off-by: Evgeni Raikhel
---
Documentation/media/uapi/v4l/pixfmt-inz
From: Aviv Greenberg
Add support for Intel SR300 depth camera in uvc driver.
This includes adding three uvc GUIDs for the required pixel formats,
adding a new V4L pixel format definition to user api headers,
and updating the uvc driver GUID-to-4cc tables with the new formats.
Signed-off-by: Aviv
Thanks Hans, I will test with new compliance.
BR,
Hugues.
On 12/05/2016 11:18 AM, Hans Verkuil wrote:
> Hi Hugues,
>
> On 11/22/2016 04:53 PM, Hugues Fruchet wrote:
>> This patchset introduces a basic support for DELTA multi-format video
>> decoder of STMicroelectronics STiH4xx SoC series.
>>
>> D
Hello Javi,
On 12/05/2016 07:09 AM, Javi Merino wrote:
> In asds configured with V4L2_ASYNC_MATCH_OF, the v4l2 subdev can be
> part of a devicetree overlay, for example:
>
> &media_bridge {
> ...
> my_port: port@0 {
> #address-cells = <1>;
> #size-cells = <
Hi Hans,
Thanks for the comments!
On 12/05/2016 01:32 PM, Hans Verkuil wrote:
> I have two comments (and the same two comments apply to the video encoder
> patch
> as well):
>
> On 12/01/2016 10:03 AM, Stanimir Varbanov wrote:
>> This consists of video decoder implementation plus decoder
>> con
Please provide a commit message, it shouldn't be empty.
But are you sure you want to enable it in the defconfig? I think in general
DEBUGFS config options aren't enabled by default.
Regards,
Hans
On 11/28/2016 11:30 AM, Jean-Christophe Trotin wrote:
> Signed-off-by: Jean-Christophe Trot
Hi Hans,
On 12/05/2016 01:25 PM, Hans Verkuil wrote:
> On 12/01/2016 10:03 AM, Stanimir Varbanov wrote:
>> this add functions for:
>> - remove buffers from src/dst queue by index
>> - remove exact buffer from src/dst queue
>>
>> also extends m2m API to iterate over a list of src/dst buffers
>>
On 12/01/2016 10:16 AM, Laurent Pinchart wrote:
> Hello,
>
> On Thursday 01 Dec 2016 09:57:31 Sakari Ailus wrote:
>> On Wed, Nov 30, 2016 at 04:14:11PM -0800, Kevin Hilman wrote:
>>> Sakari Ailus writes:
On Wed, Nov 23, 2016 at 03:25:32PM -0800, Kevin Hilman wrote:
> Sakari Ailus writes
Hi Hans,
On 12/05/2016 02:05 PM, Hans Verkuil wrote:
> On 12/01/2016 10:03 AM, Stanimir Varbanov wrote:
>> Here is the implementation of Venus video accelerator low-level
>> functionality. It contanins code which setup the registers and
>> startup uthe processor, allocate and manipulates with the
On Sun, 2016-12-04 at 21:59 +0800, Icenowy Zheng wrote:
> A new usbid of UTV007 is found in a newly bought device.
>
> The usbid is 1f71:3301.
>
> The ID on the chip is:
> UTV007
> A89029.1
> 1520L18K1
>
> Both video and audio is tested with the modified usbtv driver.
Thank you.
Acked-by: Lubo
Em Sun, 4 Dec 2016 15:25:25 -0300
Ezequiel Garcia escreveu:
> On 4 December 2016 at 10:01, Marcel Hasler wrote:
> > Hello
> >
> > 2016-12-03 21:46 GMT+01:00 Ezequiel Garcia :
> >
> >> On 2 December 2016 at 08:05, Mauro Carvalho Chehab
> >> wrote:
> >>> Em Sun, 27 Nov 2016 12:11:48 +0100
>
On Sun, 2016-12-04 at 22:59 +0800, Icenowy Zheng wrote:
>
> 04.12.2016, 22:00, "Icenowy Zheng" :
> > A new usbid of UTV007 is found in a newly bought device.
> >
> > The usbid is 1f71:3301.
> >
> > The ID on the chip is:
> > UTV007
> > A89029.1
> > 1520L18K1
> >
>
> Seems that my device come w
On 12/01/2016 10:03 AM, Stanimir Varbanov wrote:
> Here is the implementation of Venus video accelerator low-level
> functionality. It contanins code which setup the registers and
> startup uthe processor, allocate and manipulates with the shared
> memory used for sending commands and receiving mes
I have two comments (and the same two comments apply to the video encoder patch
as well):
On 12/01/2016 10:03 AM, Stanimir Varbanov wrote:
> This consists of video decoder implementation plus decoder
> controls.
>
> Signed-off-by: Stanimir Varbanov
> ---
> drivers/media/platform/qcom/venus/vdec
On 12/01/2016 10:03 AM, Stanimir Varbanov wrote:
> this add functions for:
> - remove buffers from src/dst queue by index
> - remove exact buffer from src/dst queue
>
> also extends m2m API to iterate over a list of src/dst buffers
> in safely and non-safely manner.
>
> Signed-off-by: Stanimi
Hi Evgeni,
Thank you for the patch.
On Monday 05 Dec 2016 10:06:55 Raikhel, Evgeni wrote:
> Specify GUID and FourCC codes mapping for Depth-related pixel formats
> advertised by Intel RealSense(tm) SR300 depth camera. Provide documentation
> for the new INZI pixel format introduced.
Could you pl
Hi Guennadi,
Thank you for the patch.
On Friday 02 Dec 2016 11:53:23 Guennadi Liakhovetski wrote:
> Some UVC video cameras contain metadata in their payload headers. This
> patch extracts that data, skipping the standard part of the header, on
> both bulk and isochronous endpoints and makes it av
On 11/22/2016 04:53 PM, Hugues Fruchet wrote:
> IPC (Inter Process Communication) support for communication with
> DELTA coprocessor firmware using rpmsg kernel framework.
> Based on 4 services open/set_stream/decode/close and their associated
> rpmsg messages.
> The messages structures are duplica
Hi Hugues,
On 11/22/2016 04:53 PM, Hugues Fruchet wrote:
> This patchset introduces a basic support for DELTA multi-format video
> decoder of STMicroelectronics STiH4xx SoC series.
>
> DELTA hardware IP is controlled by a remote firmware loaded in a ST231
> coprocessor. Communication with firmwar
In asds configured with V4L2_ASYNC_MATCH_OF, the v4l2 subdev can be
part of a devicetree overlay, for example:
&media_bridge {
...
my_port: port@0 {
#address-cells = <1>;
#size-cells = <0>;
reg = <0>;
ep: endpoint@0 {
Specify GUID and FourCC codes mapping for Depth-related pixel formats
advertised by Intel RealSense(tm) SR300 depth camera.
Provide documentation for the new INZI pixel format introduced.
-
Intel Israel (74) Limited
This e-mail
77 matches
Mail list logo
