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 Oct 21 05:00:16 CEST 2017
media-tree git hash:61065fc3e32002ba48aa6bc3816c1f6f9f8daf55
media_build gi
From: Gustavo Padovan
Hi,
I renamed this back to RFC as many things are still under
discussion/open but it integrates all comments received on the
previous round[1].
My main goal now is to fit as many use cases as possible into this
Explicit Synchronization implementation, but first I'd like to
From: Gustavo Padovan
In all places that we were calling v4l2_ctrl_subscribe event() we now call
v4l2_subscribe_event_v4l2() that embed v4l2_ctrl_subscribe event() and can
be expanded to support more events.
Signed-off-by: Gustavo Padovan
---
drivers/media/common/saa7146/saa7146_video.c
From: Gustavo Padovan
We need a common function to subscribe all the common events in drivers,
so far we had only V4L2_EVENT_CTRL, so such a function wasn't necessary,
but we are about to introduce a new event for the upcoming explicit fences
implementation, thus a common place is needed.
Signed
From: Gustavo Padovan
For some type of events we may require the event user in the
kernel to run some operation when DQ_EVENT() is called.
V4L2_EVENT_OUT_FENCE is the first user of this mechanism as it needs
to call v4l2 core back to install a file descriptor.
This is WIP, I believe we are able
From: Gustavo Padovan
Driver that implement their own .vidioc_subscribe_event function should
be using v4l2_subscribe_event_v4l2() instead of
v4l2_ctrl_subscribe_event().
Signed-off-by: Gustavo Padovan
---
drivers/media/pci/cobalt/cobalt-v4l2.c | 2 +-
drivers/media/pci/ivtv/ivtv-i
From: Gustavo Padovan
Instead of assigning the global v4l2 device, assign the specific device.
This was causing trouble when using V4L2 events with vivid devices.
The device's queue should be the same we opened in userspace.
This is needed for the upcoming V4L2_EVENT_OUT_FENCE support. The curre
From: Gustavo Padovan
With the upcoming explicit synchronization support to V4L2 we need a
way to notify userspace of the out_fence_fd when buffers are queued to the
driver - buffers with in-fences attached to it can only be queued once the
fence signal, so the queueing to the driver might be def
From: Gustavo Padovan
For explicit synchronization (and soon for HAL3/Request API) we need
the v4l2-driver to guarantee the ordering in which the buffers were queued
by userspace. This is already true for many drivers, but we never needed
to say it.
v2: rename property to 'ordered_in_driver' to
From: Gustavo Padovan
To enable vivid to be used with explicit synchronization we need
to mark its queues as ordered. vivid queues are already ordered by
default so we no changes are needed.
v2: rename 'ordered' to 'ordered_in_driver' to avoid confusion.
Signed-off-by: Gustavo Padovan
Acked-by
From: Gustavo Padovan
By setting this member on vb2_queue the driver tell vb2 core that
it requires the buffers queued in QBUF to be queued with same order to the
driver.
Signed-off-by: Gustavo Padovan
---
include/media/videobuf2-core.h | 4
1 file changed, 4 insertions(+)
diff --git a/i
From: Gustavo Padovan
To support explicit synchronization we need to run all operations that can
fail before we queue the buffer to the driver. With fences the queueing
will be delayed if the fence is not signaled yet and it will be better if
such callback do not fail.
For that we move the vb2_s
From: Gustavo Padovan
Turn the reserved2 field into fence_fd that we will use to send
an in-fence to the kernel and return an out-fence from the kernel to
userspace.
Two new flags were added, V4L2_BUF_FLAG_IN_FENCE, that should be used
when sending a fence to the kernel to be waited on, and
V4L2
From: Javier Martinez Canillas
Add a videobuf2-fence.h header file that contains different helpers
for DMA buffer sharing explicit fence support in videobuf2.
v2: - use fence context provided by the caller in vb2_fence_alloc()
Signed-off-by: Javier Martinez Canillas
Signed-off-by: Gustavo
From: Gustavo Padovan
Add vb2_setup_out_fence() and the needed members to struct vb2_buffer.
v2: - change it to reflect fd_install at DQEVENT
- add fence context for out-fences
Signed-off-by: Gustavo Padovan
---
drivers/media/v4l2-core/videobuf2-core.c | 31 +++
From: Gustavo Padovan
If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create
an out_fence and send to userspace on the V4L2_EVENT_OUT_FENCE when
the buffer is queued to the driver, or right away if the queue is ordered
both in VB2 and in the driver.
The fence is signaled on buffer
From: Gustavo Padovan
Add section to VIDIOC_QBUF about it
v3:
- make the out_fence refer to the current buffer (Hans)
- Note what happens when the IN_FENCE is not set (Hans)
v2:
- mention that fences are files (Hans)
- rework for the new API
Signed-off-by: Gusta
From: Gustavo Padovan
Receive in-fence from userspace and add support for waiting on them
before queueing the buffer to the driver. Buffers are only queued
to the driver once they are ready. A buffer is ready when its
in-fence signals.
For queues that require vb2 to queue buffers to the v4l2 dri
From: Gustavo Padovan
Add a new event the userspace can subscribe to receive notifications
of the out_fence_fd when a buffer is queued onto the driver.
The event provides the index of the queued buffer and the out_fence_fd.
v3: - Rename event to V4L2_EVENT_OUT_FENCE
v2: - Add missing Documentat
2017-10-20 10:12 GMT+02:00 Russell King - ARM Linux :
> On Sat, Oct 14, 2017 at 12:53:35AM +0200, Pierre-Hugues Husson wrote:
>> @@ -2382,6 +2383,18 @@ __dw_hdmi_probe(struct platform_device *pdev,
>> goto err_isfr;
>> }
>>
>> + hdmi->cec_clk = devm_clk_get(hdmi->dev, "cec")
The documentation already mentions "cec" optional clock, but
currently the driver doesn't enable it.
Changes:
v2:
- Separate ENOENT errors from others
- Propagate other errors (especially -EPROBE_DEFER)
Signed-off-by: Pierre-Hugues Husson
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 26 +
Am Freitag, 20. Oktober 2017, 09:44:55 CEST schrieb Hans Verkuil:
> On 20/10/17 09:38, Heiko Stübner wrote:
> > Hi Hans,
> >
> > Am Freitag, 20. Oktober 2017, 09:28:58 CEST schrieb Hans Verkuil:
> >> On 14/10/17 17:39, Heiko Stuebner wrote:
> >>> So far only the hdmi cec supports using one of two
On 20/10/17 16:00, Tim Harvey wrote:
> On Thu, Oct 19, 2017 at 12:39 AM, Hans Verkuil wrote:
>
What I am missing here is handling of the RGB quantization range.
An HDMI receiver will typically send full range RGB or limited range YUV
to the SoC. The HDMI source can however send ful
Hi Ludwig,
P2P transactions are still *very* experimental at the moment and take a
lot of expertise to get working in a general setup. It will definitely
require changes to the kernel, including the drivers of all the devices
you are trying to make talk to eachother. If you're up for it you ca
On Fri, Oct 20, 2017 at 02:51:07PM +, Zhi, Yong wrote:
> > > + /* flip table to for convolution reverse indexing */
> > > + s64 coeff = coeffs[coeffs_size -
> > > + ((tap * (coeffs_size / taps)) +
> > > +
Hi, Sakari,
> -Original Message-
> From: Sakari Ailus [mailto:sakari.ai...@iki.fi]
> Sent: Friday, October 20, 2017 2:58 AM
> To: Zhi, Yong
> Cc: linux-media@vger.kernel.org; sakari.ai...@linux.intel.com; Zheng, Jian
> Xu ; Mani, Rajmohan
> ; Yang, Hyungwoo
> ; Hu, Jerry W
> Subject: Re:
Hey Marek and others,
just wanted to point out that I've also played around with Seung-Woo' patch for
a while. However this patch alone is very much incomplete.
In particular this is missing:
- At least v5 MFC hw needs source buffers to be also writable, so dma mapping
needs to be setup bidirecti
On Thu, Oct 19, 2017 at 12:39 AM, Hans Verkuil wrote:
>>> What I am missing here is handling of the RGB quantization range.
>>> An HDMI receiver will typically send full range RGB or limited range YUV
>>> to the SoC. The HDMI source can however send full or limited range RGB
>>> or limited range
Dear Linux kernel group
my name is Ludwig Petrosyan I am working in DESY (Germany)
we are responsible for the control system of all accelerators in DESY.
For a 7-8 years we have switched to MTCA.4 systems and using PCIe as a
central Bus.
I am mostly responsible for the Linux drivers of the
Hi Hans,
On Fri, Oct 20, 2017 at 01:56:48PM +0200, Hans Verkuil wrote:
> On 19/10/17 16:53, Sakari Ailus wrote:
> > Hi Harald and Hans,
> >
> > On Thu, Oct 19, 2017 at 03:09:15PM +0200, Harald Dankworth wrote:
> >> Find the major and minor numbers of the device. Check if the
> >> file /dev/dev/ch
On 19/10/17 16:53, Sakari Ailus wrote:
> Hi Harald and Hans,
>
> On Thu, Oct 19, 2017 at 03:09:15PM +0200, Harald Dankworth wrote:
>> Find the major and minor numbers of the device. Check if the
>> file /dev/dev/char/major:minor/uevent contains "DEVNAME=v4l-subdev".
>> If so, the device is a sub-d
Hi Hans,
On Thu, Oct 19, 2017 at 08:52:22AM +0200, Hans Verkuil wrote:
> On 10/18/2017 05:32 PM, Sakari Ailus wrote:
> > On Wed, Oct 18, 2017 at 04:56:56PM +0300, Sakari Ailus wrote:
> >> v4l2_fwnode_reference_parse_int_prop() will find an fwnode such that under
> >> the device's own fwnode, it wi
Hi Yong,
On Tue, Oct 17, 2017 at 10:54:56PM -0500, Yong Zhi wrote:
> ipu3 imgu video device based on v4l2, vb2 and
> media controller framework.
>
> Signed-off-by: Yong Zhi
> Signed-off-by: Ramya Vijaykumar
> ---
> drivers/media/pci/intel/ipu3/ipu3-v4l2.c | 1150
>
Hi all,
We are organizing a media mini-summit on Friday October 27 in Prague, co-located
with the ELCE conference:
http://events.linuxfoundation.org/events/embedded-linux-conference-europe
If you plan to attend, please let me know. It is open for all, but it is
nice if we know beforehand who we
On Tue, Oct 17, 2017 at 10:55:59PM -0500, Yong Zhi wrote:
> This patch adds support for the Intel IPU v3 as found
> on Skylake and Kaby Lake SoCs. The driver has a dependency
> on the firmware binary to function properly.
>
> Signed-off-by: Yong Zhi
> Signed-off-by: Tomasz Figa
> ---
> drivers/
On Tue, Oct 17, 2017 at 10:54:51PM -0500, Yong Zhi wrote:
> The pools are used to store previous parameters set by
> user with the parameter queue. Due to pipelining,
> there needs to be multiple sets (up to four)
> of parameters which are queued in a host-to-sp queue.
>
> Signed-off-by: Yong Zhi
From: Seung-Woo Kim
There is memory constraint for the buffers in V5 of the MFC hardware, but
when IOMMU is used, then this constraint is meaningless. Other version of
the MFC hardware don't have such limitations. So in such cases the driver
is able to use buffers placed anywhere in the system me
From: Hans Verkuil
This patch series sits on top of these two patch series:
https://lkml.org/lkml/2017/10/13/971
https://lkml.org/lkml/2017/10/14/161
The first adds support for the cec clk in dw-hdmi, the second adds an
iomux-route for the CEC pin on the rk3288.
This patch series defines the c
From: Hans Verkuil
The vdd10_lcd and vcc18_lcd regulators need to be enabled for HDMI output
to work, so add 'regulator-always-on', just as is done in rk3288-firefly.dtsi.
Also enable i2c5 and the hdmi block.
Signed-off-by: Hans Verkuil
---
arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi |
From: Hans Verkuil
The Firefly Reload uses PC7.
Signed-off-by: Hans Verkuil
Tested-by: Hans Verkuil
---
arch/arm/boot/dts/rk3288-firefly-reload.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288-firefly-reload.dts
b/arch/arm/boot/dts/rk3288-firefly-reload.dts
From: Hans Verkuil
The dw-hdmi block needs the cec clk for the rk3288. Add it.
Signed-off-by: Hans Verkuil
---
arch/arm/boot/dts/rk3288.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index 356ed1e62452.
From: Hans Verkuil
The CEC line can be routed to two possible pins. Define those pins.
Signed-off-by: Hans Verkuil
---
arch/arm/boot/dts/rk3288.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
index a48352aa1591..242
Hi Yong,
On Tue, Jul 18, 2017 at 10:13:40PM -0500, Yong Zhi wrote:
> A collection of routines that are mainly responsible
> to calculate the acc parameters.
>
> Signed-off-by: Yong Zhi
> ---
> drivers/media/pci/intel/ipu3/ipu3-css-params.c | 3114
>
> drivers/media/pci
Hi Yong,
On Tue, Oct 17, 2017 at 10:54:49PM -0500, Yong Zhi wrote:
> The UAPI header defines the structures and macros
> to be used by user space.
>
> Signed-off-by: Rajmohan Mani
> Signed-off-by: Yong Zhi
> ---
> include/uapi/linux/intel-ipu3.h | 2199
> ++
Hi Yong,
On Tue, Oct 17, 2017 at 10:48:34PM -0500, Yong Zhi wrote:
> From: Tomasz Figa
>
> IPU3 is capable to deal with a virtual address space with
> a dedicated MMU. The driver supports address translation
> from virtual(IPU3 internal) to 39 bit wide physical(system).
>
> Build has dependency
Dear Friend,
I am interested in establishing and operating a very viable business as a means
of investment. I do not know too well on how this is done in your country, so I
will need you to help me in this regard.
My preference is any good profit yielding business and I would appreciate any
Hi Yong,
On Tue, Oct 17, 2017 at 10:48:59PM -0500, Yong Zhi wrote:
> From: Tomasz Figa
>
> This patch adds driver to support IPU3-specific
> MMU-aware memory alloc/free and sg mapping functions.
>
> Signed-off-by: Tomasz Figa
> Signed-off-by: Yong Zhi
> ---
> drivers/media/pci/intel/ipu3/Kco
Hi Yong,
On Tue, Oct 17, 2017 at 10:46:48PM -0500, Yong Zhi wrote:
> This patchset adds support for the Intel IPU3 (Image Processing Unit)
> ImgU which is essentially a modern memory-to-memory ISP. It implements
> raw Bayer to YUV image format conversion as well as a large number of
> other pixel
On Sat, Oct 14, 2017 at 12:53:35AM +0200, Pierre-Hugues Husson wrote:
> @@ -2382,6 +2383,18 @@ __dw_hdmi_probe(struct platform_device *pdev,
> goto err_isfr;
> }
>
> + hdmi->cec_clk = devm_clk_get(hdmi->dev, "cec");
> + if (IS_ERR(hdmi->cec_clk)) {
> + hdmi
On 20/10/17 09:38, Heiko Stübner wrote:
> Hi Hans,
>
> Am Freitag, 20. Oktober 2017, 09:28:58 CEST schrieb Hans Verkuil:
>> On 14/10/17 17:39, Heiko Stuebner wrote:
>>> So far only the hdmi cec supports using one of two different pins
>>> as source, so add the route switching for it.
>>>
>>> Signe
Hi Hans,
Am Freitag, 20. Oktober 2017, 09:28:58 CEST schrieb Hans Verkuil:
> On 14/10/17 17:39, Heiko Stuebner wrote:
> > So far only the hdmi cec supports using one of two different pins
> > as source, so add the route switching for it.
> >
> > Signed-off-by: Heiko Stuebner
>
> Just tested thi
On 14/10/17 10:16, Hans Verkuil wrote:
> On 10/14/2017 12:53 AM, Pierre-Hugues Husson wrote:
>> The documentation already mentions "cec" optional clock, but
>> currently the driver doesn't enable it.
>>
>> Signed-off-by: Pierre-Hugues Husson
>
> Acked-by: Hans Verkuil
Tested-by: Hans Verkuil
On 14/10/17 17:39, Heiko Stuebner wrote:
> So far only the hdmi cec supports using one of two different pins
> as source, so add the route switching for it.
>
> Signed-off-by: Heiko Stuebner
Just tested this on my firefly reload and it works great!
Tested-by: Hans Verkuil
I'll post some dts p
usb_endpoint_maxp() has an inline keyword and searches for bits[10:0]
by & operation with 0x7ff. So, we can remove the duplicate & operation
with 0x7ff.
Signed-off-by: Jaejoong Kim
---
drivers/media/usb/uvc/uvc_video.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drive
usb_endpoint_maxp() has an inline keyword and searches for bits[10:0]
by & operation with 0x7ff. So, we can remove the duplicate & operation
with 0x7ff.
Signed-off-by: Jaejoong Kim
---
drivers/media/usb/usbtv/usbtv-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driver
usb_endpoint_maxp() has an inline keyword and searches for bits[10:0]
by & operation with 0x7ff. So, we can remove the duplicate & operation
with 0x7ff.
Jaejoong Kim (2):
media: usb: uvc: remove duplicate & operation
media: usb: usbtv: remove duplicate & operation
drivers/media/usb/usbtv/usb
Hi Mita-san,
Thank you for fixing this.
> Subject: [PATCH 2/4] media: max2175: don't clear V4L2_SUBDEV_FL_IS_I2C
>
> The v4l2_i2c_subdev_init() sets V4L2_SUBDEV_FL_IS_I2C flag in the
> subdev->flags. But this driver overwrites subdev->flags immediately
> subdev->after
> calling v4l2_i2c_subdev_
57 matches
Mail list logo
