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 12 05:00:50 CET 2019
media-tree git hash:1e0d0a5fd38192f23304ea2fc2b531fea7c74247
media_build git
Hi Laurent et al,
> Subject: RE: [PATCH v7 00/16] Intel IPU3 ImgU patchset
>
> 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/
Hi Jacopo,
> Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
>
> Hi Raj,
>
> On Wed, Jan 09, 2019 at 06:36:02PM +, Mani, Rajmohan wrote:
> > Hi Jacopo,
> >
> > > Subject: Re: [PATCH v7 00/16] Intel IPU3 ImgU patchset
> > >
> > > Hi Raj,
> > >
> > > On Wed, Jan 09, 2019 at 06:01:39PM +
On Sat, Jan 12, 2019 at 1:30 AM Jernej Skrabec wrote:
>
> A64 IR is compatible with A13, so add A64 compatible with A13 as a
> fallback.
We ask people to add the SoC-specific compatible as a contigency,
in case things turn out to be not so "compatible".
To be consistent with all the other SoCs a
Hi Hans,
On Fri, Jan 11, 2019 at 09:31:25AM +0100, Hans Verkuil wrote:
> Three fixes for a bug introduced in 5.0.
>
> The last patch (Validate num_planes for debug messages) is also backported
> to kernels >= 4.12 (the oldest kernel for which it applies cleanly).
The surrounding lines of code ha
Hi Kieran,
Thank you for the patch.
On Friday, 11 January 2019 19:41:41 EET Kieran Bingham wrote:
> The ADV748X_PAGE_WAIT is a fake page to insert arbitrary delays in the
> register tables.
>
> Its only usage was removed, so we can remove the handling and simplify
> the code.
>
> Signed-off-by:
On 1/11/19 9:13 PM, Nicolas Dufresne wrote:
> Le vendredi 11 janvier 2019 à 12:37 +0100, Hans Verkuil a écrit :
>> v4l2_compliance gave a warning for the S_PARM test for output streams:
>>
>> warn: v4l2-test-formats.cpp(1235): S_PARM is supported for buftype 2, but
>> not for ENUM_FRAMEINTERVALS
>
Hi Kieran,
Thank you for the patch.
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 table lacks documentation and contains magic values to perform the
> actions, including using a fake
Le vendredi 11 janvier 2019 à 12:37 +0100, Hans Verkuil a écrit :
> v4l2_compliance gave a warning for the S_PARM test for output streams:
>
> warn: v4l2-test-formats.cpp(1235): S_PARM is supported for buftype 2, but not
> for ENUM_FRAMEINTERVALS
>
> The reason is that vivid mapped s_parm for ou
Em Fri, 11 Jan 2019 19:17:31 +0100
Christoph Hellwig escreveu:
> 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
On Fri, 4 Jan 2019 11:05:59 +0800, Yunfei Dong wrote:
> Fix MTK binding document for MT8173 dtsi changed in order
> to use standard CCF interface.
> MT8173 SoC from Mediatek.
>
> Signed-off-by: Yunfei Dong
> Signed-off-by: Qianqian Yan
> ---
> change note:
> v2: modify subject
> ---
> .../devic
On 1/11/19 8:08 AM, Kieran Bingham wrote:
Hi Steve,
On 11/01/2019 15:43, Kieran Bingham wrote:
From: Steve Longerbeam
Thank you for the patch, (which was forwarded to me from the BSP team)
Switch to devm_kzalloc() when allocating the adv748x device struct.
Signed-off-by: Steve Longerbea
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 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 be practically useful.
Use WARN_ON_ONCE to print a stack trace and return a proper error
code instead.
Signed-off-by: Christoph Hellwig
---
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-mapping.h
index d3087829a6df..91a
Just returning the physical address when not map_resource method is
present is highly dangerous as it doesn't take any offset in the
direct mapping into account and does the completely wrong thing for
IOMMUs. Instead provide a proper implementation in the direct mapping
code, and also wire it up f
Reviewed-by: Steve Longerbeam
On 1/11/19 3:10 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 enabl
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 the table, and convert to code, documenting the purpose of
The sw_reset functionality was implemented through a poorly documented
set of 'required writes' from a table.
This also included an delay in the table which required a 'hack' in the
adv748x_write() routines.
These patches rework the reset handling to a function and remove the
delay workaround.
K
The ADV748X_PAGE_WAIT is a fake page to insert arbitrary delays in the
register tables.
Its only usage was removed, so we can remove the handling and simplify
the code.
Signed-off-by: Kieran Bingham
---
drivers/media/i2c/adv748x/adv748x-core.c | 17 ++---
drivers/media/i2c/adv748x/a
OrangePi Win board contains IR receiver. Enable it.
Signed-off-by: Jernej Skrabec
---
arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts
b/arch/arm64/boot/dts/allwinner/sun50
A64 IR is compatible with A13, so add A64 compatible with A13 as a
fallback.
Signed-off-by: Jernej Skrabec
---
Documentation/devicetree/bindings/media/sunxi-ir.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/sunxi-ir.txt
b/Docu
IR on A64 is nothing special and very similar to IR on A13 to the point
that same driver can be used.
Following patches just add necessary DT changes.
Best regards,
Jernej
Igors Makejevs (1):
arm64: dts: allwinner: a64: Add IR node
Jernej Skrabec (2):
media: dt: bindings: sunxi-ir: Add A64
From: Igors Makejevs
IR is similar to that in A13 and can use same driver.
Signed-off-by: Igors Makejevs
Signed-off-by: Jernej Skrabec
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i
imx274_read_reg() is not used since commit ca017467c78b ("media:
imx274: add helper to read multibyte registers").
Signed-off-by: Luca Ceresoli
---
drivers/media/i2c/imx274.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/drivers/media/i2c/imx274.c b/drivers/media/i2c/imx
From: Steve Longerbeam
Switch to devm_kzalloc() when allocating the adv748x device struct.
The sizeof() is updated to determine the correct allocation size from
the dereferenced pointer type rather than hardcoding the struct type.
Signed-off-by: Steve Longerbeam
Reviewed-by: Kieran Bingham
[K
Hi Steve,
On 11/01/2019 15:43, Kieran Bingham wrote:
> From: Steve Longerbeam
Thank you for the patch, (which was forwarded to me from the BSP team)
> Switch to devm_kzalloc() when allocating the adv748x device struct.
>
> Signed-off-by: Steve Longerbeam
> ---
> drivers/media/i2c/adv748x/adv
Hi Matsuoka-san,
Thank you for the patch,
On 11/01/2019 15:43, Kieran Bingham wrote:>
> From: Koji Matsuoka
>
> By Documentation/timers/timers-howto.txt, when waiting 20ms from 10us,
> it is correct to use usleep_range. this patch corrects it.
>
> Signed-off-by: Koji Matsuoka
> (cherry picked f
Embedded systems often connect to sensors or other multimedia
subdevices directly. Currently, to be able to select such a
subdevice (e.g. CONFIG_VIDEO_OV5640) disabling of the auto-
select config option is needed (CONFIG_MEDIA_SUBDRV_AUTOSELECT).
This is inconvenient as the ancillary drivers for a
From: Steve Longerbeam
Switch to devm_kzalloc() when allocating the adv748x device struct.
Signed-off-by: Steve Longerbeam
---
drivers/media/i2c/adv748x/adv748x-core.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/media/i2c/adv748x/adv748x-core.c
b/drivers/
From: Koji Matsuoka
By Documentation/timers/timers-howto.txt, when waiting 20ms from 10us,
it is correct to use usleep_range. this patch corrects it.
Signed-off-by: Koji Matsuoka
(cherry picked from horms/renesas-bsp commit
af0cdba377bc8a784cdae6a77fb7a822cebc7083)
Signed-off-by: Steve Longerb
On 19.10.2018 15:52, Luis Oliveira wrote:
> Add bindings for Synopsys DesignWare MIPI CSI-2 host.
>
> Signed-off-by: Luis Oliveira
> ---
> Changelog
> v2-V3
> - removed IPI settings
>
> .../devicetree/bindings/media/snps,dw-csi-plat.txt | 52
> ++
> 1 file changed, 52 i
Hi Helen,
I've started work to fix the last compliance failures with vimc so that
vimc can be used in regression tests.
But I found a kernel warning and a kernel oops using vimc from our master tree.
To test, load vimc, then run:
v4l2-ctl -d2 -v width=1920,height=1440
v4l2-ctl -d2 --stream-mmap
Convert to use vm_insert_range_buggy to map range of kernel memory
to user vma.
This driver has ignored vm_pgoff. We could later "fix" these drivers
to behave according to the normal vm_pgoff offsetting simply by
removing the _buggy suffix on the function name and if that causes
regressions, it gi
On 1/11/19 7:59 AM, Hans Verkuil wrote:
On 1/11/19 3:57 PM, shuah wrote:
On 12/19/18 6:51 AM, Takashi Iwai wrote:
On Tue, 18 Dec 2018 18:59:39 +0100,
sh...@kernel.org wrote:
From: Shuah Khan
Media Device Allocator API to allows multiple drivers share a media device.
This API solves a very c
Previouly drivers have their own way of mapping range of
kernel pages/memory into user vma and this was done by
invoking vm_insert_page() within a loop.
As this pattern is common across different drivers, it can
be generalized by creating new functions and use it across
the drivers.
vm_insert_ran
Previouly drivers have their own way of mapping range of
kernel pages/memory into user vma and this was done by
invoking vm_insert_page() within a loop.
As this pattern is common across different drivers, it can
be generalized by creating new functions and use it across
the drivers.
vm_insert_ran
On 1/11/19 3:57 PM, shuah wrote:
> On 12/19/18 6:51 AM, Takashi Iwai wrote:
>> On Tue, 18 Dec 2018 18:59:39 +0100,
>> 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
On 12/19/18 6:51 AM, Takashi Iwai wrote:
On Tue, 18 Dec 2018 18:59:39 +0100,
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) p
The first three patches add the buf_out_validate callback to vb2 so video
output devices can validate the v4l2_buffer struct (specifically, validating
the field).
This fixes a v4l2-compliance failure.
The last two patches fix a vim2m bug and fix a vivid compliance bug.
With this pull request all
Fix vim2m bug introduced in 4.20.
Regards,
Hans
The following changes since commit 1e0d0a5fd38192f23304ea2fc2b531fea7c74247:
media: s5p-mfc: fix incorrect bus assignment in virtual child device
(2019-01-07 14:39:36 -0500)
are available in the Git repository at:
git://linuxtv.org/
2019年1月11日(金) 0:28 Akinobu Mita :
>
> The VIDIOC_SUBDEV_G_FMT ioctl for this driver doesn't recognize
> V4L2_SUBDEV_FORMAT_TRY and always works as if V4L2_SUBDEV_FORMAT_ACTIVE
> is specified.
>
> Cc: Enrico Scholz
> Cc: Michael Grzeschik
> Cc: Marco Felsch
> Cc: Sakari Ailus
> Cc: Mauro Carval
Em Thu, 10 Jan 2019 21:42:27 +0100
"F.M." escreveu:
> Hi folks,
>
> I’m trying to set up two DVB-adapters, one receiving a cable and the
> other a terrestrial signal. In the tests involved are the following
> adapters:
>
> 1. TechnoTrend TVStick CT2-4400 (bus ID 0b48:3014)
> 2. Hauppaug
Hi Niklas,
Thank you for this series. I think it really helps towards breaking down
those pre-defined tables of register data.
--
Kieran
On 29/11/2018 02:01, Niklas Söderlund wrote:
> Hi,
>
> This series allows the TXA CSI-2 transmitter of the adv748x to function
> in 1-, 2- and 4- lane mode.
Hi Niklas,
On 29/11/2018 02:01, Niklas Söderlund wrote:
> The driver fixed the TXA CSI-2 transmitter in 4-lane mode while it could
> operate using 1-, 2- and 4-lanes. Update the driver to support all
> available modes.
>
> The driver makes use of large tables of static register/value writes
> whe
Hi Niklas,
On 29/11/2018 02:01, Niklas Söderlund wrote:
> The adv748x CSI-2 transmitters TXA and TXB can use different number of
> lanes to transmit data. In order to be able to configure the device
> correctly this information need to be parsed from device tree and stored
> in each TX private dat
Hi Niklas,
On 29/11/2018 02:01, Niklas Söderlund wrote:
> Extend the MIPI CSI-2 power up sequence to match the power up sequence
> in the hardware manual chapter "9.5.1 Power Up Sequence". This change
> allows the power up functions to be reused when initializing the
> hardware reducing code dupli
Hi Niklas,
Thank you for this series.
On 29/11/2018 02:01, Niklas Söderlund wrote:
> The CSI-2 transmitters can use a different number of lanes to transmit
> data. Make the data-lanes mandatory for the endpoints that describe the
> transmitters as no good default can be set to fallback on.
>
> S
Split off the field validation from buf_prepare into a new
buf_out_validate function. Field validation for output buffers should
be done there since buf_prepare is not guaranteed to be called at
QBUF time.
Signed-off-by: Hans Verkuil
---
Changes since v2:
- drop test whether the queue is an outpu
cancel_delayed_work_sync() was called for any queue, but it should only
be called for the queue that is associated with the currently running job.
Otherwise, if two filehandles are streaming at the same time, then closing the
first will cancel the work which might still be running for a job from t
The buffer arguments to v4l2_m2m_buf_copy_data args were swapped.
The reason is confusing naming conventions in vim2m. It certainly
could be improved.
Fixes: 7aca565ee3d0 ("media: vim2m: use v4l2_m2m_buf_copy_data")
Signed-off-by: Hans Verkuil
---
diff --git a/drivers/media/platform/vim2m.c b/dr
v4l2_compliance gave a warning for the S_PARM test for output streams:
warn: v4l2-test-formats.cpp(1235): S_PARM is supported for buftype 2, but not
for ENUM_FRAMEINTERVALS
The reason is that vivid mapped s_parm for output streams to g_parm. But if
S_PARM doesn't actually change anything, then i
On Wed, Jan 02, 2019 at 11:16:57PM +0200, Sakari Ailus wrote:
> Drivers such as the Intel IPU3 ImgU driver use the IOVA library to manage
> the device's own virtual address space while not implementing the IOMMU
> API. Currently the IOVA library is only compiled if the IOMMU support is
> enabled, r
Prepare for mbus format being smaller than the written rectangle
due to burst size.
Signed-off-by: Philipp Zabel
Reviewed-by: Steve Longerbeam
---
drivers/staging/media/imx/imx-media-capture.c | 56 +--
1 file changed, 38 insertions(+), 18 deletions(-)
diff --git a/drivers/stag
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
Reviewed-by: Steve Longerbeam
---
drivers/staging/media/imx/imx-ic-prpencvf.c | 3 +-
drivers/staging/media/imx/imx-m
On 11.01.2019 10:11, Luis de Oliveira wrote:
>
>
> On 11-Jan-19 7:25, eugen.hris...@microchip.com wrote:
>>
>>
>> On 10.01.2019 18:18, Luis de Oliveira wrote:
>>>
>>>
>>> On 09-Jan-19 13:07, eugen.hris...@microchip.com wrote:
On 19.10.2018 15:52, Luis Oliveira wrote:
> Add th
Three fixes for a bug introduced in 5.0.
The last patch (Validate num_planes for debug messages) is also backported
to kernels >= 4.12 (the oldest kernel for which it applies cleanly).
Regards,
Hans
The following changes since commit 1e0d0a5fd38192f23304ea2fc2b531fea7c74247:
media:
On 11-Jan-19 7:25, eugen.hris...@microchip.com wrote:
>
>
> On 10.01.2019 18:18, Luis de Oliveira wrote:
>>
>>
>> On 09-Jan-19 13:07, eugen.hris...@microchip.com wrote:
>>>
>>>
>>> On 19.10.2018 15:52, Luis Oliveira wrote:
Add the Synopsys MIPI CSI-2 controller driver. This
controlle
59 matches
Mail list logo
