From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Arce, Abraham" <x0066660@ti.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: Dual touchscreen implementation
Date: Fri, 13 Aug 2010 00:50:48 -0700 [thread overview]
Message-ID: <20100813075047.GA7700@core.coreip.homeip.net> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A53043F6195B1@dlee03.ent.ti.com>
Hi,
On Tue, Aug 10, 2010 at 06:16:27PM -0500, Arce, Abraham wrote:
> Hi,
>
> I am working in a board with dual display/touchscreen. I have searched within drivers/input/touchscreen for some examples on how to implement the functionality to configure driver and behave as a single touchscreen if 2 sensors are present, no specific example found
>
> My idea is to create an attribute "virtualized" to enable/disable virtualization in the second touchscreen
>
> + static DEVICE_ATTR(virtualized, S_IRUGO | S_IWUSR,
> + syn_show_attr_virtualized, syn_store_attr_virtualized);
>
>
> In the function which reports the values to input subsystem we can then decide to make the second one as an extension of the first touchscreen if
>
> * virtualized is set to 1
> * and touchscreen sensor is the second one
>
>
> + if (ts->virtualized && dev_name(&sensor->dev == '2')
> + data->x = ts->touch_caps.max_x + d->x;
> [..]
> + input_report_abs(idev, ABS_x, data->x);
>
>
> I'd appreciate any comments on this approach...
>
Does the kernel have to do that? I'd say it is userspace task to
[re]interpret events.
--
Dmitry
next prev parent reply other threads:[~2010-08-13 7:50 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 [this message]
2010-08-13 8:40 ` Arce, Abraham
2010-08-17 14:06 ` Murphy, Dan
2010-08-20 5:01 ` Dmitry Torokhov
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=20100813075047.GA7700@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.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).