linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Murphy, Dan" <dmurphy@ti.com>
Cc: "Arce, Abraham" <x0066660@ti.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: Dual touchscreen implementation
Date: Thu, 19 Aug 2010 22:01:11 -0700	[thread overview]
Message-ID: <20100820050109.GA12243@core.coreip.homeip.net> (raw)
In-Reply-To: <C9D59C82B94F474B872F2092A87F261412470D10F6@dlee07.ent.ti.com>

Hi Dan,

On Tue, Aug 17, 2010 at 09:06:00AM -0500, Murphy, Dan wrote:
> Abraham
>
> My thoughts would be similar to Dmitry's.  We should let the user
> space figure it out.  Then the application itself can combine and
> render the touches as a contiguous touch screen or as an independent
> touch.
> 
> But we would probably need a way for the kernel driver to identify
> which touch controller that the information came from.
> 
> For multi touch we may be able to use ABS_MT_TRACKING_ID for passing
> up the controller ID but there is not really a good code for the
> standard ABS axes.  Maybe we can make one called ABS_TRACKING_ID to
> keep with the theme.
> 
> This way the user space and use that to know where it came from.
> 
> Or Dmitry if you have any patches or thoughts let me know.
> 

I am confused - you should have 2 device nodes for each pf your
controllers and so you should be able to figure out what device
particular event is coming from. What am I missing here?

Thanks.

-- 
Dmitry

      reply	other threads:[~2010-08-20  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 23:16 Dual touchscreen implementation Arce, Abraham
2010-08-13  7:50 ` Dmitry Torokhov
2010-08-13  8:40   ` Arce, Abraham
2010-08-17 14:06     ` Murphy, Dan
2010-08-20  5:01       ` Dmitry Torokhov [this message]

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=20100820050109.GA12243@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=dmurphy@ti.com \
    --cc=linux-input@vger.kernel.org \
    --cc=x0066660@ti.com \
    /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).