On 27.06.19 10:20, Hans Verkuil wrote:
> On 6/27/19 10:12 AM, Florian Echtler wrote:
>> On 26.06.19 11:52, Hans Verkuil wrote:
>>> This driver set the colorspace to SRGB, but that makes no sense for
>>> a touchscreen. Use RAW instead. This also ensures consistency with t
On 26.06.19 11:52, Hans Verkuil wrote:
> This driver set the colorspace to SRGB, but that makes no sense for
> a touchscreen. Use RAW instead. This also ensures consistency with the
> v4l_pix_format_touch() call that's used in v4l2-ioctl.c.
One question for clarification: this will only affect use
Sorry, didn't realize you'd also need my feedback. No complaints.
Acked-by: Florian Echtler
Best, Florian
On 04.06.19 18:06, Dmitry Torokhov wrote:
> Hi Hans,
>
> On Tue, Jun 04, 2019 at 02:36:27PM +0200, Hans Verkuil wrote:
>> Instead of filling in the struct v4
Hello Hans,
On 14.02.2018 13:13, Hans Verkuil wrote:
>
> On 14/02/18 13:09, Florian Echtler wrote:
>>
>> The internal device memory contains a table with two bytes for each sensor
>> pixel
>> (i.e. 960x540x2 = 1036800 bytes) that basically provide individual black
Hello Hans,
I've picked up work on the sur40 driver again recently. There is one major
feature left that is currently unsupported by the Linux driver, which is the
hardware-based calibration.
The internal device memory contains a table with two bytes for each sensor pixel
(i.e. 960x540x2 = 103680
This patch registers four standard control handlers using the corresponding
V4L2 framework.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 64 +++
1 file changed, 64 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b
This patch adds parameter definitions and module parameters for the four
userspace controls that the SUR40 can currently provide.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/input
Iteration 4, now with min/max values for module parameters.
Best regards, Florian
The SUR40 can recognize specific printed patterns directly in hardware;
this information (i.e. the pattern id) is present but currently unused
in the blob structure.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 -
1 file changed, 4 insertions(+), 1 deletion
ned-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 75 +++
1 file changed, 75 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 8a5b031..d6fa25e 100644
--- a/drivers/input/touchscreen/sur
As discussed previously, here's the third iteration of my patch to add
control functions for the SUR40 driver, with (hopefully) correct handling
of default values/module parameters, using the V4L2 control framework.
Best regards, Florian
ned-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 75 +++
1 file changed, 75 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 8a5b031..d6fa25e 100644
--- a/drivers/input/touchscreen/sur
The SUR40 can recognize specific printed patterns directly in hardware;
this information (i.e. the pattern id) is present but currently unused
in the blob structure.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 -
1 file changed, 4 insertions(+), 1 deletion
This patch adds parameter definitions and module parameters for the four
userspace controls that the SUR40 can currently provide.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/input
This patch registers four standard control handlers using the corresponding
V4L2 framework.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 64 +++
1 file changed, 64 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b
On 06.02.2018 22:31, Hans Verkuil wrote:
> On 02/06/2018 10:01 PM, Florian Echtler wrote:
>> To allow setting custom parameters for the sensor directly at startup, the
>> three primary controls are exposed as module parameters in this patch.
>>
>> +/* module pa
On 06.02.2018 22:22, Hans Verkuil wrote:
> On 02/06/2018 10:01 PM, Florian Echtler wrote:
>> The SUR40 can recognize specific printed patterns directly in hardware;
>> this information (i.e. the pattern id) is present but currently unused
>> in the blob structure.
>&g
This patch adds parameter definitions for the four userspace controls that
the SUR40 can currently provide.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers
This patch registers four standard control handlers using the corresponding
V4L2 framework.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 51 +++
1 file changed, 51 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b
ned-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 71 +++
1 file changed, 71 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 3af63415..7f6461d 100644
--- a/drivers/input/touchscreen/sur
To allow setting custom parameters for the sensor directly at startup, the
three primary controls are exposed as module parameters in this patch.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 16
1 file changed, 16 insertions(+)
diff --git a/drivers
As discussed previously, here's a second iteration of my patch to add
control functions for the SUR40 driver, now using the V4L2 control
framework.
The SUR40 can recognize specific printed patterns directly in hardware;
this information (i.e. the pattern id) is present but currently unused
in the blob structure.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 -
1 file changed, 4 insertions(+), 1 deletion
On 05.02.2018 15:56, Hans Verkuil wrote:
> Please add a change log when you make a patch.
> I for one would like to know why this has to be supplied as a module option.
The idea here was that each individual SUR40 device will likely have slightly
different "ideal" settings for the parameters, and
Hello Hans,
On Mon, 5 Feb 2018, Hans Verkuil wrote:
On 02/05/2018 03:29 PM, Florian Echtler wrote:
+
+static int sur40_vidioc_queryctrl(struct file *file, void *fh,
+ struct v4l2_queryctrl *qc)
Sorry, but this is very wrong. Use the control framework instead. See
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 114 ++
1 file changed, 114 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 63c7264b..c4b7cf1 100644
--- a/drivers/input/touchscreen
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 70 +++
1 file changed, 70 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 0dbb004..63c7264b 100644
--- a/drivers/input/touchscreen
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index c4b7cf1..d612f3f 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b/drivers/input
The SUR40 (aka Pixelsense) has internal registers that expose sensor
parameters such as brightness, gain etc. This patch creates V4L2
control items and maps them to the appropriate parameters.
This is an initial submission for review, comments welcome!
Best regards, Florian
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index f16f835..8375b06 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b/drivers
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 8375b06..0dbb004 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b
Hello again,
solved it myself, posting here for the record.
Solution is to install uvcdynctrl and running
uvcdynctrl -i /usr/share/uvcdynctrl/data/046d/logitech.xml
And voila, custom controls back again. Not well documented, but hey.
Best regards, Florian
On Sun, 1 Oct 2017, Florian Echtler
Hello everyone,
I recently upgraded from a 4.4 kernel to 4.10, and found that my Logitech
Quickcam Sphere now behaves differently.
More specifically, the pan/tilt controls do not work anymore - in fact,
they are completely gone from "v4l2-ctl -L".
In dmesg, I'm getting these messages:
[
Hi everyone,
next chapter in the neverending story of reverse-engineering the SUR40:
I've identified a couple of internal LCD panel registers which control
some aspects of the built-in image sensor. In particular, these are called
"Video Voltage", "Video Bias", and "IR Illumination Level".
N
On 06.07.2016 10:40, Hans Verkuil wrote:
> On 07/05/16 09:06, Hans Verkuil wrote:
>> On 07/05/2016 08:56 AM, Florian Echtler wrote:
>>> On 05.07.2016 08:41, Hans Verkuil wrote:
>>>>
>>>> Why is s_parm added when you can't change the framerate?
>
Hello Hans,
On 05.07.2016 08:41, Hans Verkuil wrote:
> On 05/31/2016 10:15 PM, Florian Echtler wrote:
>> The device hardware is always running at 60 FPS, so report this both via
>> PARM_IOCTL and ENUM_FRAMEINTERVALS.
>>
>> Signed-off-by: Martin Kaltenbrunner
>&g
Hello Hans,
On 01.07.2016 16:45, Hans Verkuil wrote:
> Florian Echtler (3):
> sur40: properly report a single frame rate of 60 FPS
> sur40: lower poll interval to fix occasional FPS drops to ~56 FPS
> sur40: fix occasional oopses on device close
Thanks for merging
On 30.06.2016 19:38, Nick Dyer wrote:
> Support both V4L2_TCH_FMT_TU08 and V4L2_PIX_FMT_GREY for backwards
> compatibility.
>
> Note: I have not tested these changes (I have no access to the hardware)
> so not signing off.
I will try to test this ASAP. However, I'm currently ill, so it might
take
On 23.06.2016 00:08, Nick Dyer wrote:
> diff --git a/drivers/input/touchscreen/sur40.c
> b/drivers/input/touchscreen/sur40.c
> index 880c40b..841e045 100644
> --- a/drivers/input/touchscreen/sur40.c
> +++ b/drivers/input/touchscreen/sur40.c
> @@ -599,7 +599,7 @@ static int sur40_probe(struct usb_i
On Wed, 22 Jun 2016, Nick Dyer wrote:
On 22/06/2016 12:48, Florian Echtler wrote:
On 20.06.2016 14:00, Hans Verkuil wrote:
On 06/17/2016 04:16 PM, Nick Dyer wrote:
Use a new device prefix v4l-touch for these devices, to stop generic
capture software from treating them as webcams.
Come to
On 20.06.2016 14:00, Hans Verkuil wrote:
> On 06/17/2016 04:16 PM, Nick Dyer wrote:
>> Some touch controllers send out raw touch data in a similar way to a
>> greyscale frame grabber. Add a new device type for these devices.
>>
>> Use a new device prefix v4l-touch for these devices, to stop generic
Hello everyone,
I've been doing some latency testing on my sur40 driver, and I've
measured over 160 ms of round-trip delay (with an external high-speed
camera, delay between lighting up an LED and seeing the on-screen
response in the video stream).
I'm aware that this value has to factor in scree
Closing the V4L2 device sometimes triggers a kernel oops.
Present patch fixes this.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c
The device hardware is always running at 60 FPS, so report this both via
PARM_IOCTL and ENUM_FRAMEINTERVALS.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 20 ++--
1 file changed, 18 insertions(+), 2 deletions
The framerate sometimes drops below 60 Hz if the poll interval is too high.
Lowering it to the minimum of 1 ms fixes this.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hello Hans,
On 23.05.2016 12:45, Hans Verkuil wrote:
>> +static int sur40_ioctl_parm(struct file *file, void *priv,
>> +struct v4l2_streamparm *p)
>> +{
>> +if (p->type == V4L2_BUF_TYPE_VIDEO_CAPTURE) {
>> +p->parm.capture.timeperframe.numerator = 1;
>> +
The device hardware is always running at 60 FPS, so report this both via
PARM_IOCTL and ENUM_FRAMEINTERVALS.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff
Closing the V4L2 device sometimes triggers a kernel oops.
Present patch fixes this.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c
The framerate sometimes drops below 60 Hz if the poll interval is too high.
Lowering it to the minimum of 1 ms fixes this.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
I do still plan to fix this, but I have no idea right now how this can
actually happen: if TOUCHSCREEN_SUR40 is enabled, then this will enable
VIDEOBUF2_DMA_SG, and that will select most of the other V4L2 modules in
turn - or am I missing something here?
Best, Florian1
On 04.07.2015 19:56, kbuild
Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 8add986..8be7b9b 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b/drivers/input
.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index e707b8d..d860d05 100644
--- a
Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index d860d05..8add986 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b
without blocking
all the time and still allowing for a bit of timing jitter, we reduce the poll
interval to 4 ms.
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers
This patch series adds several small fixes, features & performance
improvements. Many thanks to Martin Kaltenbrunner for testing the
original driver & submitting the patches.
Martin Kaltenbrunner (4):
reduce poll interval to allow full 60 FPS framerate
add frame size/frame rate query function
On 25.05.2015 13:22, Hans Verkuil wrote:
> On 05/21/2015 02:29 PM, Florian Echtler wrote:
>> This patch series adds several small fixes, features & performance
>> improvements. Many thanks to Martin Kaltenbrunner for testing the
>> original driver & submitting the pa
This patch series adds several small fixes, features & performance
improvements. Many thanks to Martin Kaltenbrunner for testing the
original driver & submitting the patches.
Martin Kaltenbrunner (4):
reduce poll interval to allow full 60 FPS framerate
add frame size/frame rate query function
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index d860d05..8add986 100644
--- a/drivers
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index a24eba5..e707b8d 100644
--- a/drivers/input
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index e707b8d..d860d05 100644
--- a
Signed-off-by: Martin Kaltenbrunner
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 8add986..8be7b9b 100644
--- a/drivers/input/touchscreen
n the spinlock
is taken and sur40_poll attempts to fetch the next buffer from buf_list, the
list is in fact empty.
This patch needs to be applied on top of the queued one adding V4L2 support
to the sur40 driver.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c | 5 +
1
Hello Antonio,
On 26.03.2015 22:10, Antonio Ospite wrote:
> On Wed, 25 Mar 2015 15:10:44 +0100
> Florian Echtler wrote:
>>
>> Thanks - any other suggestions how to debug such a complete freeze? I
>> have the following options enabled in my kernel config:
>>
&g
Hello Dmitry,
On 25.03.2015 14:23, Dmitry Torokhov wrote:
> On March 24, 2015 11:52:54 PM PDT, Florian Echtler
> wrote:
>> Currently, I'm setting the interval for input_polldev to 10 ms.
>> However, with video data being retrieved at the same time, it's quite
>&
than that. Could this ultimately be the
reason? What happens if a new poll() call is scheduled before the previous one
completes?
Best, Florian
On March 23, 2015 4:47:19 PM CET, Florian Echtler wrote:
>Additional note: this happens almost never with the original code using
>dma-contig, which
e that can help somebody in narrowing down the reason of the problem?
Best, Florian
On 23.03.2015 12:57, Florian Echtler wrote:
> Hello everyone,
>
> now that I'm using the newly merged sur40 video driver in a development
> environment, I've noticed that a custom V4L2 appl
Hello everyone,
now that I'm using the newly merged sur40 video driver in a development
environment, I've noticed that a custom V4L2 application we've been
using in our lab will sometimes trigger a hard lockup of the machine
(_nothing_ works anymore, no VT switching, no network, not even Magic
Sys
gt;
> git://linuxtv.org/hverkuil/media_tree.git for-v4.1m
>
> for you to fetch changes up to 69dc25b1cd764181a6b8c5b16b753ab645b3d55b:
>
> add raw video stream support for Samsung SUR40 (2015-03-16 12:43:10 +0100)
>
>
This patch adds raw video support for the Samsung SUR40 using vbuf2-dma-sg.
All tests from v4l2-compliance pass. Support for VB2_USERPTR is currently
disabled due to unexpected interference with dma-sg buffer sizes.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/Kconfig | 2
Hello Hans,
On 15.03.2015 17:26, Hans Verkuil wrote:
> On 03/12/2015 08:37 PM, Florian Echtler wrote:
>> On 09.03.2015 15:02, Hans Verkuil wrote:
>>> On 03/09/2015 02:45 PM, Florian Echtler wrote:
>>>> On 09.03.2015 11:09, Hans Verkuil wrote:
>>>&
This patch adds raw video support for the Samsung SUR40 using vbuf2-dma-sg.
All tests from v4l2-compliance pass. Support for VB2_USERPTR is currently
disabled due to unexpected interference with dma-sg buffer sizes.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/Kconfig | 2
Hello Hans,
On 09.03.2015 15:02, Hans Verkuil wrote:
> On 03/09/2015 02:45 PM, Florian Echtler wrote:
>> On 09.03.2015 11:09, Hans Verkuil wrote:
>>> The error almost certainly comes from usb_submit_urb(). That function does
>>> some
>>> checks on the sgl:
>
On 09.03.2015 11:09, Hans Verkuil wrote:
> Hi Florian,
>
> OK, the cause of this failure is this message:
>
> Mar 9 10:39:08 sur40 kernel: [ 1093.200960] sur40 2-1:1.0: error in
> usb_sg_wait
>
> So you need to print the error message here (sgr.status) so that I can see
> what
> it is.
I've a
On 21.02.2015 11:22, Hans Verkuil wrote:
> On 02/20/2015 10:46 PM, Florian Echtler wrote:
>> On 16.02.2015 12:40, Hans Verkuil wrote:
>>> On 02/11/2015 12:52 PM, Florian Echtler wrote:
>>> I prefer to dig into this a little bit more, as I don't really understan
On 16.02.2015 12:40, Hans Verkuil wrote:
> On 02/11/2015 12:52 PM, Florian Echtler wrote:
>> does anyone have any suggestions why USERPTR still fails with dma-sg?
>>
>> Could I just disable the corresponding capability for the moment so that
>> the patch could perhaps
Hello again,
does anyone have any suggestions why USERPTR still fails with dma-sg?
Could I just disable the corresponding capability for the moment so that
the patch could perhaps be merged, and investigate this separately?
Best, Florian
On 04.02.2015 16:30, Florian Echtler wrote:
> This pa
This patch adds raw video support for the Samsung SUR40, now finally using
videobuf2-dma-sg and the usb_sg_init/_wait helper functions. Further comments
regarding buffer handling are invited, as v4l2-compliance -s still fails the
USERPTR test.
Signed-off-by: Florian Echtler
---
drivers/input
Hello everyone,
On 04.02.2015 12:39, Hans Verkuil wrote:
> On 02/04/15 12:34, Laurent Pinchart wrote:
>> On Wednesday 04 February 2015 11:56:58 Florian Echtler wrote:
>>> That's what I assumed, however, I'm running into the same problem as
>>> with dma-sg
t, specify --expbuf-device
Total: 45, Succeeded: 44, Failed: 1, Warnings: 0
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/Kconfig | 2 +
drivers/input/touchscreen/sur40.c | 422 --
2 files changed, 412 insertions(+), 12 deletions(-)
diff --git a/dri
On 04.02.2015 11:22, Hans Verkuil wrote:
> On 02/04/15 11:08, Florian Echtler wrote:
>> On 04.02.2015 09:08, Hans Verkuil wrote:
>>> You can also make a version with vmalloc and I'll merge that, and then
>>> you can look more into the DMA issues. That way the dri
Hello Hans,
On 04.02.2015 09:08, Hans Verkuil wrote:
> I remain very skeptical about the use of dma-contig (or dma-sg for that
> matter). Have you tried using vmalloc and check if the USB core isn't
> automatically using DMA transfers for that?
>
> Basically I would like to see proof that vmalloc
Sorry to bring this up again, but would it be acceptable to simply use
dma-contig after all? Since the GFP_DMA flag is gone, this shouldn't be
too big of an issue IMHO, and I was kind of hoping the patch could still
be part of 3.20.
Best, Florian
On 29.01.2015 22:35, Florian Echtler wrote:
Hello again,
On 21.01.2015 14:29, Hans Verkuil wrote:
> On 01/21/15 14:28, Florian Echtler wrote:
>> On 20.01.2015 14:06, Laurent Pinchart wrote:
>>> That depends on the platform and whether it can DMA to vmalloc'ed memory
>>> :-)
>>> To be totally saf
Hello Teodora,
On 23.01.2015 14:05, Baluta, Teodora wrote:
> The fingerprint sensor acts more like a scanner device, so the
> closest type is the V4L2_CAP_VIDEO_CAPTURE. However, this is not a
> perfect match because the driver only sends an image, once, when
> triggered. Would it be a better alte
Hello everyone,
On 20.01.2015 14:06, Laurent Pinchart wrote:
> On Tuesday 20 January 2015 14:03:00 Hans Verkuil wrote:
>> On 01/20/15 13:59, Laurent Pinchart wrote:
>>> On Tuesday 20 January 2015 10:30:07 Hans Verkuil wrote:
I've CC-ed Laurent, I think he knows a lot more about this than I do
Hello Hans,
On 19.01.2015 11:38, Hans Verkuil wrote:
> Sorry for the delay.
No problem, thanks for your feedback.
>> Note: I'm intentionally using dma-contig instead of vmalloc, as the USB
>> core apparently _will_ try to use DMA for larger bulk transfers.
> As far as I can tell from looking thr
://floe.butterbrot.org/external/results.txt for details).
Note: I'm intentionally using dma-contig instead of vmalloc, as the USB
core apparently _will_ try to use DMA for larger bulk transfers.
Signed-off-by: Florian Echtler
---
drivers/input/touchscreen/sur40.c
On 06.01.2015 11:23, Hans Verkuil wrote:
> On 01/06/2015 11:17 AM, Florian Echtler wrote:
>>> You're not filling in the 'field' field of struct v4l2_buffer when
>>> returning a
>>> frame. It should most likely be FIELD_NONE in your case.
>>>&g
On 06.01.2015 10:36, Hans Verkuil wrote:
> On 01/06/2015 10:29 AM, Florian Echtler wrote:
>> There's only one failing test left, which is this one:
>>
>> Streaming ioctls:
>> test read/write: OK
>> fail: v4l2-test-buffers.cpp(284): g_fie
On Fri, 19 Dec 2014, Hans Verkuil wrote:
drivers/media remains under heavy development, so for video capture drivers
like yours you should always patch against either the mainline linux tree
or (preferred) the media_tree.git repo (git://linuxtv.org/media_tree.git,
master branch).
As per your sugg
On 19.12.2014 15:36, Hans Verkuil wrote:
> On 12/19/2014 03:30 PM, Florian Echtler wrote:
>> Ran the most recent version from git master, got a total of 6 fails, 4
>> of which are probably easy fixes:
>>
>>> fail: v4l2-compliance.cpp(306): missing bus_info prefix (&#x
On 18.12.2014 15:11, Hans Verkuil wrote:
> Run as 'v4l2-compliance -s' (-s starts streaming tests as well and it
> assumes you have a valid input signal).
> Mail if you have any questions about the v4l2-compliance output. The failure
> messages expect you to look at the v4l2-compliance source code
Hello everyone,
as promised, I've finally implemented the missing raw video feature for
the SUR40 touchscreen. Since this is a bit of a weird hybrid device
(multitouch input as well as video), I'm hoping for comments from both
communities (linux-input and linux-media). I'm also attaching the full
On 15.12.2014 23:34, Hans Verkuil wrote:
> On 12/15/2014 11:15 PM, Florian Echtler wrote:
>> On 15.12.2014 17:01, Hans Verkuil wrote:
>>> On 12/15/2014 04:47 PM, Florian Echtler wrote:
>>> Why on earth is sur40_poll doing anything with video buffers? That's
>>
Hello Hans,
On 15.12.2014 17:01, Hans Verkuil wrote:
> On 12/15/2014 04:47 PM, Florian Echtler wrote:
>> However, I'm running into an issue I have a hard time understanding. In
>> particular, as soon as I load the kernel module, I'm getting a kernel
>> oops (NULL p
Hi everyone,
I'm currently working on adding raw sensor video support for the Samsung
SUR40 touchscreen. I've finally found some useful documentation about
videobuf2, and added the required functions to the driver (without
actually delivering data so far, I just wanted to try and stream empty
fram
Hello everyone,
I'm preparing to finally add support for the raw sensor video stream to
my driver for the SUR40 touchscreen. However, after an extensive amount
of Googling, I'm still not clear on the relationship between DMA
transfers, the USB core and the videobuf2 framework.
Specifically, I'd l
Hello everyone,
I've installed the latest & greatest v4l drivers from
http://linuxtv.org/hg/~jfrancois/gspca/ and tried to use the camera on a
Samsung Q1 Ultra with them. The camera reports as
Bus 001 Device 005: ID 0ac8:c301 Z-Star Microelectronics Corp.
and the gspca_vc032x driver recognizes
98 matches
Mail list logo
