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 Jan 19 05:00:12 CET 2019
media-tree git hash:e8f9b16d72631870e30a3d8e4ee9f1c097bc7ba0
media_build git
Want to shoot photos for your products and retouching also i needed?
We are studio special for photo shooting and retouching.
For your photos:
White background, Optimized for Shopify, Retouching included
Revisions accepted
We can also give you dedicate editing service for your photos
Let me kn
Want to shoot photos for your products and retouching also i needed?
We are studio special for photo shooting and retouching.
For your photos:
White background, Optimized for Shopify, Retouching included
Revisions accepted
We can also give you dedicate editing service for your photos
Let me kn
Want to shoot photos for your products and retouching also i needed?
We are studio special for photo shooting and retouching.
For your photos:
White background, Optimized for Shopify, Retouching included
Revisions accepted
We can also give you dedicate editing service for your photos
Let me kn
Want to shoot photos for your products and retouching also i needed?
We are studio special for photo shooting and retouching.
For your photos:
White background, Optimized for Shopify, Retouching included
Revisions accepted
We can also give you dedicate editing service for your photos
Let me kn
Repeatedly sending a stream off immediately followed by stream on can
eventually cause a complete system hard lockup on the SabreAuto when
streaming from the ADV7180:
while true; do v4l2-ctl -d4 --stream-mmap --stream-count=3; done
Eventually this either causes the system lockup or EOF timeouts
Upstream must be stopped immediately after receiving the last EOF and
before disabling the IDMA channel. This can be accomplished by moving
upstream stream off to just after receiving the last EOF completion in
prp_stop(). For symmetry also move upstream stream on to end of
prp_start().
This fixes
Disable the SMFC before disabling the IDMA channel, instead of after,
in csi_idmac_unsetup().
This fixes a complete system hard lockup on the SabreAuto when streaming
from the ADV7180, by repeatedly sending a stream off immediately followed
by stream on:
while true; do v4l2-ctl -d4 --stream-mmap
On 1/18/19 2:54 PM, shuah wrote:
On 1/18/19 1:36 AM, Hans Verkuil wrote:
On 12/18/18 6:59 PM, sh...@kernel.org wrote:
From: Shuah Khan
Media Device Allocator API to allows multiple drivers share a media
device.
This API solves a very common use-case for media devices where one
physical
devi
On 1/18/19 11:01 AM, Steve Longerbeam wrote:
On 1/18/19 2:24 AM, Philipp Zabel wrote:
On Thu, 2019-01-17 at 12:49 -0800, Steve Longerbeam wrote:
Disable the CSI immediately after receiving the last EOF before stream
off (and thus before disabling the IDMA channel).
This fixes a complete s
It is hard to say what KEY_SCREEN and KEY_ZOOM mean, but historically DVB
folks have used them to indicate switch to full screen mode. Later, they
converged on using KEY_ZOOM to switch into full screen mode and KEY)SCREEN
to control aspect ratio (see Documentation/media/uapi/rc/rc-tables.rst).
Let
We defined better names for keys to activate full screen mode or
change aspect ratio (while keeping the existing keycodes to avoid
breaking userspace), so let's use them in the document.
Signed-off-by: Dmitry Torokhov
---
Documentation/media/uapi/rc/rc-tables.rst | 4 ++--
1 file changed, 2 inse
On 1/18/19 1:36 AM, Hans Verkuil wrote:
On 12/18/18 6:59 PM, sh...@kernel.org wrote:
From: Shuah Khan
Media Device Allocator API to allows multiple drivers share a media device.
This API solves a very common use-case for media devices where one physical
device (an USB stick) provides both audi
The pull request you sent on Fri, 18 Jan 2019 15:40:58 -0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
> tags/media/v5.0-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2339e91d0e6609e17943a0ab3c3c8c4044760c05
Thank you!
--
Deet-doot-dot
Hi Peter,
Thanks for the suggestion. My patch introduces some inconsistency in the
code, and your solution fixes those issues and is much simpler. It seems
the fix is to silence the video data stream entering the IDMAC channel
before disabling the channel, and that can be done either by disabl
On 1/18/19 2:24 AM, Philipp Zabel wrote:
On Thu, 2019-01-17 at 12:49 -0800, Steve Longerbeam wrote:
Disable the CSI immediately after receiving the last EOF before stream
off (and thus before disabling the IDMA channel).
This fixes a complete system hard lockup on the SabreAuto when streamin
Oi Fabio,
On Fri 18 Jan 2019 at 16:49, Fabio Estevam wrote:
Hi Rui,
On Fri, Dec 7, 2018 at 10:44 AM Hans Verkuil
wrote:
I got a few checkpatch warnings about coding style:
CHECK: Alignment should match open parenthesis
#953: FILE: drivers/staging/media/imx/imx7-media-csi.c:911:
+static str
On 1/17/19 8:15 PM, Lucas A. M. Magalhaes wrote:
> Add a linear pipeline logic for the stream control. It's created by
> walking backwards on the entity graph. When the stream starts it will
> simply loop through the pipeline calling the respective process_frame
> function of each entity.
>
> F
> -Original Message-
> From: eugen.hris...@microchip.com
> Sent: Friday, January 18, 2019 9:40 AM
> To: Ken Sloat
> Cc: mche...@kernel.org; nicolas.fe...@microchip.com;
> alexandre.bell...@bootlin.com; ludovic.desroc...@microchip.com; linux-
> me...@vger.kernel.org; devicet...@vger.kernel
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v5.0-1
for:
- A regression fix at v4l2 core, with affects multi-plane streams;
- a fix at vim2m driver.
Thanks!
Mauro
The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313
Hello Steve,
On Thu, Jan 17, 2019 at 6:15 PM Steve Longerbeam wrote:
>
> Disable the CSI immediately after receiving the last EOF before stream
> off (and thus before disabling the IDMA channel).
>
> This fixes a complete system hard lockup on the SabreAuto when streaming
> from the ADV7180, by r
On Fri, 2019-01-18 at 12:18 +0100, Philipp Zabel wrote:
> Hi Hans,
>
> On Fri, 2019-01-18 at 10:30 +0100, Hans Verkuil wrote:
> > On 1/17/19 4:50 PM, Philipp Zabel wrote:
>
> [...]
> > > +
> > > +static const struct video_device ipu_csc_scaler_videodev_template = {
> > > + .name = "ipu0
Hi Rui,
On Fri, Dec 7, 2018 at 10:44 AM Hans Verkuil wrote:
> I got a few checkpatch warnings about coding style:
>
> CHECK: Alignment should match open parenthesis
> #953: FILE: drivers/staging/media/imx/imx7-media-csi.c:911:
> +static struct v4l2_mbus_framefmt *imx7_csi_get_format(struct imx7_
This is v6 set for previous version[1] series to support CSI on Allwinner A64.
Tested 640x480, 320x240, 720p, 1080p resolutions UYVY8_2X8 format.
Changes for v6:
- set the mod rate in seett_power instead of probe
Changes for v5:
- Add mod_rate quirk for better handling clk_set code
Changes for v4
Allwinner A64 CSI is a single channel time-multiplexed BT.656
protocol interface.
Add separate compatible string for A64 since it require explicit
change in sun6i_csi driver to update default CSI_SCLK rate.
Reviewed-by: Rob Herring
Signed-off-by: Jagan Teki
---
Documentation/devicetree/binding
Bananapi M64 comes with an optional sensor based on the ov5640,
add support for it with below pin information.
- PE13, PE12 via i2c-gpio bitbanging
- CLK_CSI_MCLK as external clock
- PE1 as external clock pin muxing
- DLDO3 as AVDD supply
- ALDO1 as DOVDD supply
- ELDO3 as DVDD supply
- PE16 gpio
Unfortunately default CSI_SCLK rate cannot work properly to
drive the connected sensor interface, particularly on few
Allwinner SoC's like A64.
So, add mod_rate quirk via driver data so-that the respective
SoC's which require to alter the default mod clock rate can assign
the operating clock rate.
CSI block in Allwinner A64 has similar features as like in H3,
but default mod clock rate in BSP along with latest mainline testing
require to operate it at 300MHz.
So, add A64 CSI compatibe along with mod_rate quirk.
Signed-off-by: Jagan Teki
---
drivers/media/platform/sunxi/sun6i-csi/sun6i_cs
Add dts node details for Allwinner A64 CSI controller.
A64 CSI has similar features as like in H3, but the CSI_SCLK
need to update it to 300MHz than default clock rate.
Signed-off-by: Jagan Teki
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 20 +++
1 file changed, 20 inser
Some camera modules have the SoC feeding a master clock to the sensor
instead of having a standalone crystal. This clock signal is generated
from the clock control unit and output from the CSI MCLK function of
pin PE1.
Add a pinmux setting for it for camera sensors to reference.
Signed-off-by: Ja
Hi Alex,
If you have time please review this patch, I'd like to send a pull
request for this series.
On 1/9/19 10:46 AM, Stanimir Varbanov wrote:
> By historical reasons we defined firmware memory size to be 6MB even
> that the firmware size for all supported Venus versions is 5MBs. Correct
> tha
Want to shoot photos for your products and retouching also i needed?
We are studio special for photo shooting and retouching.
For your photos:
White background, Optimized for Shopify, Retouching included
Revisions accepted
We can also give you dedicate editing service for your photos
Let me kn
This ixes an issue when setting the encoder framerate because of
missing precision. Now the frameinterval type is changed to
TYPE_CONTINUOUS and step = 1. Also the math is changed when
framerate property is called - the firmware side expects that
the framerate one is 1 << 16 units.
Signed-off-by:
On 18.01.2019 16:28, Ken Sloat wrote:
> From: Ken Sloat
>
> Update device tree binding documentation specifying how to
> enable BT656 with CRC decoding.
>
> Signed-off-by: Ken Sloat
> ---
> Changes in v2:
> -Use correct media "bus-type" dt property.
>
> Documentation/devicetree/bindi
Steve, all,
On 1/17/19 3:49 PM, Steve Longerbeam wrote:
The CSI must be disabled immediately after receiving the last EOF before
stream off (and thus before disabling the IDMA channel). This can be
accomplished by moving upstream stream off to just after receiving the
last EOF completion in prp_
Steeve, all,
On 1/17/19 3:49 PM, Steve Longerbeam wrote:
Disable the CSI immediately after receiving the last EOF before stream
off (and thus before disabling the IDMA channel).
This fixes a complete system hard lockup on the SabreAuto when streaming
from the ADV7180, by repeatedly sending a st
From: Ken Sloat
The ISC driver currently supports ITU-R 601 encoding which
utilizes the external hysync and vsync signals. ITU-R 656
format removes the need for these pins by embedding the
sync pulses within the data packet.
To support this feature, enable necessary register bits
when this featu
From: Ken Sloat
Update device tree binding documentation specifying how to
enable BT656 with CRC decoding.
Signed-off-by: Ken Sloat
---
Changes in v2:
-Use correct media "bus-type" dt property.
Documentation/devicetree/bindings/media/atmel-isc.txt | 5 +
1 file changed, 5 insertions(+)
On Fri, 2019-01-18 at 14:45 +0100, Hans Verkuil wrote:
> On 1/18/19 2:42 PM, Philipp Zabel wrote:
> > On Fri, 2019-01-18 at 13:41 +0100, Hans Verkuil wrote:
> > [...]
> > > > I can do that, but what would be the purpose of it showing up in the
> > > > media controller?
> > > > There is nothing to b
Hi Michael,
On 1/18/19 2:37 PM, Michael Tretter wrote:
> This is v2 of the series to add support for the Allegro DVT H.264 encoder
> found in the EV family of the Xilinx ZynqMP platform.
>
> See v1 [0] of the patch series for a description of the hardware.
>
> I fixed the handling of frames with
On 1/18/19 2:42 PM, Philipp Zabel wrote:
> On Fri, 2019-01-18 at 13:41 +0100, Hans Verkuil wrote:
> [...]
>>> I can do that, but what would be the purpose of it showing up in the
>>> media controller?
>>> There is nothing to be configured, no interaction with the rest of the
>>> graph, and the proc
On Fri, 2019-01-18 at 13:41 +0100, Hans Verkuil wrote:
[...]
> > I can do that, but what would be the purpose of it showing up in the
> > media controller?
> > There is nothing to be configured, no interaction with the rest of the
> > graph, and the processing subdevice wouldn't even correspond to
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
This is v2 of the series to add support for the Allegro DVT H.264 encoder
found in the EV family of the Xilinx ZynqMP platform.
See v1 [0] of the patch series for a description of the hardware.
I fixed the handling of frames with various sizes and driver is now able to
encode H.264 video in the b
Add device-tree bindings for the Allegro DVT video IP core found on the
Xilinx ZynqMP EV family.
Signed-off-by: Michael Tretter
---
Changes since v1:
none
---
.../devicetree/bindings/media/allegro.txt | 35 +++
1 file changed, 35 insertions(+)
create mode 100644 Documentati
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
Hi Hans,
On 18/01/2019 12:09, Hans Verkuil wrote:
> On 1/11/19 6:41 PM, Kieran Bingham wrote:
>> The ADV748x is currently reset by writting a small table of registers to
>> the device.
s/writting/writing/
>>
>> The table lacks documentation and contains magic values to perform the
>> actions, in
Two related fixes for the imx driver for 5.0 and stable for 4.13 and up.
Regards,
Hans
The following changes since commit e8f9b16d72631870e30a3d8e4ee9f1c097bc7ba0:
media: remove soc_camera ov9640 (2019-01-17 09:01:11 -0500)
are available in the Git repository at:
git://linuxtv.org
The following changes since commit e8f9b16d72631870e30a3d8e4ee9f1c097bc7ba0:
media: remove soc_camera ov9640 (2019-01-17 09:01:11 -0500)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.1g
for you to fetch changes up to 3a881781fe1ebd9f924aaabf89b
On 1/18/19 12:18 PM, Philipp Zabel wrote:
> Hi Hans,
>
> On Fri, 2019-01-18 at 10:30 +0100, Hans Verkuil wrote:
>> On 1/17/19 4:50 PM, Philipp Zabel wrote:
> [...]
>>> +
>>> +static const struct video_device ipu_csc_scaler_videodev_template = {
>>> + .name = "ipu0_ic_pp mem2mem",
>>
>>
Hi Kieran,
On Sat, Jan 12, 2019 at 04:50:32PM +, Kieran Bingham wrote:
> On 11/01/2019 20:15, Laurent Pinchart wrote:
> > On Friday, 11 January 2019 19:41:40 EET Kieran Bingham wrote:
> >> The ADV748x is currently reset by writting a small table of registers to
> >> the device.
> >>
> >> The t
On 1/11/19 6:41 PM, Kieran Bingham wrote:
> The ADV748x is currently reset by writting a small table of registers to
> the device.
>
> The table lacks documentation and contains magic values to perform the
> actions, including using a fake register address to introduce a delay
> loop.
>
> Remove
Use WARN_ON_ONCE to print a stack trace and return a proper error
code instead.
Signed-off-by: Christoph Hellwig
Reviewed-by: Robin Murphy
---
include/linux/dma-mapping.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mappin
Hi all,
this series fixes a rather gross layering violation in videobuf2, which
pokes into arm DMA mapping internals to get a DMA address for memory that
does not have a page structure, and to do so fixes up the dma_map_resource
implementation to not provide a somewhat dangerous default and improv
Instead provide a proper implementation in the direct mapping code, and
also wire it up for arm and powerpc, leaving an error return for all the
IOMMU or virtual mapping instances for which we'd have to wire up an
actual implementation
Signed-off-by: Christoph Hellwig
---
arch/arm/mm/dma-mapping
vb2_dc_get_userptr pokes into arm direct mapping details to get the
resemblance of a dma address for a a physical address that does is
not backed by a page struct. Not only is this not portable to other
architectures with dma direct mapping offsets, but also not to uses
of IOMMUs of any kind. Swi
Hi Hans,
On Fri, 2019-01-18 at 10:30 +0100, Hans Verkuil wrote:
> On 1/17/19 4:50 PM, Philipp Zabel wrote:
[...]
> > +
> > +static const struct video_device ipu_csc_scaler_videodev_template = {
> > + .name = "ipu0_ic_pp mem2mem",
>
> I would expect to see something like 'imx-media-csc
Hi Matt,
I'm merging this patch, but can you add a new patch that updates the entry for
this driver in the MAINTAINERS file with references to the relevant bindings
files?
I.e., for this one you add:
F: Documentation/devicetree/bindings/media/i2c/melexis,mlx90640.txt
but you need to add t
Hi Hans,
On Fri, Jan 18, 2019 at 11:08 AM Hans Verkuil wrote:
> This patch is still in my patchwork todo list, and I wonder who will pick
> this up,
> especially the change to arch/powerpc/include/asm/io.h.
I think the powerpc tree makes most sense.
> Wouldn't it be easier to just fix this in
On Thu, 2019-01-17 at 12:49 -0800, Steve Longerbeam wrote:
> Disable the CSI immediately after receiving the last EOF before stream
> off (and thus before disabling the IDMA channel).
>
> This fixes a complete system hard lockup on the SabreAuto when streaming
> from the ADV7180, by repeatedly sen
Hi Geert,
This patch is still in my patchwork todo list, and I wonder who will pick this
up,
especially the change to arch/powerpc/include/asm/io.h.
Wouldn't it be easier to just fix this in fsl-viu.c only by doing this:
#ifndef CONFIG_PPC
#ifndef out_be32
#define out_be32(v, a) iowrite32be(a,
Hi Arvind,
Yes, I know, this is an extremely reply. I'm cleaning up some old patches
that fell through the cracks, and this is one of them. My apologies.
On 3/20/18 12:16 PM, Arvind Yadav wrote:
> Here, double-free is happening on error path of hdpvr_probe.
>
> error_v4l2_unregister:
> v4l2_de
Hi Christoph,
On 2019-01-17 18:21, Christoph Hellwig wrote:
> On Mon, Jan 14, 2019 at 01:42:26PM +0100, Marek Szyprowski wrote:
>> On 2019-01-11 19:17, Christoph Hellwig wrote:
>>> vb2_dc_get_userptr pokes into arm direct mapping details to get the
>>> resemblance of a dma address for a a physical
On 1/17/19 4:50 PM, Philipp Zabel wrote:
> Add a single imx-media mem2mem video device that uses the IPU IC PP
> (image converter post processing) task for scaling and colorspace
> conversion.
> On i.MX6Q/DL SoCs with two IPUs currently only the first IPU is used.
>
> The hardware only supports wr
On 1/16/19 1:37 PM, Stanimir Varbanov wrote:
> This changes v4l2_pix_format and v4l2_plane_pix_format sizeimage
> field description to allow v4l clients to set bigger image size
> in case of variable length compressed data.
>
> Signed-off-by: Stanimir Varbanov
> ---
> Documentation/media/uapi/v4
On Fri, Jan 18, 2019 at 09:58:43AM +0100, Hans Verkuil wrote:
> On 1/18/19 9:56 AM, Sakari Ailus wrote:
> > On Thu, Jan 17, 2019 at 05:17:54PM +0100, hverkuil-ci...@xs4all.nl wrote:
> >> From: Hans Verkuil
> >>
> >> The soc_mt9t112, soc_ov772x and soc_tw9910 drivers now have
> >> non-soc-camera re
The following changes since commit e8f9b16d72631870e30a3d8e4ee9f1c097bc7ba0:
media: remove soc_camera ov9640 (2019-01-17 09:01:11 -0500)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-rmsensors3
for you to fetch changes up to 8ae3463355f534129814cb
On 1/18/19 9:56 AM, Sakari Ailus wrote:
> On Thu, Jan 17, 2019 at 05:17:54PM +0100, hverkuil-ci...@xs4all.nl wrote:
>> From: Hans Verkuil
>>
>> The soc_mt9t112, soc_ov772x and soc_tw9910 drivers now have
>> non-soc-camera replacements, so those three drivers can be
>> removed.
>>
>> The soc_camera
On Thu, Jan 17, 2019 at 05:17:54PM +0100, hverkuil-ci...@xs4all.nl wrote:
> From: Hans Verkuil
>
> The soc_mt9t112, soc_ov772x and soc_tw9910 drivers now have
> non-soc-camera replacements, so those three drivers can be
> removed.
>
> The soc_camera sh_mobile_ceu_camera platform driver also has
On 1/17/19 7:23 PM, Dafna Hirschfeld wrote:
> If the the queues are not streaming then the first resolution
> change is handled in the buf_queue callback.
> The following resolution change events are handled in job_ready.
>
> Signed-off-by: Dafna Hirschfeld
> ---
> drivers/media/platform/vicodec
The OV5640 driver currently supports a static color bar pattern with a
small vertical gamma gradient. The hardware also supports a color square
pattern, as well as having a rolling bar for dynamic sequences.
Add three more test patterns:
- color bars with a rolling bar (but without the gamma gr
Hi everyone,
This series improves the JPEG compression output mode handling of the
OV5640 sensor, and adds some more test patterns for users to use.
The JPEG compression output mode of the sensor works, but the data
framing is incorrect. Additional registers need to be set to configure
the framin
The OV5640 has many options for generating test patterns. Unfortunately
there is only one V4L2 control for it. Thus the driver would need to
list some or all combinations.
Move the test_pattern_menu list before the ov5640_set_ctrl_test_pattern
function that programs the hardware. This would allow
The OV5640 can generate many types of test patterns, some with
additional modifiers, such as a rolling bar, or gamma gradients.
Add the bit definitions for all bits in the test pattern register,
and use them to compose the values to be written to the register.
Signed-off-by: Chen-Yu Tsai
---
dr
The transparent feature for test patterns blends the test pattern with
an actual captured image. This makes the result non-static, subject to
changes in the sensor's field of view.
Test patterns should be predictable and deterministic, even if they are
dynamic patterns. Disable the transparent fea
The register value lists for all the supported resolution settings all
include a register address/value pair for setting the JPEG compression
mode. With the exception of 1080p (which sets mode 2), all resolutions
use mode 3.
The only difference between mode 2 and mode 3 is that mode 2 may have
pad
When compression is turned on, the on-bus data is framed according to
the compression mode, and the height and width set in VFIFO_VSIZE and
VFIFO_HSIZE. If these are not updated correctly, the sensor will send
data framed in a manner unexpected by the capture interface, such as
having more bytes pe
I, Mikhail Fridman have selected you specifically as one of my
beneficiaries for my Charitable Donation of $5 Million Dollars,
Check the link below for confirmation:
https://www.rt.com/business/343781-mikhail-fridman-will-charity/
I await your earliest response.
Best Regards,
Mikhail Fridman.
On 1/17/19 7:23 PM, Dafna Hirschfeld wrote:
> Add flags indicating the pixel encoding - yuv/rgb/hsv to
> fwht header and to the pixel info. Use it to enumerate
> the supported pixel formats.
>
> Signed-off-by: Dafna Hirschfeld
> ---
> drivers/media/platform/vicodec/codec-fwht.h | 5 ++
> .../
On 12/18/18 6:59 PM, sh...@kernel.org wrote:
> From: Shuah Khan
>
> Media Device Allocator API to allows multiple drivers share a media device.
> This API solves a very common use-case for media devices where one physical
> device (an USB stick) provides both audio and video. When such media devi
80 matches
Mail list logo
