These formats are compressed 12-bit raw bayer formats with four different
pixel orders. They are similar to 10-bit bayer formats 'IPU3'.
Signed-off-by: Edgar Thier
---
drivers/media/usb/uvc/uvcvideo.h | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/medi
On the GTA04, current consumption rose by about 30mA when the omap3_isp
module was loaded and the v4l device was not accessed and even no
camera attached.
Module removal fixed it again. Slowing down the removal process reveals
that calling isp_detach_iommu() is required to have low
current. So isp_
Hi Michael,
I love your patch! Yet something to improve:
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v5.0-rc1 next-20190109]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
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: Thu Jan 10 05:00:11 CET 2019
media-tree git hash:1e0d0a5fd38192f23304ea2fc2b531fea7c74247
media_build git
We see your photos photos for editing.
Please send us the details of this task.
Do your photos need cut out? Or clipping path, and retouching?
You may give us 1 photo, we will do test for you to check the quality.
Thanks,
Helen
On Wed, Jan 9, 2019 at 1:24 PM Marcel Holtmann wrote:
>
> Hi Sebastian,
>
> >>> +static int ll_register_fm(struct ll_device *lldev)
> >>> +{
> >>> + struct device *dev = &lldev->serdev->dev;
> >>> + int err;
> >>> +
> >>> + if (!of_device_is_compatible(dev->of_node, "ti,wl1281-st") &&
> >>>
On 1/9/19 2:40 PM, Niklas Söderlund wrote:
Hi Steve,
Thanks for your patch, I think it looks good.
Thanks for the Ack! I'm not real familiar with the RFC patch process.
Should this be submitted again with RFC stripped from the subject line?
Steve
On 2019-01-06 13:20:18 -0800, Steve Lon
We see your photos photos for editing.
Please send us the details of this task.
Do your photos need cut out? Or clipping path, and retouching?
You may give us 1 photo, we will do test for you to check the quality.
Thanks,
Helen
Reviewed-by: Steve Longerbeam
On 1/9/19 3:08 AM, Philipp Zabel wrote:
Prepare for mbus format being smaller than the written rectangle
due to burst size.
Signed-off-by: Philipp Zabel
---
Changes since v1:
- Typo fixups, this time applied to the correct patch.
---
drivers/staging/media/im
Reviewed-by: Steve Longerbeam
On 1/9/19 3:08 AM, Philipp Zabel wrote:
Allowing to compose captured images into larger memory buffers
will let us lift alignment restrictions on CSI crop width.
Signed-off-by: Philipp Zabel
Acked-by: Sakari Ailus
---
Changes since v1:
- remove NATIVE_SIZE se
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
Hi Steve,
Thanks for your patch, I think it looks good.
On 2019-01-06 13:20:18 -0800, Steve Longerbeam wrote:
> There is a block of code in rvin_group_link_notify() that loops through
> all entities in the media graph, and prevents enabling a link to a VIN
> node if any entity is in use. This pre
On Mon, 7 Jan 2019 11:18:58 +0100
Hans Verkuil wrote:
> On 01/03/2019 07:01 PM, Antonio Ospite wrote:
> > Add a new option --list-ctrls-values to list the values of controls in
> > a format which can be passed again to --set-ctrl.
> >
> > This can be useful to save and restore device settings:
>
Hi Paweł,
Thank you for the patch.
On 1/9/19 7:00 PM, Paweł Chmiel wrote:
This commit corrects max and step values for v4l2 control for
V4L2_CID_JPEG_RESTART_INTERVAL. Max should be 0x and step should be 1.
It was found by using v4l2-compliance tool and checking result of
VIDIOC_QUERY_EXT_C
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
P010 is a planar 4:2:0 YUV with interleaved UV plane, 10 bits per
channel video format.
P012 is a planar 4:2:0 YUV 12 bits per channel
P016 is a planar 4:2:0 YUV with interleaved UV plane, 16 bits per
channel video format.
V3: Added P012 and fixed cpp for P010.
V4: format definition refined per
This pixel format is a fully packed and 10bits variant of NV12.
A luma pixel would take 10bits in memory, without any
filled bits between pixels in a stride.
Signed-off-by: Randy Li
---
drivers/gpu/drm/drm_fourcc.c | 4
include/uapi/drm/drm_fourcc.h | 8
2 files changed, 12 insert
As the requirement from:
P010 fourcc format support - Was: Re: Kernel error "Unknown pixelformat
0x" occurs when I start capture video
I don't know which device would support the P010, P012, P016 video pixel
format, but Rockchip would support that NV12_10LE40 and a patch for that
driver is
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
Do you have photos for editing? We asked this because we see your photos on
your website.
We mainly supply service for photos cut out , clipping path, and
retouching.
You may just send us a photo, we can provide you test editing to check
quality.
Thanks,
Jane
Hi Sebastian,
>>> +static int ll_register_fm(struct ll_device *lldev)
>>> +{
>>> + struct device *dev = &lldev->serdev->dev;
>>> + int err;
>>> +
>>> + if (!of_device_is_compatible(dev->of_node, "ti,wl1281-st") &&
>>> + !of_device_is_compatible(dev->of_node, "ti,wl1283-st") &&
>>> +
On 1/9/19 3:08 AM, Philipp Zabel wrote:
The CSI, PRP ENC, and PRP VF subdevices shouldn't have to care about
IDMAC line start address alignment. With compose rectangle support in
the capture driver, they don't have to anymore.
If the direct CSI -> IC path is enabled, the CSI output width must
Hi Jacopo,
> Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
>
> Hi Raj,
>
> On Wed, Jan 09, 2019 at 06:01:39PM +, Mani, Rajmohan wrote:
> > Hi Jacopo,
> >
> > > Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
> > >
> > > Hello Raj,
> > >
> > > On Wed, Jan 09, 2019 at 05:00:21P
Some imx platforms do not have fwnode connections to all CSI input
ports, and should not be treated as an error. This includes the
imx6q SabreAuto, which has no connections to ipu1_csi1 and ipu2_csi0.
Return -ENOTCONN in imx_csi_parse_endpoint() so that v4l2-fwnode
endpoint parsing will not treat a
If the incoming sink field type is alternate, the reset crop height
and crop height bounds must be set to twice the incoming height,
because in alternate field mode, upstream will report only the
lines for a single field, and the CSI captures the whole frame.
Signed-off-by: Steve Longerbeam
Revie
Skip writing U/V components to odd rows for YVU420 in addition to
YUV420 and NV12.
Signed-off-by: Steve Longerbeam
Reviewed-by: Philipp Zabel
---
drivers/staging/media/imx/imx-media-csi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/media/imx/imx-media-csi.c
b/drivers/st
To support interlaced scan with planar formats, cpmem SLUV must
be programmed with the correct chroma line stride. For full and
partial planar 4:2:2 (YUV422P, NV16), chroma line stride must
be doubled. For full and partial planar 4:2:0 (YUV420, YVU420, NV12),
chroma line stride must _not_ be double
The function ipu_csi_init_interface() was inverting the F-bit for
NTSC case, in the CCIR_CODE_1/2 registers. The result being that
for NTSC bottom-top field order, the CSI would swap fields and
capture in top-bottom order.
Instead, base field swap on the field order of the input to the CSI,
and th
If IDMAC interweaving is enabled in a write channel, the channel must
write the odd chroma rows for 4:2:0 formats. Skipping writing the odd
chroma rows produces corrupted captured 4:2:0 images when interweave
is enabled.
Reported-by: Krzysztof Hałasa
Signed-off-by: Steve Longerbeam
Reviewed-by:
prepare_vdi_in_buffers() was setting up the dma pointers as if the
VDIC is always programmed to receive the fields in bottom-top order,
i.e. as if ipu_vdi_set_field_order() only programs BT order in the VDIC.
But that's not true, ipu_vdi_set_field_order() is working correctly.
So fix prepare_vdi_i
Allow sequential->interlaced interweaving but with top/bottom
lines swapped to the output buffer.
This can be accomplished by adding one line length to IDMAC output
channel address, with a negative line length for the interlace offset.
This is to allow the seq-bt -> interlaced-bt transformation,
Also add an example pipeline for unconverted capture with interweave
on SabreAuto.
Cleanup some language in various places in the process.
Signed-off-by: Steve Longerbeam
Reviewed-by: Philipp Zabel
---
Changes since v4:
- Make clear that it is IDMAC channel that does pixel reordering and
inte
A set of patches that fixes some bugs with capturing from an
interlaced source, and incompatibilites between IDMAC interlace
interweaving and 4:2:0 data write reduction.
History:
v8:
- Add some missing sign-offs. No functional changes.
v7:
- Remove regression-fix patch "media: imx-csi: Input conn
If caller passes un-initialized field type V4L2_FIELD_ANY to CSI
sink pad, the reset CSI crop window would not be correct, because
the crop window depends on a valid input field type. To fix move
the reset of crop and compose windows to after the call to
imx_media_fill_default_mbus_fields().
Signe
Adds two helper macros:
V4L2_FIELD_IS_SEQUENTIAL: returns true if the given field type is
'sequential', that is a full frame is transmitted, or exists in
memory, as all top field lines followed by all bottom field lines,
or vice-versa.
V4L2_FIELD_IS_INTERLACED: returns true if the given field typ
IDMAC interlaced scan, a.k.a. interweave, should be enabled in the
IDMAC output channels only if the IDMAC output pad field type is
'seq-bt' or 'seq-tb', and field type at the capture interface is
'interlaced*'.
V4L2_FIELD_HAS_BOTH() macro should not be used on the input to determine
enabling inte
Hi Raj,
On Wed, Jan 09, 2019 at 06:01:39PM +, Mani, Rajmohan wrote:
> Hi Jacopo,
>
> > Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
> >
> > Hello Raj,
> >
> > On Wed, Jan 09, 2019 at 05:00:21PM +, Mani, Rajmohan wrote:
> > > Hi Laurent, Tomasz, Jacopo,
> > >
> > > > Subject: Re:
Le mercredi 09 janvier 2019 à 15:28 -0200, Mauro Carvalho Chehab a
écrit :
> Em Wed, 09 Jan 2019 11:52:45 -0500
> Nicolas Dufresne escreveu:
>
> > Le jeudi 10 janvier 2019 à 00:42 +0800, Ayaka a écrit :
> > > > There is a UVC media device that supports P010 device. We're discussing
> > > > about
Also add an example pipeline for unconverted capture with interweave
on SabreAuto.
Cleanup some language in various places in the process.
Signed-off-by: Steve Longerbeam
---
Changes since v4:
- Make clear that it is IDMAC channel that does pixel reordering and
interweave, not the CSI. Caught
Adds two helper macros:
V4L2_FIELD_IS_SEQUENTIAL: returns true if the given field type is
'sequential', that is a full frame is transmitted, or exists in
memory, as all top field lines followed by all bottom field lines,
or vice-versa.
V4L2_FIELD_IS_INTERLACED: returns true if the given field typ
The function ipu_csi_init_interface() was inverting the F-bit for
NTSC case, in the CCIR_CODE_1/2 registers. The result being that
for NTSC bottom-top field order, the CSI would swap fields and
capture in top-bottom order.
Instead, base field swap on the field order of the input to the CSI,
and th
Hi Pavel,
On Sat, Dec 22, 2018 at 08:29:34PM +0100, Pavel Machek wrote:
> On Fri 2018-12-21 02:17:48, Sebastian Reichel wrote:
> > From: Sebastian Reichel
> >
> > Remove unused return code from fmc_prepare() and fmc_release() to
> > simplify the code a bit.
>
>
> > /*
> > * This function wi
If caller passes un-initialized field type V4L2_FIELD_ANY to CSI
sink pad, the reset CSI crop window would not be correct, because
the crop window depends on a valid input field type. To fix move
the reset of crop and compose windows to after the call to
imx_media_fill_default_mbus_fields().
Signe
prepare_vdi_in_buffers() was setting up the dma pointers as if the
VDIC is always programmed to receive the fields in bottom-top order,
i.e. as if ipu_vdi_set_field_order() only programs BT order in the VDIC.
But that's not true, ipu_vdi_set_field_order() is working correctly.
So fix prepare_vdi_i
To support interlaced scan with planar formats, cpmem SLUV must
be programmed with the correct chroma line stride. For full and
partial planar 4:2:2 (YUV422P, NV16), chroma line stride must
be doubled. For full and partial planar 4:2:0 (YUV420, YVU420, NV12),
chroma line stride must _not_ be double
If IDMAC interweaving is enabled in a write channel, the channel must
write the odd chroma rows for 4:2:0 formats. Skipping writing the odd
chroma rows produces corrupted captured 4:2:0 images when interweave
is enabled.
Reported-by: Krzysztof Hałasa
Signed-off-by: Steve Longerbeam
Reviewed-by:
If the incoming sink field type is alternate, the reset crop height
and crop height bounds must be set to twice the incoming height,
because in alternate field mode, upstream will report only the
lines for a single field, and the CSI captures the whole frame.
Signed-off-by: Steve Longerbeam
Revie
IDMAC interlaced scan, a.k.a. interweave, should be enabled in the
IDMAC output channels only if the IDMAC output pad field type is
'seq-bt' or 'seq-tb', and field type at the capture interface is
'interlaced*'.
V4L2_FIELD_HAS_BOTH() macro should not be used on the input to determine
enabling inte
Skip writing U/V components to odd rows for YVU420 in addition to
YUV420 and NV12.
Signed-off-by: Steve Longerbeam
Reviewed-by: Philipp Zabel
---
drivers/staging/media/imx/imx-media-csi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/media/imx/imx-media-csi.c
b/drivers/st
Allow sequential->interlaced interweaving but with top/bottom
lines swapped to the output buffer.
This can be accomplished by adding one line length to IDMAC output
channel address, with a negative line length for the interlace offset.
This is to allow the seq-bt -> interlaced-bt transformation,
A set of patches that fixes some bugs with capturing from an
interlaced source, and incompatibilites between IDMAC interlace
interweaving and 4:2:0 data write reduction.
History:
v7:
- Remove regression-fix patch "media: imx-csi: Input connections to CSI
should be optional" which will be submitt
Hi Marcel,
First of all thanks for your review.
On Sun, Dec 23, 2018 at 04:56:47PM +0100, Marcel Holtmann wrote:
> Hi Sebastian,
[...]
> > +static int ll_register_fm(struct ll_device *lldev)
> > +{
> > + struct device *dev = &lldev->serdev->dev;
> > + int err;
> > +
> > + if (!of_device_i
Hi Jacopo,
> Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
>
> Hello Raj,
>
> On Wed, Jan 09, 2019 at 05:00:21PM +, Mani, Rajmohan wrote:
> > Hi Laurent, Tomasz, Jacopo,
> >
> > > Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
> > >
> > > Hello,
> > >
> > > On Tue, Jan 08, 2
On 12/29/18 7:51 PM, Brad Love wrote:
Check error status bit on command execute, if error bit is
set return -EAGAIN. Ignore -EAGAIN in probe during device check.
Signed-off-by: Brad Love
---
drivers/media/tuners/si2157.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
dif
This commit corrects max and step values for v4l2 control for
V4L2_CID_JPEG_RESTART_INTERVAL. Max should be 0x and step should be 1.
It was found by using v4l2-compliance tool and checking result of
VIDIOC_QUERY_EXT_CTRL/QUERYMENU test.
Previously it was complaining that step was bigger than di
On 12/20/18 11:57 PM, Brad Love wrote:
Works in ATSC and QAM as is, DVB is completely untested.
Firmware required.
Signed-off-by: Brad Love
---
drivers/media/tuners/si2157.c | 6 ++
drivers/media/tuners/si2157_priv.h | 3 ++-
#define SI2158_A20_FIRMWARE "dvb-tuner-si2158-a20-0
Em Wed, 09 Jan 2019 11:52:45 -0500
Nicolas Dufresne escreveu:
> Le jeudi 10 janvier 2019 à 00:42 +0800, Ayaka a écrit :
> > > There is a UVC media device that supports P010 device. We're discussing
> > > about adding support for it on media. The full thread is at:
> > >
> > > https://lore.kernel
On 1/9/19 3:13 AM, Philipp Zabel wrote:
On Tue, 2019-01-08 at 16:15 -0800, Steve Longerbeam wrote:
Some imx platforms do not have fwnode connections to all CSI input
ports, and should not be treated as an error. This includes the
imx6q SabreAuto, which has no connections to ipu1_csi1 and ipu2
Hello Raj,
On Wed, Jan 09, 2019 at 05:00:21PM +, Mani, Rajmohan wrote:
> Hi Laurent, Tomasz, Jacopo,
>
> > -Original Message-
> > From: Jacopo Mondi [mailto:jac...@jmondi.org]
> > Sent: Wednesday, January 09, 2019 8:41 AM
> > To: Tomasz Figa
> > Cc: Zhi, Yong ; Mani, Rajmohan
> > ; Qi
Hi Laurent, Tomasz, Jacopo,
> -Original Message-
> From: Jacopo Mondi [mailto:jac...@jmondi.org]
> Sent: Wednesday, January 09, 2019 8:41 AM
> To: Tomasz Figa
> Cc: Zhi, Yong ; Mani, Rajmohan
> ; Qiu, Tian Shu ; Cao,
> Bingbu ; Laurent Pinchart
> ; Linux Media Mailing List me...@vger.ker
Le jeudi 10 janvier 2019 à 00:42 +0800, Ayaka a écrit :
> > There is a UVC media device that supports P010 device. We're discussing
> > about adding support for it on media. The full thread is at:
> >
> > https://lore.kernel.org/linux-media/20190109121900.hbrpttmxz3gao...@valkosipuli.retiisi.org.u
Sent from my iPad
> On Jan 9, 2019, at 9:01 PM, Mauro Carvalho Chehab
> wrote:
>
> Em Wed, 9 Jan 2019 14:19:00 +0200
> Sakari Ailus escreveu:
>
>>> On Tue, Jan 08, 2019 at 04:49:16PM -0200, Mauro Carvalho Chehab wrote:
>>> Em Tue, 8 Jan 2019 21:11:41 +0500
>>> Mikhail Gavrilov escreveu:
>
Hello,
On Tue, Jan 08, 2019 at 03:54:34PM +0900, Tomasz Figa wrote:
> Hi Raj, Yong, Bingbu, Tianshu,
>
> On Fri, Dec 21, 2018 at 12:04 PM Tomasz Figa wrote:
> >
> > On Fri, Dec 21, 2018 at 7:24 AM Laurent Pinchart
> > wrote:
> > >
> > > Hellon
> > >
> > > On Sunday, 16 December 2018 09:26:18 EET
On 01/09/19 15:42, Paul Kocialkowski wrote:
> Hi,
>
> On Wed, 2019-01-09 at 15:29 +0100, Hans Verkuil wrote:
>> On 01/09/19 15:19, Paul Kocialkowski wrote:
>>> It was reported that some cases of interleaved video decoding require
>>> using the current destination buffer as a reference. However, th
Remove remaining soc_camera specific code and drop soc_camera dependency
from this driver.
Cc: Guennadi Liakhovetski
Cc: Sakari Ailus
Cc: Mauro Carvalho Chehab
Signed-off-by: Akinobu Mita
---
* v2.1
- Fix misconversion while opencoding soc_camera_limit_side().
drivers/media/i2c/Kconfig |
Hi,
On Wed, 2019-01-09 at 15:29 +0100, Hans Verkuil wrote:
> On 01/09/19 15:19, Paul Kocialkowski wrote:
> > It was reported that some cases of interleaved video decoding require
> > using the current destination buffer as a reference. However, this is
> > no longer possible after the move to vb2_
On 01/09/19 15:19, Paul Kocialkowski wrote:
> It was reported that some cases of interleaved video decoding require
> using the current destination buffer as a reference. However, this is
> no longer possible after the move to vb2_find_timestamp because only
> dequeued and done buffers are consider
It was reported that some cases of interleaved video decoding require
using the current destination buffer as a reference. However, this is
no longer possible after the move to vb2_find_timestamp because only
dequeued and done buffers are considered.
Add a helper in our driver that also considers
Some leftover declarations are still in the cedrus_dec header although
they were moved to cedrus_video already. Clean them up.
Signed-off-by: Paul Kocialkowski
---
drivers/staging/media/sunxi/cedrus/cedrus_dec.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/staging/media/sunxi
Hi Jacopo,
One more comment below:
On 07/01/2019 12:36, Kieran Bingham wrote:
> Hi Jacopo,
>
> On 06/01/2019 15:54, Jacopo Mondi wrote:
>> When the adv748x driver is informed about a link being created from HDMI or
>> AFE to a CSI-2 TX output, the 'link_setup()' callback is invoked. Make
>> sure
On 09/01/2019 00:15, Laurent Pinchart wrote:
> Hello,
>
> On Monday, 7 January 2019 14:36:28 EET Kieran Bingham wrote:
>> On 06/01/2019 15:54, Jacopo Mondi wrote:
>>> When the adv748x driver is informed about a link being created from HDMI
>>> or AFE to a CSI-2 TX output, the 'link_setup()' callba
On 01/03/19 05:33, Hans Verkuil wrote:
> This message is generated daily by a cron job that builds media_tree for
> the kernels and architectures in the list below.
Sorry, the mail from the cron job stopped working. It should be fixed now.
I also (hopefully) fixed compilation failures after the m
Hi Mita-san,
On Wed, Jan 09, 2019 at 12:40:33AM +0900, Akinobu Mita wrote:
> 2019年1月8日(火) 23:52 Akinobu Mita :
> >
> > Remove remaining soc_camera specific code and drop soc_camera dependency
> > from this driver.
> >
> > Cc: Guennadi Liakhovetski
> > Cc: Sakari Ailus
> > Cc: Mauro Carvalho Cheh
Hi Mauro,
On Wed, Jan 09, 2019 at 10:13:42AM -0200, Mauro Carvalho Chehab wrote:
> Em Tue, 08 Jan 2019 18:05:57 +0200
> Laurent Pinchart escreveu:
>
> > On Tuesday, 8 January 2019 16:30:22 EET Mauro Carvalho Chehab wrote:
> > > Em Tue, 8 Jan 2019 15:40:47 +0200
> > >
> > > Sakari Ailus escreve
On 19.10.2018 15:52, Luis Oliveira wrote:
> Add the Synopsys MIPI CSI-2 controller driver. This
> controller driver is divided in platform dependent functions
> and core functions. It also includes a platform for future
> DesignWare drivers.
>
> Signed-off-by: Luis Oliveira
> ---
> Changelog
>
Em Wed, 9 Jan 2019 14:19:00 +0200
Sakari Ailus escreveu:
> On Tue, Jan 08, 2019 at 04:49:16PM -0200, Mauro Carvalho Chehab wrote:
> > Em Tue, 8 Jan 2019 21:11:41 +0500
> > Mikhail Gavrilov escreveu:
> >
> > > On Tue, 8 Jan 2019 at 20:57, Laurent Pinchart
> > > wrote:
> > > >
> > > > Thank
On Wed, Jan 09, 2019 at 10:33:25AM +0100, Maxime Ripard wrote:
> Cadence has designed a D-PHY that can be used by the, currently in tree,
> DSI bridge (DRM), CSI Transceiver and CSI Receiver (v4l2) drivers.
>
> Only the DSI driver has an ad-hoc driver for that phy at the moment, while
> the v4l2 d
Hi Maxime,
On Wed, Jan 09, 2019 at 10:33:24AM +0100, Maxime Ripard wrote:
> The Cadence D-PHY bindings was defined as part of the DSI block so far.
> However, since it's now going to be a separate driver, we need to move the
> binding to a file of its own.
>
> Signed-off-by: Maxime Ripard
Revie
On Wed, Jan 09, 2019 at 10:33:17AM +0100, Maxime Ripard wrote:
> Hi,
>
> Here is a set of patches to allow the phy framework consumers to test and
> apply runtime configurations.
>
> This is needed to support more phy classes that require tuning based on
> parameters depending on the current use
On Tue, Jan 08, 2019 at 04:49:16PM -0200, Mauro Carvalho Chehab wrote:
> Em Tue, 8 Jan 2019 21:11:41 +0500
> Mikhail Gavrilov escreveu:
>
> > On Tue, 8 Jan 2019 at 20:57, Laurent Pinchart
> > wrote:
> > >
> > > Thank you.
> > >
> > > Your device exposes five formats: YUY2 (YUYV), YV12 (YVU420),
Em Tue, 08 Jan 2019 18:05:57 +0200
Laurent Pinchart escreveu:
> On Tuesday, 8 January 2019 16:30:22 EET Mauro Carvalho Chehab wrote:
> > Em Tue, 8 Jan 2019 15:40:47 +0200
> >
> > Sakari Ailus escreveu:
> > > On Tue, Jan 08, 2019 at 10:59:55AM -0200, Mauro Carvalho Chehab wrote:
> > > > Em T
Em Wed, 9 Jan 2019 08:51:29 +0500
Mikhail Gavrilov escreveu:
> I upgraded kernel to 5.0 rc1 and the error message "Unknown
> pixelformat 0x" are disappeared.
>
> Instead I see not obvious message "uvcvideo: Non-zero status (-71) in
> video completion handler."
This is unrelated. Usuall
This remote has a small joystick which acts like a mouse. Support
decoding this.
Signed-off-by: Sean Young
---
utils/keytable/bpf_protocols/Makefile.am | 2 +-
utils/keytable/bpf_protocols/bpf_helpers.h| 192 +++---
utils/keytable/bpf_protocols/imon_rsc.c | 156 +
Hi Vishal,
Please see my comments below.
On Wed, May 30, 2018 at 12:24:44AM +0530, Vishal Sagar wrote:
> The Xilinx MIPI CSI-2 Rx Subsystem soft IP is used to capture images
> from MIPI CSI-2 camera sensors and output AXI4-Stream video data ready
> for image processing.
>
> It supports upto 4 la
We see your photos photos for editing.
Please send us the details of this task.
Do your photos need cut out? Or clipping path, and retouching?
You may give us 1 photo, we will do test for you to check the quality.
Thanks,
Helen
Add device-tree bindings for the Allegro DVT video IP core found on the
Xilinx ZynqMP EV family.
Signed-off-by: Michael Tretter
---
.../devicetree/bindings/media/allegro.txt | 35 +++
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media
This series adds support for the Allegro DVT H.264 encoder found in the EV
family of the Xilinx ZynqMP platform.
The encoder is part of the ZynqMP VCU (video codec unit), which supports
encoding and decoding of H.264 and H.265. I am planning to support decoding
and H.265 as well in this driver.
T
Add a V4L2 mem-to-mem driver for Allegro DVT video IP cores as found in
the EV family of the Xilinx ZynqMP SoC. The Zynq UltraScale+ Device
Technical Reference Manual uses the term VCU (Video Codec Unit) for the
encoder, decoder and system integration block.
This driver takes care of interacting w
The allegro hardware encoder does not write SPS/PPS nal units into the
encoded video stream. Therefore, we need to write the units in software.
The implementation follows Rec. ITU-T H.264 (04/2017) to allow to
convert between a C struct and the RBSP representation of the SPS and
PPS nal units.
Th
Because it looks neater.
Signed-off-by: Peter Rosin
---
drivers/media/common/saa7146/saa7146_i2c.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/media/common/saa7146/saa7146_i2c.c
b/drivers/media/common/saa7146/saa7146_i2c.c
index 3feddc52c446..df9ebe2a168c 100
Hi Patrick,
On Sat, Dec 08, 2018 at 02:18:05AM +0100, Patrick Lerda wrote:
> media: add support for RCMM infrared remote controls.
>
> Signed-off-by: Patrick Lerda
Sorry about the delay in getting this reviewed. December was a very
busy month for me.
> ---
> MAINTAINERS
On Tue, 2019-01-08 at 16:15 -0800, Steve Longerbeam wrote:
> Also add an example pipeline for unconverted capture with interweave
> on SabreAuto.
>
> Cleanup some language in various places in the process.
>
> Signed-off-by: Steve Longerbeam
Reviewed-by: Philipp Zabel
regards
Philipp
On Tue, 2019-01-08 at 16:15 -0800, Steve Longerbeam wrote:
> Some imx platforms do not have fwnode connections to all CSI input
> ports, and should not be treated as an error. This includes the
> imx6q SabreAuto, which has no connections to ipu1_csi1 and ipu2_csi0.
> Return -ENOTCONN in imx_csi_par
On Tue, 2019-01-08 at 16:15 -0800, Steve Longerbeam wrote:
> The function ipu_csi_init_interface() was inverting the F-bit for
> NTSC case, in the CCIR_CODE_1/2 registers. The result being that
> for NTSC bottom-top field order, the CSI would swap fields and
> capture in top-bottom order.
>
> Inst
The CSI, PRP ENC, and PRP VF subdevices shouldn't have to care about
IDMAC line start address alignment. With compose rectangle support in
the capture driver, they don't have to anymore.
If the direct CSI -> IC path is enabled, the CSI output width must
still be aligned to 8 pixels (IC burst length
Allowing to compose captured images into larger memory buffers
will let us lift alignment restrictions on CSI crop width.
Signed-off-by: Philipp Zabel
Acked-by: Sakari Ailus
---
Changes since v1:
- remove NATIVE_SIZE selection target
- fixed typo in capture_s_fmt_vid_cap
---
drivers/staging/m
Prepare for mbus format being smaller than the written rectangle
due to burst size.
Signed-off-by: Philipp Zabel
---
Changes since v1:
- Typo fixups, this time applied to the correct patch.
---
drivers/staging/media/imx/imx-media-capture.c | 56 +--
1 file changed, 38 insertions
Hi,
Here is a set of patches to allow the phy framework consumers to test and
apply runtime configurations.
This is needed to support more phy classes that require tuning based on
parameters depending on the current use case of the device, in addition to
the power state management already provide
1 - 100 of 117 matches
Mail list logo
