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 CAP_TOUCH just
On 06/27/2016 01:57 PM, Nick Dyer wrote:
> 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
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 RMI4 drivers.
>>
>> It's a
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 RMI4 drivers.
>
> It's a rewrite of the previous implementation which output via debugfs: it now
> uses a V4L2 device in a similar
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
