[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A82E1F59-BB34-40EA-A13F-456EBCC0519D@kernel.org>
Date: Fri, 17 Oct 2014 17:33:01 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Nick Dyer <nick.dyer@...ev.co.uk>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Greg KH <greg@...ah.com>
CC: "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Touch processing on host CPU
On October 17, 2014 11:42:10 AM GMT+01:00, Nick Dyer <nick.dyer@...ev.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists