Hi Jacopo,
On 2018年01月10日 17:20, jacopo mondi wrote:
Hi Shunqian,
On Wed, Jan 10, 2018 at 10:06:04AM +0800, Shunqian Zheng wrote:
Add device tree binding documentation for the OV5695 sensor.
Signed-off-by: Shunqian Zheng
---
.../devicetree/bindings/media/i2c/ov5695.txt | 41
Hi Jacopo,
On 2018年01月10日 17:08, jacopo mondi wrote:
Hello Shunqian,
On Wed, Jan 10, 2018 at 10:06:05AM +0800, Shunqian Zheng wrote:
[snip]
+static int __ov5695_start_stream(struct ov5695 *ov5695)
+{
+ int ret;
+
+ ret = ov5695_write_array(ov5695->client, ov5695_global_regs);
+
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 Jan 11 05:00:16 CET 2018
media-tree git hash:e3ee691dbf24096ea51b3200946b11d68ce75361
media_build git
Add binding documentation for Allwinner V3s CSI.
Signed-off-by: Yong Deng
---
.../devicetree/bindings/media/sun6i-csi.txt| 59 ++
1 file changed, 59 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/sun6i-csi.txt
diff --git a/Documentation/dev
Allwinner V3s SoC features two CSI module. CSI0 is used for MIPI CSI-2
interface and CSI1 is used for parallel interface. This is not
documented in datasheet but by test and guess.
This patch implement a v4l2 framework driver for it.
Currently, the driver only support the parallel interface. MIPI
This patchset add initial support for Allwinner V3s CSI.
Allwinner V3s SoC features two CSI module. CSI0 is used for MIPI CSI-2
interface and CSI1 is used for parallel interface. This is not
documented in datasheet but by test and guess.
This patchset implement a v4l2 framework driver and add a b
Hi Maxime,
On Wed, 10 Jan 2018 16:37:24 +0100
Maxime Ripard wrote:
> Hi Hugues,
>
> On Mon, Jan 08, 2018 at 05:13:39PM +, Hugues FRUCHET wrote:
> > I'm using a ST board with OV5640 wired in parallel bus output in order
> > to interface to my STM32 DCMI parallel interface.
> > Perhaps could
Hi Hugues,
On Wed, Jan 10, 2018 at 03:51:07PM +, Hugues FRUCHET wrote:
> Good news Maxime !
>
> Have you seen that you can adapt the polarities through devicetree ?
>
> + /* Parallel bus endpoint */
> + ov5640_to_parallel: endpoint {
> [...]
> +
On Wed, Jan 10, 2018 at 8:03 PM, Christoph Hellwig wrote:
> We need to pass a struct device to the dma API, even if some
> architectures still support that for legacy reasons, and should not mix
> it with the old PCI dma API.
>
> Note that the driver also seems to never actually unmap its dma mapp
Back before the dawn of time pci_dma_* with a NULL pci_dev argument
was used for all kinds of things, e.g. dma mapping for non-PCI
devices. All this has been long removed, but it turns out we
still care for a NULL pci_dev in the wrappers, and we still have
two odd USB drivers that use pci_dma_allo
Switch to a plain kzalloc instead of pci_zalloc_coherent to allocate
memory for the USB DMA.
Signed-off-by: Christoph Hellwig
---
drivers/media/usb/ttusb-budget/dvb-ttusb-budget.c | 18 --
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git a/drivers/media/usb/ttusb-budg
Switch to a plain kzalloc instead of pci_zalloc_coherent to allocate
memory for the USB DMA.
Signed-off-by: Christoph Hellwig
---
drivers/media/usb/ttusb-dec/ttusb_dec.c | 18 --
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git a/drivers/media/usb/ttusb-dec/ttusb_dec.
We need to pass a struct device to the dma API, even if some
architectures still support that for legacy reasons, and should not mix
it with the old PCI dma API.
Note that the driver also seems to never actually unmap its dma mappings,
but to fix that we'll need someone more familar with the drive
Historically some ISA drivers used the old PCI DMA API with a NULL pdev
argument, but these days this isn't used and not too useful due to the
per-device DMA ops, so remove it.
Signed-off-by: Christoph Hellwig
---
include/linux/pci-dma-compat.h | 27 +--
1 file changed, 1
I'm trying to build using the latest media_build and media_tree
branches, but I'm getting an issue when running `modprobe -a cx23885`
(from dmesg):
[ 5373.246321] Linux video capture interface: v2.00
[ 5373.257419] rc_core: loading out-of-tree module taints kernel.
[ 5373.257452] rc_core: module v
2018-01-10 Nicolas Dufresne :
> Le mercredi 10 janvier 2018 à 14:07 -0200, Gustavo Padovan a écrit :
> > v7 bring a fix for a crash when not using fences and a uAPI fix.
> > I've done a bit more of testing on it and also measured some
> > performance. On a intel laptop a DRM<->V4L2 pipeline with f
On Tue, Jan 9, 2018 at 11:31 PM, Sakari Ailus
wrote:
>> depends on VIDEO_V4L2_SUBDEV_API
>> ---help---
>> This is a driver for the DW9714 camera lens voice coil.
>> @@ -636,7 +636,6 @@ config VIDEO_OV5670
>> tristate "OmniVision OV5670 sensor support"
>>
Le mercredi 10 janvier 2018 à 14:07 -0200, Gustavo Padovan a écrit :
> v7 bring a fix for a crash when not using fences and a uAPI fix.
> I've done a bit more of testing on it and also measured some
> performance. On a intel laptop a DRM<->V4L2 pipeline with fences is
> runnning twice as faster tha
Replace GPL license statement with SPDX GPL-2.0 license identifier.
Signed-off-by: Shuah Khan
---
drivers/media/v4l2-core/v4l2-mc.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-mc.c
b/drivers/media/v4l2-core/v4l2-mc.c
index 303980b
From: Gustavo Padovan
Add section to VIDIOC_QBUF about it
v5:
- Remove V4L2_CAP_ORDERED
- Add doc about V4L2_FMT_FLAG_UNORDERED
v4:
- Document ordering behavior for in-fences
- Document V4L2_CAP_ORDERED capability
- Remove doc about OUT_FENCE event
From: Gustavo Padovan
Explicit synchronization benefits a lot from ordered queues, they fit
better in a pipeline with DRM for example so create a opt-in way for
drivers notify videobuf2 that the queue is unordered.
Drivers don't need implement it if the queue is ordered.
Signed-off-by: Gustavo
From: Gustavo Padovan
For explicit synchronization it important for userspace to know if the
format being used by the driver can deliver the buffers back to userspace
in the same order they were queued with QBUF.
Ordered streams fits nicely in a pipeline with DRM for example, where
ordered buffe
From: Gustavo Padovan
If V4L2_BUF_FLAG_OUT_FENCE flag is present on the QBUF call we create
an out_fence and send its fd to userspace on the fence_fd field as a
return arg for the QBUF call.
The fence is signaled on buffer_done(), when the job on the buffer is
finished.
v8:
- return 0 a
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 can't be queued to the
driver before its fences signal. And a buffer can't be queue to the driver
out of the order they were queued from userspace. That mean
From: Gustavo Padovan
Hi,
v7 bring a fix for a crash when not using fences and a uAPI fix.
I've done a bit more of testing on it and also measured some
performance. On a intel laptop a DRM<->V4L2 pipeline with fences is
runnning twice as faster than the same pipeline with no fences.
For more de
Good news Maxime !
Have you seen that you can adapt the polarities through devicetree ?
+ /* Parallel bus endpoint */
+ ov5640_to_parallel: endpoint {
[...]
+ hsync-active = <0>;
+ vsync-active
Hi Hugues,
On Mon, Jan 08, 2018 at 05:13:39PM +, Hugues FRUCHET wrote:
> I'm using a ST board with OV5640 wired in parallel bus output in order
> to interface to my STM32 DCMI parallel interface.
> Perhaps could you describe your setup so I could help on understanding
> the problem on your s
Some devices, such as the DVBSky S952 and T982 cards, are dual port cards
that provide two cx23885 devices on the same PCI device, which means the
attributes available for writing udev rules are exactly the same, apart
from the adapter number. Unfortunately, the adapter numbers are dependent
on th
On Wed, Jan 10, 2018 at 02:46:32PM +0100, Christian König wrote:
> Am 10.01.2018 um 14:21 schrieb Daniel Vetter:
> > On Wed, Jan 10, 2018 at 01:53:41PM +0100, Christian König wrote:
> > > Change reservation_object_get_fences_rcu to make the exclusive fence
> > > pointer optional.
> > >
> > > If no
Am 10.01.2018 um 14:21 schrieb Daniel Vetter:
On Wed, Jan 10, 2018 at 01:53:41PM +0100, Christian König wrote:
Change reservation_object_get_fences_rcu to make the exclusive fence
pointer optional.
If not specified the exclusive fence is put into the fence array as
well.
This is helpful for a
On Wed, Jan 10, 2018 at 01:53:41PM +0100, Christian König wrote:
> Change reservation_object_get_fences_rcu to make the exclusive fence
> pointer optional.
>
> If not specified the exclusive fence is put into the fence array as
> well.
>
> This is helpful for a couple of cases where we need all f
Change reservation_object_get_fences_rcu to make the exclusive fence
pointer optional.
If not specified the exclusive fence is put into the fence array as
well.
This is helpful for a couple of cases where we need all fences in a
single array.
Signed-off-by: Christian König
---
drivers/dma-buf/
Before this patch, when compiled for arm32, the signal strength
were reported as:
Lock (0x1f) Signal= 4294908.66dBm C/N= 12.79dB
Because of a 32 bit integer overflow. After it, it is properly
reported as:
Lock (0x1f) Signal= -58.64dBm C/N= 12.79dB
Signed-off-by: Mauro Carvalho Cheha
On Tue, 9 Jan 2018 10:58:30 -0800 Linus Torvalds
wrote:
> So I really think "you can use up 90% of CPU time with a UDP packet
> flood from the same network" is very very very different - and
> honestly not at all as important - as "you want to be able to use a
> USB DVB receiver and watch/recor
The "txbuf" is uninitialized when we call ir_raw_encode_scancode() so
this failure path would lead to a crash.
Fixes: a74b2bff5945 ("media: lirc: do not pass ERR_PTR to kfree")
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index fae42f120aa4.
On Wed, Jan 10, 2018 at 10:20:10AM +0100, jacopo mondi wrote:
> Hi Shunqian,
>
> On Wed, Jan 10, 2018 at 10:06:04AM +0800, Shunqian Zheng wrote:
> > Add device tree binding documentation for the OV5695 sensor.
> >
> > Signed-off-by: Shunqian Zheng
> > ---
> > .../devicetree/bindings/media/i2c/ov5
Hi Shunqian,
On Wed, Jan 10, 2018 at 10:06:04AM +0800, Shunqian Zheng wrote:
> Add device tree binding documentation for the OV5695 sensor.
>
> Signed-off-by: Shunqian Zheng
> ---
> .../devicetree/bindings/media/i2c/ov5695.txt | 41
> ++
> 1 file changed, 41 insertions
Hello Shunqian,
On Wed, Jan 10, 2018 at 10:06:05AM +0800, Shunqian Zheng wrote:
[snip]
> +static int __ov5695_start_stream(struct ov5695 *ov5695)
> +{
> + int ret;
> +
> + ret = ov5695_write_array(ov5695->client, ov5695_global_regs);
> + if (ret)
> + return ret;
> + r
On Tue, Jan 09, 2018 at 12:49:26PM -0800, Joe Perches wrote:
> This message doesn't make sense anymore and it might as well
> be deleted.
>
> And it might be better to use kcalloc
>
> ttusb->iso_buffer = kcalloc(FRAMES_PER_ISO_BUF * ISO_BUF_COUNT,
> ISO_FRA
On Tue, Jan 09, 2018 at 06:25:44PM -0600, Bjorn Helgaas wrote:
> It looks like "pci_free_consistent(NULL" is still used in
> drivers/net/ethernet/tundra/tsi108_eth.c.
Yikes. That one needs to pass the device is the platform dev to
the dma_map_* routines to start with, and mixing that with PCI
is
41 matches
Mail list logo
