On 02/06/2016 16:14, Nick Dyer wrote:
> On 01/06/2016 19:17, Dmitry Torokhov wrote:
>> On Wed, Jun 01, 2016 at 05:39:44PM +0100, Nick Dyer wrote:
>>> This is a series of patches to add diagnostic data support to the Atmel
>>> maXTouch driver. It's a rewrite of the pr
On 27/05/2016 13:38, Hans Verkuil wrote:
> On 05/04/2016 07:07 PM, Nick Dyer wrote:
>> +V4L2_PIX_FMT_YS16
>> +Grey-scale image
>> +
>> +
>> +Description
>> +
>> +This is a signed grey-scale image with a depth of 16 bits per
&
On 27/05/2016 14:18, Hans Verkuil wrote:
> On 05/27/2016 02:52 PM, Nick Dyer wrote:
>> On 27/05/2016 13:38, Hans Verkuil wrote:
>>> On 05/04/2016 07:07 PM, Nick Dyer wrote:
>>>> +V4L2_PIX_FMT_YS16
>>>> +Grey-scale ima
Hi Dmitry-
On 01/06/2016 19:17, Dmitry Torokhov wrote:
> On Wed, Jun 01, 2016 at 05:39:44PM +0100, Nick Dyer wrote:
>> This is a series of patches to add diagnostic data support to the Atmel
>> maXTouch driver. It's a rewrite of the previous implementation which output
>> v
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <nick.d...@itdev.co
ame it. For what it's worth,
Synaptics RMI4 also emits 16 bit signed, see
https://github.com/wanam/Adam-Kernel-GS4/blob/master/drivers/input/touchscreen/rmi_f54.c#L1831
> On 05/04/2016 07:07 PM, Nick Dyer wrote:
> BTW, did you run v4l2-compliance? I think it should work if you just do:
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/Kconfig| 2 +
drivers/input/touchscreen/atmel_mxt_ts.c | 247 +++
2 files changed, 249 insertions(+)
diff --git a/d
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 29 ++---
1 file changed, 26 insertions(+), 3 deletions(-)
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 58
1 file changed, 51 insertions(+), 7 del
This is a series of patches to add diagnostic data support to the Atmel
maXTouch driver. It's a rewrite of the previous implementation which output via
debugfs: it now uses a V4L2 device in a similar way to the sur40 driver.
There are significant performance advantages to putting this code into
This will be used for output of raw touch delta data. This format is
used by Atmel maXTouch (atmel_mxt_ts) and also Synaptics RMI4.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
Documentation/DocBook/media/v4l/pixfmt-ys16.xml | 79 +
Documentation/DocBook/med
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
capture software from treating them as webcams.
Signed-off-by: Nick Dyer <nic
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touch
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:
>>> Some touch controllers send out raw touch data in a similar way to a
>>> greyscale frame grabber. Add a new device type for these device
On 20/06/2016 17:09, Hans Verkuil wrote:
> On 06/17/2016 04:16 PM, Nick Dyer wrote:
>> @@ -2325,11 +2344,20 @@ static int mxt_vidioc_querycap(struct file *file,
>> void *priv,
>> static int mxt_vidioc_enum_input(struct file *file, void *priv,
>>
On 20/06/2016 17:20, Hans Verkuil wrote:
> On 06/17/2016 04:16 PM, Nick Dyer wrote:
>> +static int rmi_f54_vidioc_enum_input(struct file *file, void *priv,
>> + struct v4l2_input *i)
>> +{
>> +struct f54_data *f54 = video_
On 22/06/2016 21:38, Florian Echtler wrote:
> 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:
>>>>>
>>>>&g
- V4L2_TCH_FMT_DELTA_TD08 for signed 16-bit touch deltas
- V4L2_TCH_FMT_TU16 for unsigned 16-bit touch data
- V4L2_TCH_FMT_TU08 for unsigned 8-bit touch data
This support will be used by:
* Atmel maXTouch (atmel_mxt_ts)
* Synaptics RMI4.
* sur40
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
Documen
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/Kconfig| 6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 244 +++
2 files changed, 248 insertions(+), 2 deletions(-)
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <nick.d...@itdev.co
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/Kconfig
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/rmi4/Kconfig | 11 +
drivers/inpu
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touch
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 58
1 file changed, 51 insertions(+), 7 del
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/sur40.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/input/touchscreen/sur40.c
b/drivers/input/touchscreen/sur40.c
index 880c40b..841e045 100644
--- a/drivers
Hi Hans-
On 20/06/2016 12:00, Hans Verkuil wrote:
> On 06/17/2016 04:16 PM, Nick Dyer wrote:
>> This will be used for output of raw touch delta data. This format is
>> used by Atmel maXTouch (atmel_mxt_ts) and also Synaptics RMI4.
>>
>> Signed-off-by: Nick
On 22/06/2016 23:08, Nick Dyer wrote:
> Some touch controllers send out touch data in a similar way to a
> greyscale frame grabber.
>
> Use a new device prefix v4l-touch for these devices, to stop generic
> capture software from treating them as webcams.
&
This will be used for output of raw touch delta data. This format is
used by Atmel maXTouch (atmel_mxt_ts) and also Synaptics RMI4.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
Documentation/DocBook/media/v4l/pixfmt-ys16.xml | 79 +
Documentation/DocBook/med
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touch
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/rmi4/Kconfig | 11 +
drivers/inpu
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <nick.d...@itdev.co
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 58
1 file changed, 51 insertions(+), 7 del
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
capture software from treating them as webcams.
Signed-off-by: Nick Dyer <nic
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/Kconfig| 6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 244 +++
2 files changed, 248 insertions(+), 2 deletions(-)
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/Kconfig
On 22/04/2016 15:45, Mauro Carvalho Chehab wrote:
> Em Fri, 22 Apr 2016 10:26:37 +0200
> Hans Verkuil <hverk...@xs4all.nl> escreveu:
>> On 04/21/2016 11:31 AM, Nick Dyer wrote:
>>> This is a series of patches to add diagnostic data support to the Atmel
>>
On 22/04/2016 16:44, Mauro Carvalho Chehab wrote:
>> On the other hand, it would be a good place to tell the user that it
>> is from a touch sensor.
>>
>> Using the upcoming metadata feature wouldn't work since there is no width
>> and height in the metadata format.
>>
>> I wonder what others
on it.
best regards
Nick
On 04/05/2016 18:07, Nick Dyer wrote:
> This is a series of patches to add diagnostic data support to the Atmel
> maXTouch driver. It's a rewrite of the previous implementation which output
> via
> debugfs: it now uses a V4L2 device in a similar way to the
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/Kconfig| 2 +
drivers/input/touchscreen/atmel_mxt_ts.c | 271 +++
2 files changed, 273 insertions(+)
diff --git a/d
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
capture software from treating them as webcams.
Signed-off-by: Nick Dyer <nic
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/drivers/input/touch
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <nick.d...@itdev.co
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 29 ++---
1 file changed, 26 insertions(+), 3 deletions(-)
This is a series of patches to add diagnostic data support to the Atmel
maXTouch driver. It's a rewrite of the previous implementation which output via
debugfs: it now uses a V4L2 device in a similar way to the sur40 driver.
There are significant performance advantages to putting this code into
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 66 +++-
1 file changed, 56 insertions(+), 10 del
This will be used for output of raw touch data.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
Documentation/DocBook/media/v4l/pixfmt-ys16.xml | 79 +
Documentation/DocBook/media/v4l/pixfmt.xml | 1 +
drivers/media/v4l2-core/v4l2-ioctl.c
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c
This is a series of patches to add diagnostic data support to the Atmel
maXTouch driver. It's a rewrite of the previous implementation which output via
debugfs: it now uses a V4L2 device in a similar way to the sur40 driver.
There are significant performance advantages to putting this code into
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/drivers/input/touch
---
drivers/input/touchscreen/atmel_mxt_ts.c | 270 +++
1 file changed, 270 insertions(+)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index 0784a18..81eecf1 100644
--- a/drivers/input/touchscreen/atmel_mxt_ts.c
+++
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 36
1 file changed, 32 insertions(+), 4 del
Add function to retrieve raw references data from the diagnostic data
object
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 152 +++
1 file changed, 152 insertions(+)
diff --git a/drivers/input/touch
---
drivers/input/touchscreen/atmel_mxt_ts.c | 33
include/uapi/linux/videodev2.h | 1 +
2 files changed, 26 insertions(+), 8 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
index
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <nick.d...@itdev.co.uk>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 29 ++---
1 file changed, 26 insertions(+), 3 deletions(-)
Add support for retrieving a single node of data at high rate.
---
drivers/input/touchscreen/atmel_mxt_ts.c | 79
1 file changed, 70 insertions(+), 9 deletions(-)
diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c
b/drivers/input/touchscreen/atmel_mxt_ts.c
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <nick.d...@itdev.co
[v2: Fix minor issues and document V4L2_INPUT_TYPE_TOUCH and V4L2_CAP_TOUCH]
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
Documentation/media/uapi/mediactl/media-types.rst | 24 +++--
Documentation/media/uapi/v4l/dev-touch.rst| 56 +++
Documentation/media/ua
Signed-off-by: Nick Dyer <n...@shmanahar.org>
On 12 August 2016 10:41:08 BST, Hans Verkuil <hverk...@xs4all.nl> wrote:
>Hi Nick,
>
>On 07/18/2016 11:10 PM, Nick Dyer wrote:
>> Support both V4L2_TCH_FMT_TU08 and V4L2_PIX_FMT_GREY for backwards
>> compatibilit
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 57 ++
1 file changed, 51 insertions(+), 6 deletions(-)
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 +++---
1 file changed, 28 insertions(+), 3 deletions(-)
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <n...@shmanahar.
touch data
- V4L2_TCH_FMT_TU08 for unsigned 8-bit touch data
This support will be used by:
- Atmel maXTouch (atmel_mxt_ts)
- Synaptics RMI4.
- sur40
Signed-off-by: Nick Dyer <n...@shmanahar.org>
Tested-By: Chris Healy <cphe...@gmail.com>
---
drivers/media/media-entity.c |2
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.
---
drivers/input/touchscreen/sur40.c | 122 +++--
1 file changed, 89 insertions(+), 33
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
utils/v4l2-compliance/v4l2-compliance.cpp| 51 +-
utils/v4l2-compliance/v4l2-compliance.h |1 +
utils/v4l2-compliance/v4l2-test-input-output.cpp |4 +-
3 files changed, 53 insertions(+), 3 del
I'm leaving ITDev, so change to my personal email. My understanding is
that someone at Atmel will take this on once their takeover by Microchip
has settled down.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
MAINTAINERS |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/Kconfig|6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 245 ++
2 files changed, 249 insertions(+), 2 deletions(-)
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touch
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
Tested-by: Andrew Duggan <adug...@synaptics.com>
Tested-by:
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/Kconfig
Hi Hans-
Thanks for reviewing this again in such detail.
On 27/06/2016 12:26, Hans Verkuil wrote:
> On 06/23/2016 12:08 AM, Nick Dyer wrote:
>> This is a series of patches to add output of raw touch diagnostic data via
>> V4L2
>> to the Atmel maXTouch and Synaptics RMI
On 27/06/2016 11:25, Hans Verkuil wrote:
> Don't fill in the format description. This is now done in the V4L2 core to
> ensure
> consistent descriptions.
>
> Signed-off-by: Hans Verkuil <hans.verk...@cisco.com>
Acked-by: Nick Dyer <nick.d...@itdev.co.uk>
>
On 27/06/2016 13:22, Hans Verkuil wrote:
> On 06/27/2016 01:57 PM, Nick Dyer wrote:
> 2) Alternatively, if we want to keep using BUF_TYPE_VIDEO_CAPTURE, then:
>
> - we keep V4L2_CAP_TOUCH which is combined with CAP_VIDEO_CAPTURE (and perhaps
> VIDEO_OUTPUT in the future). The
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
Tested-by: Andrew Duggan <adug...@synaptics.com>
Tested-by:
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 +++---
1 file changed, 28 insertions(+), 3 deletions(-)
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
utils/v4l2-compliance/v4l2-compliance.cpp| 51 +-
utils/v4l2-compliance/v4l2-compliance.h |1 +
utils/v4l2-compliance/v4l2-test-input-output.cpp |4 +-
3 files changed, 53 insertions(+), 3 del
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
Documentation/DocBook/media/v4l/dev-touch.xml | 51
Documentation/DocBook/media/v4l/media-types.xml|5 ++
.../DocBook/media/v4l/pixfmt-tch-td08.xml | 66
.../DocBook/media/v4l/pixfmt-tc
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touch
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/Kconfig|6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 244 ++
2 files changed, 248 insertions(+), 2 deletions(-)
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can
Atmel maXTouch devices have a T37 object which can be used to read raw
touch deltas from the device. This consists of an array of 16-bit
integers, one for each node on the touchscreen matrix.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/Kconfig
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.
---
drivers/input/touchscreen/sur40.c | 123 +++--
1 file changed, 89 insertions(+), 34
touch data
- V4L2_TCH_FMT_TU08 for unsigned 8-bit touch data
This support will be used by:
- Atmel maXTouch (atmel_mxt_ts)
- Synaptics RMI4.
- sur40
Signed-off-by: Nick Dyer <n...@shmanahar.org>
Tested-By: Chris Healy <cphe...@gmail.com>
---
drivers/media/media-entity.c |2
I'm leaving ITDev, so change to my personal email. My understanding is
that someone at Atmel will take this on once their takeover by Microchip
has settled down.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
MAINTAINERS |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
There are different datatypes available from a maXTouch chip. Add
support to retrieve reference data as well.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 57 ++
1 file changed, 51 insertions(+), 6 deletions(-)
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <n...@shmanahar.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
utils/v4l2-compliance/v4l2-compliance.cpp| 48 +++-
utils/v4l2-compliance/v4l2-compliance.h | 1 +
utils/v4l2-compliance/v4l2-test-input-output.cpp | 4 +-
3 files changed, 51 insertions(+), 2 del
Register a video device to output T37 diagnostic data.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/Kconfig| 6 +-
drivers/input/touchscreen/atmel_mxt_ts.c | 244 +++
2 files changed, 248 insertions(+), 2 deletions(-)
touch data
- V4L2_TCH_FMT_TU08 for unsigned 8-bit touch data
This support will be used by:
- Atmel maXTouch (atmel_mxt_ts)
- Synaptics RMI4.
- sur40
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/media/media-entity.c | 2 ++
drivers/media/v4l2-core/v4l2-dev.c
Invert the diagnostic data to match the orientation of the input device.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/input/touch
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
Documentation/DocBook/media/v4l/dev-touch.xml | 51 ++
Documentation/DocBook/media/v4l/media-types.xml| 5 ++
.../DocBook/media/v4l/pixfmt-tch-td08.xml | 66 +
.../DocBook/media/v4l/pixfmt-tc
The mXT1386 family of chips have a different architecture which splits
the diagnostic data into 3 columns.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/touchscreen/atmel_mxt_ts.c | 31 ---
1 file changed, 28 insertions(+), 3 deletions(-)
diff
This is a series of patches to add output of raw touch diagnostic data via V4L2
to the Atmel maXTouch and Synaptics RMI4 drivers.
It's a rewrite of the previous implementation which output via debugfs: it now
uses a V4L2 device in a similar way to the sur40 driver.
We have a utility which can
The touchscreen may have a margin where not all the matrix is used. Read
the parameters from T9 and T100 and take account of the difference.
Note: this does not read the XORIGIN/YORIGIN fields so it assumes that
the touchscreen starts at (0,0)
Signed-off-by: Nick Dyer <n...@shmanahar.
Function 54 implements access to various RMI4 diagnostic features.
This patch adds support for retrieving this data. It registers a V4L2
device to output the data to user space.
Signed-off-by: Nick Dyer <n...@shmanahar.org>
---
drivers/input/rmi4/Kconfig | 11 +
drivers/inpu
1 - 100 of 108 matches
Mail list logo