From: Nick Dyer <nick.dyer@itdev.co.uk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Greg KH <greg@kroah.com>, Jonathan Cameron <jic23@kernel.org>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Touch processing on host CPU
Date: Fri, 17 Oct 2014 11:42:10 +0100 [thread overview]
Message-ID: <5440F282.8040306@itdev.co.uk> (raw)
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)? Does the protocol
(there is ancillary/control data as well) need to be documented?
cheers
--
Nick Dyer
Senior Software Engineer, ITDev
Fully Managed Technology Design Services
+44 (0)23 80988855 - http://www.itdev.co.uk
next reply other threads:[~2014-10-17 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 10:42 Nick Dyer [this message]
2014-10-17 16:33 ` Touch processing on host CPU Jonathan Cameron
2014-10-17 17:17 ` Dmitry Torokhov
2014-10-21 12:22 ` One Thousand Gnomes
2014-10-21 16:47 ` Nick Dyer
2014-10-22 13:20 ` One Thousand Gnomes
2014-10-22 21:15 ` Andrew de los Reyes
2014-10-21 11:01 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5440F282.8040306@itdev.co.uk \
--to=nick.dyer@itdev.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=jic23@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).