Hi!
Without this series media-build is broken for Kernels older that 4.10.
When you will apply them?
Links to the individual patches:
https://patchwork.linuxtv.org/patch/43481/
https://patchwork.linuxtv.org/patch/43483/
https://patchwork.linuxtv.org/patch/43482/
BR,
Jasmin
driver_attribute are not supposed to change at runtime.
Functions driver_create_file/driver_remove_file are working with
const driver_attribute. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav
---
drivers/staging/media/atomisp/pci/atomisp2/atomisp_drvfs.c | 2 +-
1 file chang
From: Hans Verkuil
This little patch series adds support for CEC to the Toshiba TC358743
HDMI to CSI bridge.
The CEC IP is identical to that of the tc358840 for which I already had
CEC support. So this is effectively the tc358840 CEC code copied to the
tc358743. An RFC version of the tc358840 ha
From: Hans Verkuil
Make sure these values are set to avoid 'uninitialized variable'
warnings. Hasn't happened yet, but better safe than sorry.
Signed-off-by: Hans Verkuil
---
include/media/cec.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/media/cec.h b/include/media/cec.h
i
From: Hans Verkuil
Add the missing CEC register defines.
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/tc358743_regs.h | 94 ++-
1 file changed, 92 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/tc358743_regs.h
b/drivers/media/i2c/tc35874
From: Hans Verkuil
Add CEC support for the tc358743 HDMI-CSI bridge.
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/Kconfig| 8 ++
drivers/media/i2c/tc358743.c | 205 +--
2 files changed, 207 insertions(+), 6 deletions(-)
diff --git a/drivers/m
Use tabs in Kconfig for indentation rather than spaces.
The patch has been created using the following command:
find drivers/staging/media/atomisp/ -name Kconfig| \
xargs perl -i -pe 's/ {8}/\t/g'
Signed-off-by: Sakari Ailus
---
drivers/staging/media/atomisp/Kconfig| 10 ++-
On Wed, Aug 30, 2017 at 6:10 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework.
>
> While I have heard of SoCs that use the GPIO pin for CEC (apparently an
> early RockChip SoC used that), the main use-case of this driver
On Wed, Aug 30, 2017 at 6:10 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Document the bindings for the cec-gpio module for hardware where the
> CEC pin and optionally the HPD pin are connected to GPIO pins.
>
> Signed-off-by: Hans Verkuil
I usually refer to GPIO "lines" rather than "pins"
Em Wed, 30 Aug 2017 15:02:59 -0700
Randy Dunlap escreveu:
> On 08/30/17 14:23, Jonathan Corbet wrote:
> > On Mon, 28 Aug 2017 16:10:09 -0700
> > Randy Dunlap wrote:
> >
> >> kernel-doc parsing uses as ASCII codec, so let people know that
> >> kernel-doc comments should be in ASCII characters
On 31/08/17 11:20, Linus Walleij wrote:
> On Wed, Aug 30, 2017 at 6:10 PM, Hans Verkuil wrote:
>
>> From: Hans Verkuil
>>
>> Document the bindings for the cec-gpio module for hardware where the
>> CEC pin and optionally the HPD pin are connected to GPIO pins.
>>
>> Signed-off-by: Hans Verkuil
>
-tree-binding-file/20170831-144636
base: git://linuxtv.org/media_tree.git master
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget
https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O
~/bin
-tree-binding-file/20170831-144636
base: git://linuxtv.org/media_tree.git master
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by
From: Hans Verkuil
Document the bindings for the cec-gpio module for hardware where the
CEC line and optionally the HPD line are connected to GPIO lines.
Signed-off-by: Hans Verkuil
---
.../devicetree/bindings/media/cec-gpio.txt | 22 ++
1 file changed, 22 insertion
From: Hans Verkuil
Document these new CEC events.
Signed-off-by: Hans Verkuil
---
Documentation/media/uapi/cec/cec-ioc-dqevent.rst | 18 ++
1 file changed, 18 insertions(+)
diff --git a/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
b/Documentation/media/uapi/cec/cec-ioc-dq
From: Hans Verkuil
Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework.
While I have heard of SoCs that use the GPIO pin for CEC (apparently an
early RockChip SoC used that), the main use-case of this driver is to
function as a debugging tool.
By connecting the CEC line
From: Hans Verkuil
Add support for two new low-level events: PIN_HPD_LOW and PIN_HPD_HIGH.
This is specifically meant for use with the upcoming cec-gpio driver
and makes it possible to trace when the HPD pin changes. Some HDMI
sinks do strange things with the HPD and this makes it easy to debug
From: Hans Verkuil
This driver adds support for CEC implementations that use a pull-up
GPIO line. While SoCs exist that do this, the primary use-case is to
turn a single-board computer into a cheap CEC debugger.
Together with 'cec-ctl --monitor-pin' you can do low-level CEC bus
monitoring and do
From: Hans Verkuil
Add an entry for the CEC GPIO driver.
Signed-off-by: Hans Verkuil
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index eb930ebecfcb..5ef0d34ef502 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3205,6 +3205,15 @@ F:
On Wed, Aug 30, 2017 at 10:25:01PM +0200, Arnd Bergmann wrote:
> >> diff --git a/include/uapi/linux/dvb/video.h
> >> b/include/uapi/linux/dvb/video.h
> >> index d3d14a59d2d5..6c7f9298d7c2 100644
> >> --- a/include/uapi/linux/dvb/video.h
> >> +++ b/include/uapi/linux/dvb/video.h
> >> @@ -135,7 +135
On Thu, 31 Aug 2017, Mauro Carvalho Chehab wrote:
> As Documentation/conf.py has:
>
> # -*- coding: utf-8 -*-
>
> on its first line, I suspect that the error you're getting is likely
> due to the usage of a python version that doesn't recognize this.
AFAIK that has nothing to do with python
Em Thu, 31 Aug 2017 16:26:44 +0300
Jani Nikula escreveu:
> On Thu, 31 Aug 2017, Mauro Carvalho Chehab wrote:
> > As Documentation/conf.py has:
> >
> > # -*- coding: utf-8 -*-
> >
> > on its first line, I suspect that the error you're getting is likely
> > due to the usage of a python version
On Thu, Aug 31, 2017 at 1:01 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Document the bindings for the cec-gpio module for hardware where the
> CEC line and optionally the HPD line are connected to GPIO lines.
>
> Signed-off-by: Hans Verkuil
Reviewed-by: Linus Walleij
Yours,
Linus Walle
On Thu, Aug 31, 2017 at 1:01 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework.
>
> While I have heard of SoCs that use the GPIO pin for CEC (apparently an
> early RockChip SoC used that), the main use-case of this driver
On Thu, 31 Aug 2017 10:56:26 -0300
Mauro Carvalho Chehab wrote:
> It should have something to do with python version and/or to some
> locale info at the system, as neither I or Jon can reproduce it.
I can't reproduce it here, but I have certainly seen situations where
Python 2 wants to run with
On 30/08/17 13:04, Dave Stevenson wrote:
> On 30 August 2017 at 11:45, Hans Verkuil wrote:
>> On 30/08/17 11:40, Dave Stevenson wrote:
>>> Hi Hans.
>>>
>>> On 28 August 2017 at 15:15, Hans Verkuil wrote:
Hi Dave,
What is the status of this work? I ask because I tried to use this dr
On 31/08/17 16:10, Linus Walleij wrote:
> On Thu, Aug 31, 2017 at 1:01 PM, Hans Verkuil wrote:
>
>> From: Hans Verkuil
>>
>> Add a simple HDMI CEC GPIO driver that sits on top of the cec-pin framework.
>>
>> While I have heard of SoCs that use the GPIO pin for CEC (apparently an
>> early RockChi
Hi Brian,
On Thursday, 24 August 2017 14:14:31 EEST Brian Starkey wrote:
> On Mon, Aug 21, 2017 at 06:36:29PM +0200, Hans Verkuil wrote:
> > On 08/21/2017 06:01 PM, Daniel Vetter wrote:
> >> On Mon, Aug 21, 2017 at 5:52 PM, Brian Starkey wrote:
> >>> Hi all,
> >>>
> >>> I couldn't find this topic
Hi Brian,
On Tuesday, 29 August 2017 12:19:43 EEST Brian Starkey wrote:
> On Fri, Aug 25, 2017 at 10:14:03AM +0200, Hans Verkuil wrote:
> >On 24/08/17 14:26, Brian Starkey wrote:
> >> On Thu, Aug 24, 2017 at 01:37:35PM +0200, Hans Verkuil wrote:
> >>> On 08/24/17 13:14, Brian Starkey wrote:
>
Hi Brian,
On Wednesday, 30 August 2017 13:32:01 EEST Brian Starkey wrote:
> On Wed, Aug 30, 2017 at 11:53:58AM +0200, Hans Verkuil wrote:
> > On 30/08/17 11:36, Brian Starkey wrote:
> >> On Wed, Aug 30, 2017 at 10:10:01AM +0200, Hans Verkuil wrote:
> >>> On 30/08/17 09:50, Daniel Vetter wrote:
> >
It's 'this message', not 'this messages'.
Fix the typo.
Signed-off-by: Hans Verkuil
---
diff --git a/Documentation/media/uapi/cec/cec-ioc-receive.rst
b/Documentation/media/uapi/cec/cec-ioc-receive.rst
index 267044f7ac30..2a9b09676add 100644
--- a/Documentation/media/uapi/cec/cec-ioc-receive.rst
Hi Laurent,
On Thu, Aug 31, 2017 at 05:51:33PM +0300, Laurent Pinchart wrote:
Hi Brian,
On Wednesday, 30 August 2017 13:32:01 EEST Brian Starkey wrote:
On Wed, Aug 30, 2017 at 11:53:58AM +0200, Hans Verkuil wrote:
> On 30/08/17 11:36, Brian Starkey wrote:
>> On Wed, Aug 30, 2017 at 10:10:01AM
The description of CEC_TX_STATUS_ERROR referred to two previous statuses, but
there are three. Update the documentation accordingly.
Signed-off-by: Hans Verkuil
---
diff --git a/Documentation/media/uapi/cec/cec-ioc-receive.rst
b/Documentation/media/uapi/cec/cec-ioc-receive.rst
index 267044f7ac30
On 08/31/17 07:17, Jonathan Corbet wrote:
> On Thu, 31 Aug 2017 10:56:26 -0300
> Mauro Carvalho Chehab wrote:
>
>> It should have something to do with python version and/or to some
>> locale info at the system, as neither I or Jon can reproduce it.
>
> I can't reproduce it here, but I have certa
On 08/31/17 02:49, Mauro Carvalho Chehab wrote:
> Em Wed, 30 Aug 2017 15:02:59 -0700
> Randy Dunlap escreveu:
>
>> On 08/30/17 14:23, Jonathan Corbet wrote:
>>> On Mon, 28 Aug 2017 16:10:09 -0700
>>> Randy Dunlap wrote:
>>>
kernel-doc parsing uses as ASCII codec, so let people know that
On Thu, 31 Aug 2017, Randy Dunlap wrote:
> On 08/31/17 07:17, Jonathan Corbet wrote:
>> On Thu, 31 Aug 2017 10:56:26 -0300
>> Mauro Carvalho Chehab wrote:
>>
>>> It should have something to do with python version and/or to some
>>> locale info at the system, as neither I or Jon can reproduce it.
Le jeudi 31 août 2017 à 17:28 +0300, Laurent Pinchart a écrit :
> > e.g. if I have two devices which support MODIFIER_FOO, I could attempt
> > to share a buffer between them which uses MODIFIER_FOO without
> > necessarily knowing exactly what it is/does.
>
> Userspace could certainly set modifiers
On 08/31/17 09:05, Jani Nikula wrote:
> On Thu, 31 Aug 2017, Randy Dunlap wrote:
>> On 08/31/17 07:17, Jonathan Corbet wrote:
>>> On Thu, 31 Aug 2017 10:56:26 -0300
>>> Mauro Carvalho Chehab wrote:
>>>
It should have something to do with python version and/or to some
locale info at the
On Thu, 31 Aug 2017, Jani Nikula wrote:
> On Thu, 31 Aug 2017, Randy Dunlap wrote:
>> On 08/31/17 07:17, Jonathan Corbet wrote:
>>> On Thu, 31 Aug 2017 10:56:26 -0300
>>> Mauro Carvalho Chehab wrote:
>>>
It should have something to do with python version and/or to some
locale info at
The s5p-cec driver returned CEC_TX_STATUS_ERROR for the NACK condition.
Some digging into the datasheet uncovered the S5P_CEC_TX_STAT1 register where
bit 0 indicates if the transmit was nacked or not.
Use this to return the correct CEC_TX_STATUS_NACK status to userspace.
This was the only driver
On 08/31/17 09:36, Jani Nikula wrote:
> On Thu, 31 Aug 2017, Jani Nikula wrote:
>> On Thu, 31 Aug 2017, Randy Dunlap wrote:
>>> On 08/31/17 07:17, Jonathan Corbet wrote:
On Thu, 31 Aug 2017 10:56:26 -0300
Mauro Carvalho Chehab wrote:
> It should have something to do with pytho
On 08/31/17 10:34, Randy Dunlap wrote:
> On 08/31/17 09:36, Jani Nikula wrote:
>> On Thu, 31 Aug 2017, Jani Nikula wrote:
>>> On Thu, 31 Aug 2017, Randy Dunlap wrote:
On 08/31/17 07:17, Jonathan Corbet wrote:
> On Thu, 31 Aug 2017 10:56:26 -0300
> Mauro Carvalho Chehab wrote:
>
On Thu, 31 Aug 2017, Randy Dunlap wrote:
> On 08/31/17 09:36, Jani Nikula wrote:
>> On Thu, 31 Aug 2017, Jani Nikula wrote:
>>> On Thu, 31 Aug 2017, Randy Dunlap wrote:
On 08/31/17 07:17, Jonathan Corbet wrote:
> On Thu, 31 Aug 2017 10:56:26 -0300
> Mauro Carvalho Chehab wrote:
>>>
On 08/31/17 10:55, Jani Nikula wrote:
> On Thu, 31 Aug 2017, Randy Dunlap wrote:
>> On 08/31/17 09:36, Jani Nikula wrote:
>>> On Thu, 31 Aug 2017, Jani Nikula wrote:
On Thu, 31 Aug 2017, Randy Dunlap wrote:
> On 08/31/17 07:17, Jonathan Corbet wrote:
>> On Thu, 31 Aug 2017 10:56:26
From: Markus Elfring
Date: Thu, 31 Aug 2017 21:46:12 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation
Improve a size determination
Delete a jump target
drivers/media/dvb-fro
From: Markus Elfring
Date: Thu, 31 Aug 2017 21:10:25 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/dvb-frontends/mb86a20s.c | 5 +
1 file changed, 1 in
From: Markus Elfring
Date: Thu, 31 Aug 2017 21:13:26 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was det
From: Markus Elfring
Date: Thu, 31 Aug 2017 21:34:58 +0200
* Return directly after a call of the function "kzalloc" failed
at the beginning.
* Move a bit of exception handling code into an if branch.
* Adjust a condition check.
* Delete the jump target "error" which became unnecessary
with
Hi Hans,
On 21.08.2017 15:23, Hans Verkuil wrote:
> Hi Maciej,
>
> On 08/10/2017 11:53 PM, Maciej S. Szmigiero wrote:
>> This patch adds support for analog part of Medion 95700 in the cxusb
>> driver.
>>
>> What works:
>> * Video capture at various sizes with sequential fields,
>> * Input switchi
Hi Hans,
Thanks for comments and sorry for not replying faster.
On 21.08.2017 15:15, Hans Verkuil wrote:
> Hi Maciej,
>
> On 08/10/2017 11:50 PM, Maciej S. Szmigiero wrote:
>> This commit adds pin to pad mapping and output format configuration support
>> in CX2584x-series chips to cx25840 driver
This converts to use setup_timer() to set callback and data, though it
doesn't look like this would have worked with timer checking enabled
since no init_timer() was ever called before.
Cc: Mats Randgaard
Cc: Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
Signed-off-by: Kees Cook
---
dr
struct dtv_cmds_h is just an ancillary struct used by the
dvb_frontend.c to internally store frontend commands.
It doesn't belong to the userspace header, nor it is used anywhere,
except inside the DVB core. So, remove it from the header.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/d
This seems to be a pure fictional API :-)
It only exists at the DVB book, with no code implemeting it.
So, just get rid of it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/dvb/dmx-get-event.rst | 60 --
Documentation/media/uapi/dvb/dmx_fcalls.rst
Use a table to document the supported bandwidths. That makes
it clearer to readers.
Signed-off-by: Mauro Carvalho Chehab
---
.../media/uapi/dvb/fe_property_parameters.rst | 44 +-
1 file changed, 26 insertions(+), 18 deletions(-)
diff --git a/Documentation/media/uapi/dv
Most of the stuff at the Digital TV frontend header file
are documented only at the Documentation. However, a few
kernel-doc markups are there, several of them with parsing
issues.
Add the missing documentation, copying definitions from the
Documentation when it applies, fixing some bugs.
Please
The DVB documentation was negligected for a long time, with
resulted on several gaps between the API description and its
documentation.
I'm doing a new reading at the documentation. As result of it,
this series:
- improves the introductory chapter, making it more generic;
- Do some adjustments at
Now that frontend.h contains most documentation for the frontend,
remove the duplicated information from Documentation/ and use the
kernel-doc auto-generated one instead.
That should simplify maintainership of DVB frontend uAPI, as most
of the documentation will stick with the header file.
Signed
There's no driver currently using it; it is also not
documented about what it would be supposed to do.
So, get rid of it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/dmx.h.rst.exceptions | 1 -
Documentation/media/uapi/dvb/dmx-get-caps.rst | 41 ---
The demux documentation is pretty poor nowadays: most of the
structs and enums aren't documented at all.
Add proper kernel-doc markups for them and use it.
Now, the demux API is fully documented :-)
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/dmx.h.rst.exceptions | 5 +
Do
Several frontend properties are specific to a subset of the
delivery systems. Make it clearer when describing each
property.
Signed-off-by: Mauro Carvalho Chehab
---
.../media/uapi/dvb/fe_property_parameters.rst | 82 --
1 file changed, 75 insertions(+), 7 deletions(-)
The references there are only for DVB. Add missing references for
ATSC and ISDB standards.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/dvb/intro.rst | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/Documentation/media/uapi/dvb/intro.rst
b/Docume
No driver uses this ioctl, nor it is documented anywhere.
So, get rid of it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/dmx.h.rst.exceptions| 13
Documentation/media/uapi/dvb/dmx-set-source.rst | 44 -
Documentation/media/uapi/dvb/dmx_f
Due to a mistake, the DVB net chapter was actually broken
into two different chapters. Fix it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/dvb/net.rst | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/media/uapi/dvb/net.rst
b/Documentation/media/uapi/dvb/net
Convergence doesn't exist anymore. The community itself maintains
the spec. Update accordingly.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/dvb/intro.rst | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/Documentation/media/uapi/dvb/intro
Both CA and decoders are optional. Also, the presence or
absence has nothing to do on being a PCI card or not.
Nowadays, most hardware leaves the decoders to either the
GPU or to some ISP inside the SoC, instead of implementing
it inside the Digital TV part of the device.
So, change the wording t
There's a flag defined for Digital TV demux that is not used
anywhere, called DMX_KERNEL_CLIENT. Get rid of it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/dmx.h.rst.exceptions | 1 -
Documentation/media/uapi/dvb/dmx_types.rst | 1 -
include/uapi/linux/dvb/dmx.h
On several places at the introduction, a digital TV board and its
kernel support is called as DVB. The reason is simple: by the
time the document was written, there were no other digital TV
standards :-)
Modernize the specs by referring to them as Digital TV.
Signed-off-by: Mauro Carvalho Chehab
From: Gustavo Padovan
Hi,
Explicit Synchronization allows us to control the synchronization of
shared buffers from userspace by passing fences to the kernel and/or
receiving them from it. Fences passed to the kernel are named in-fences
and the kernel should wait them to signal before using the b
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: 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.
v4:
- Add a comment about dma_fence_add_callback() n
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
Call v4l2_ctrl_subscribe_event to subscribe to the BUF_QUEUED event as
well.
Signed-off-by: Gustavo Padovan
---
drivers/media/usb/uvc/uvc_v4l2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/usb/uvc/uvc_v4l2.c b/drivers/media/usb/uvc/uv
From: Gustavo Padovan
Instead of assigning the global v4l2 device, assign the specific device.
This was causing trouble when using 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_BUF_QUEUED support. Th
From: Gustavo Padovan
With the upcoming explicit synchronization support to V4L2 we need a
way to notify userspace when buffers are queued to the driver - buffers
with fences attached to it can only be queued once the fence signal, so
the queueing to the driver might be deferred.
Yet, userspace
From: Gustavo Padovan
Add a new event the userspace can subscribe to receive notifications
when a buffer is queued onto the driver. The event provides the index of
the queued buffer.
v2: - Add missing Documentation (Mauro)
Signed-off-by: Gustavo Padovan
---
Documentation/media/uapi/v4l/vidioc
From: Gustavo Padovan
Implement the needed pieces to let userspace subscribe for
V4L2_EVENT_BUF_QUEUED events. Videobuf2 will queue the event for the
DQEVENT ioctl.
v3: - Do not call v4l2 event API from vb2 (Mauro)
v2: - Use VIDEO_MAX_FRAME to allocate room for events at
v4l2_ev
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.
Signed-off-by: Gustavo Padovan
---
include/m
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.
Signed-off-by: Gustavo Padovan
Acked-by: Hans Verkuil
---
drivers/media/platform/vivid/vivid-core.c |
From: Javier Martinez Canillas
Add a videobuf2-fence.h header file that contains different helpers
for DMA buffer sharing explicit fence support in videobuf2.
Signed-off-by: Javier Martinez Canillas
Signed-off-by: Gustavo Padovan
---
include/media/videobuf2-fence.h | 49 ++
From: Gustavo Padovan
Add vb2_setup_out_fence() and the needed members to struct vb2_buffer.
Signed-off-by: Gustavo Padovan
---
drivers/media/v4l2-core/videobuf2-core.c | 31 +++
include/media/videobuf2-core.h | 5 +
2 files changed, 36 insertions(+)
From: Gustavo Padovan
Add section to VIDIOC_QBUF about it
Signed-off-by: Gustavo Padovan
---
Documentation/media/uapi/v4l/vidioc-qbuf.rst | 30
1 file changed, 30 insertions(+)
diff --git a/Documentation/media/uapi/v4l/vidioc-qbuf.rst
b/Documentation/media/uapi/v
From: Gustavo Padovan
If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create
an out_fence and return it to userspace on the fence_fd field.
The out fence fd returned references the next buffer to be queued to the
driver and not the buffer in the actual QBUF call. So there a list i
Add the spin lock for the clock enable and disable operations.
Signed-off-by: Wenyou Yang
---
drivers/media/platform/atmel/atmel-isc.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/atmel/atmel-isc.c
b/drivers/media/platform/atmel/atme
To improve the readability of code, rework the format list table,
split the format array into two. And fix the clock operation issue.
Wenyou Yang (4):
media: atmel_isc: Add spin lock for clock enable ops
media: atmel-isc: Add prepare and unprepare ops
media: atmel-isc: Enable the clocks dur
A software write operation to the ISC_CLKEN or ISC_CLKDIS register
requires double clock domain synchronization and is not permitted
when the ISC_SR.SIP is asserted. So add the .prepare and .unprepare
ops to make sure the ISC_CLKSR.SIP is unasserted before the write
operation to the ISC_CLKEN or IS
To meet the relationship, enable the HCLOCK and ispck during the
device probe, "isc_pck frequency is less than or equal to isc_ispck,
and isc_ispck is greater than or equal to HCLOCK."
Meanwhile, call the pm_runtime_enable() in the right place.
Signed-off-by: Wenyou Yang
---
drivers/media/platf
To improve the readability of code, split the format array into two,
one for the format description, other for the register configuration.
Meanwhile, add the flag member to indicate the format can be achieved
from the sensor or be produced by the controller, and rename members
related to the regist
Hi Hans,
On 2017/8/24 14:41, Hans Verkuil wrote:
On 08/24/2017 08:25 AM, Yang, Wenyou wrote:
On 2017/8/23 18:37, Hans Verkuil wrote:
On 08/22/17 09:30, wenyou.y...@microchip.com wrote:
Hi Hans,
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: 2017年8月22日 15:0
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: Fri Sep 1 05:00:21 CEST 2017
media-tree git hash:fce4b371fe5c99a9c05db8493d72f0d1a474ab26
media_build gi
2017-09-01 1:46 GMT+02:00 Mauro Carvalho Chehab :
> No driver uses this ioctl, nor it is documented anywhere.
>
> So, get rid of it.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media/dmx.h.rst.exceptions| 13
> Documentation/media/uapi/dvb/dmx-set-source.rst |
90 matches
Mail list logo