On Tue, Oct 15, 2019 at 12:58 PM Biju Das wrote:
> Document support for the VIN module in the Renesas RZ/G2N (R8A774B1) SoC.
>
> Signed-off-by: Biju Das
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia3
On Tue, Oct 15, 2019 at 12:58 PM Biju Das wrote:
> Add the MIPI CSI-2 driver support for RZ/G2N(R8A774B1) SoC.
> The CSI-2 module of RZ/G2N is similar to R-Car M3-N.
>
> Signed-off-by: Biju Das
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterh
On Tue, Oct 15, 2019 at 12:58 PM Biju Das wrote:
> Add the SoC specific information for RZ/G2N(R8A774B1) SoC.
> The VIN module of RZ/G2N is similar to R-Car M3-N.
>
> Signed-off-by: Biju Das
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoev
On Tue, Oct 15, 2019 at 12:58 PM Biju Das wrote:
> Add the compatible string for RZ/G2N (R8A774B1) to the list of supported
> SoCs.
>
> Signed-off-by: Biju Das
Reviewed-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux bey
Hi Mauro,
The following changes since commit 3ff3a712a9eabb3d7bf52c263dd1ece054345df4:
media: ti-vpe: vpe: don't rely on colorspace member for conversion
(2019-10-10 13:54:22 -0300)
are available in the Git repository at:
git://linuxtv.org/pinchartl/media.git tags/v4l2-next-20191016
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59497/
Build log: https://builder.linuxtv.org/job/patchwork/20659/
Build time: 00:03:57
Link:
https://lore.kernel.org/linux-media/20191016095738.gb5...@pendragon.ideasonboard.com
gpg: Signature made Wed 16 Oct 2019 09:56
This series adds vivid metadata capture and output support. While working on
that it was discovered that the v4l2 core didn't correctly validate the ioctls
in the case of the vivid driver that has a complex mix of V4L2 devices and
various video inputs, each with different properties.
Some other cl
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59498/
Build log: https://builder.linuxtv.org/job/patchwork/20663/
Build time: 00:13:22
Link:
https://lore.kernel.org/linux-media/5364cdbc-ccea-addd-3849-c4f9e2602...@xs4all.nl
gpg: Signature made Wed 16 Oct 2019 10:27:3
This series adds support for H.264 slicing to the cedrus driver. This is done by
adding a new buffer flag V4L2_BUF_FLAG_M2M_HOLD_CAPTURE_BUF that stateless
decoders
have to set when queueing the output buffer to indicate that this output buffer
contains a compressed slice and so the capture buffer
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59500/
Build log: https://builder.linuxtv.org/job/patchwork/20670/
Build time: 00:14:23
Link:
https://lore.kernel.org/linux-media/02bfac01-d6ba-1eca-efc6-1dbfcc712...@xs4all.nl
gpg: Signature made Wed 16 Oct 2019 11:31:2
On 10/16/19 12:34 AM, Jules Irenge wrote:
> Fix "alignment should mactch open parenthesis" check.
> Issue detected by checkpatch tool
>
> Signed-off-by: Jules Irenge
> ---
> drivers/staging/media/meson/vdec/codec_mpeg12.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/
The following changes since commit 3ff3a712a9eabb3d7bf52c263dd1ece054345df4:
media: ti-vpe: vpe: don't rely on colorspace member for conversion
(2019-10-10 13:54:22 -0300)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.5k
for you to fetch chang
Hi Steve,
On Tue, Oct 15, 2019 at 10:18 PM Steve Longerbeam wrote:
> Here's a quick example that uses the end-of-frame method to measure fi's
> (all other FIM controls are left at the default values):
>
> v4l2-ctl -d0 --set-ctrl=fim_enable=1
> # disable input capture method
> v4l2-ctl -d0 --set-
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59501/
Build log: https://builder.linuxtv.org/job/patchwork/20678/
Build time: 00:09:21
Link:
https://lore.kernel.org/linux-media/cb6f7dfe-8e7c-5fa9-e287-22daa356b...@xs4all.nl
gpg: Signature made Wed 16 Oct 2019 12:57:4
Hi,
I thought I had answered here already, but looks I never sent the email.
On Sat 05 Oct 19, 23:21, Tomasz Figa wrote:
> On Sat, Oct 5, 2019 at 11:12 PM Paul Kocialkowski
> wrote:
> >
> > On Sat 05 Oct 19, 22:54, Tomasz Figa wrote:
> > > On Sat, Oct 5, 2019 at 10:39 PM Paul Kocialkowski
> > >
On 10/15/19 4:35 PM, Niklas Söderlund wrote:
> Add a video device capability flag to indicate that its inputs and/or
> outputs are controlled by the Media Controller instead of the V4L2 API.
> When this flag is set, ioctls for get, set and enum inputs and outputs
> are automatically enabled and pro
On Wed, 2019-10-16 at 15:37 +0200, Paul Kocialkowski wrote:
[...]
> > > The bottomline is that we have use cases for each of the two set of fields
> > > independently, so I feel like this is reason enough to avoid mixing them
> > > together.
> >
> > What do you mean by mixing together? Hardware pa
The touch timer is set up in intf1. If the second interface does not exist,
the timer and touch input device are not setup and we get the following
error, when touch events are reported via intf0.
Reported-by: syzbot+f49d12d34f2321cf4...@syzkaller.appspotmail.com
Signed-off-by: Sean Young
---
dr
On 10/16/19 6:04 AM, Fabio Estevam wrote:
Hi Steve,
On Tue, Oct 15, 2019 at 10:18 PM Steve Longerbeam wrote:
Here's a quick example that uses the end-of-frame method to measure fi's
(all other FIM controls are left at the default values):
v4l2-ctl -d0 --set-ctrl=fim_enable=1
# disable inp
On Wed, Oct 16, 2019 at 2:31 PM Steve Longerbeam wrote:
> If /dev/video2 is the "ipu1_ic_prpvf capture" node, it's because FIM is
> not yet available on those nodes. The FIM is only available on the
> "ipuX_csiY capture" nodes. It's on my plate to fix that.
On a 5.3.6 kernel on imx6dl-sabreauto:
On 10/16/19 11:54 AM, Fabio Estevam wrote:
On Wed, Oct 16, 2019 at 2:31 PM Steve Longerbeam wrote:
If /dev/video2 is the "ipu1_ic_prpvf capture" node, it's because FIM is
not yet available on those nodes. The FIM is only available on the
"ipuX_csiY capture" nodes. It's on my plate to fix th
Em Fri, 4 Oct 2019 13:59:00 +0200
Hans Verkuil escreveu:
> On 10/4/19 1:55 PM, Vandana BN wrote:
> > Adds new file for describing new metadata format V4L2_META_FMT_VIVID added
> > in vivid driver.
> >
> > Signed-off-by: Vandana BN
> > ---
> > Documentation/media/uapi/v4l/meta-formats.rst | 1
Hi Steve,
On Wed, Oct 16, 2019 at 4:11 PM Steve Longerbeam wrote:
> FIM is available on the above nodes (/dev/video0 and /dev/video3), after
> enabling links to them. So please try:
>
> # media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
> # v4l2-ctl -d0 --list-ctrls
>
> # media-ctl -l "
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 Oct 17 05:00:11 CEST 2019
media-tree git hash:4b1d7c2760d26363c497b959a81f8d055ba767c1
media_build gi
tree/branch: git://linuxtv.org/media_tree.git media-tree
branch HEAD: 4b1d7c2760d26363c497b959a81f8d055ba767c1 media: staging: media:
Make use of devm_platform_ioremap_resource
elapsed time: 579m
configs tested: 113
The following configs have been built successfully.
More configs may be teste
Vandana,
Can you post a v3 with this proposed license?
Thanks!
Hans
On 10/16/19 9:45 PM, Mauro Carvalho Chehab wrote:
> Em Fri, 4 Oct 2019 13:59:00 +0200
> Hans Verkuil escreveu:
>
>> On 10/4/19 1:55 PM, Vandana BN wrote:
>>> Adds new file for describing new metadata format V4L2_META_
On Fri, Oct 11, 2019 at 5:54 PM Dmitry Morozov
wrote:
>
> Hi Tomasz,
>
> On Mittwoch, 9. Oktober 2019 05:55:45 CEST Tomasz Figa wrote:
> > On Tue, Oct 8, 2019 at 12:09 AM Dmitry Morozov
> >
> > wrote:
> > > Hi Tomasz,
> > >
> > > On Montag, 7. Oktober 2019 16:14:13 CEST Tomasz Figa wrote:
> > > >
Adds new file for describing new metadata format V4L2_META_FMT_VIVID added in
vivid driver.
Signed-off-by: Vandana BN
---
Change in V3 - modified pixfmt-meta-vivid.rst to have dual GFDL and GPL license.
---
Documentation/media/uapi/v4l/meta-formats.rst | 1 +
.../media/uapi/v4l/pixfmt-meta-viv
This series adds vivid metadata capture and output support. While working on
that it was discovered that the v4l2 core didn't correctly validate the ioctls
in the case of the vivid driver that has a complex mix of V4L2 devices and
various video inputs, each with different properties.
Some other cl
On Mon, Oct 14, 2019 at 9:19 PM Gerd Hoffmann wrote:
>
> > > Well. I think before even discussing the protocol details we need a
> > > reasonable plan for buffer handling. I think using virtio-gpu buffers
> > > should be an optional optimization and not a requirement. Also the
> > > motivation
30 matches
Mail list logo
