Messages in this thread | | | Subject | Re: Touch processing on host CPU | From | Jonathan Cameron <> | Date | Fri, 17 Oct 2014 17:33:01 +0100 |
| |
On October 17, 2014 11:42:10 AM GMT+01:00, Nick Dyer <nick.dyer@itdev.co.uk> wrote: >Hi- > >I'm trying to find out which subsystem maintainer I should be talking >to - >apologies if I'm addressing the wrong people. > >There is a model for doing touch processing where the touch controller >becomes a much simpler device which sends out raw acquisitions (over >SPI >at up to 1Mbps + protocol overheads). All touch processing is then done >in >user space by the host CPU. An example of this is NVIDIA DirectTouch - >see: >http://blogs.nvidia.com/blog/2012/02/24/industry-adopts-nvidia-directtouch/ > >In the spirit of "upstream first", I'm trying to figure out how to get >a >driver accepted. Obviously it's not an input device in the normal >sense. Is >it acceptable just to send the raw touch data out via a char device? Is >there another subsystem which is a good match (eg IIO)?
Possibly... > Does the >protocol >(there is ancillary/control data as well) need to be documented?
Do you know of a suitable ADC frontend? Preferably with docs. Interesting bit is the data format and these ancillary parts. > >cheers
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
| |