From: Mohamed Ikbel Boulabiar <boulabiar@gmail.com>
To: Kim Kyuwon <q1.kim@samsung.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
felipe.balbi@nokia.com, Kim Kyuwon <chammoru@gmail.com>,
Trilok Soni <soni.trilok@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Jean Delvare <khali@linux-fr.org>,
"Zhang, Xing Z" <xing.z.zhang@intel.com>,
"Gross, Mark" <mark.gross@intel.com>,
jketreno <jketreno@linux.intel.com>,
"Trisal, Kalhan" <kalhan.trisal@intel.com>
Subject: Re: [RFC] Add Input IOCTL for accelerometer devices
Date: Mon, 25 May 2009 09:52:27 +0100 [thread overview]
Message-ID: <45cc95260905250152h5fe350b8kbdc2333cfea3c393@mail.gmail.com> (raw)
In-Reply-To: <4A1A538F.2030003@samsung.com>
Hi,
I haven't read all documents cited here (IIO, ...), but it seems that
there is a big attention made on performance.
Can we think also in the way information can be shown for a device.
To be concrete, I actually work on some multi-touch tablets, and it is
useful to create 2 or more "views" of the device.
A device file that emulate a mouse when only one contact is on the
tablet, and another showing more general information about all
contacts.
The first is used by simple applications, the other by more advanced
ones that can treat complex multi-touch events.
This is only one use case, but like in the databases, maybe simple
user (or predefined config. by other users) can propose other "views"
of a device.
Then maybe we would need a configurator (or text configuration files)
for creating these views.
I am not also very convinced why events matching are "cabled" inside
driver source code.
The matching between information sent by device and system events
(ABS_X, ...) is inside source code and any modification needs
recompilation.
What if someone should switch between 2 different matching ?
---
ikbel
next prev parent reply other threads:[~2009-05-25 8:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090515131636.GE4443@nokia.com>
2009-05-15 18:06 ` [RFC] Add Input IOCTL for accelerometer devices Trilok Soni
2009-05-15 19:30 ` Mohamed Ikbel Boulabiar
2009-05-15 20:02 ` Felipe Balbi
2009-05-16 4:19 ` Mohamed Ikbel Boulabiar
2009-05-16 12:50 ` Felipe Balbi
2009-05-18 7:45 ` Kim Kyuwon
2009-05-18 9:12 ` Felipe Balbi
2009-05-18 10:11 ` Jonathan Cameron
2009-05-18 10:31 ` Felipe Balbi
2009-05-18 11:37 ` Jonathan Cameron
2009-05-19 6:32 ` Kim Kyuwon
2009-05-21 11:42 ` Jonathan Cameron
2009-05-22 8:21 ` Kim Kyuwon
2009-05-22 13:35 ` Jonathan Cameron
2009-05-25 8:15 ` Kim Kyuwon
2009-05-25 8:52 ` Mohamed Ikbel Boulabiar [this message]
2009-05-25 11:07 ` Jonathan Cameron
2009-05-19 2:41 ` Kim Kyuwon
2009-05-19 10:42 ` Felipe Balbi
2009-05-19 12:34 ` Mohamed Ikbel Boulabiar
2009-05-21 10:21 ` Jonathan Cameron
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=45cc95260905250152h5fe350b8kbdc2333cfea3c393@mail.gmail.com \
--to=boulabiar@gmail.com \
--cc=chammoru@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=felipe.balbi@nokia.com \
--cc=jic23@cam.ac.uk \
--cc=jketreno@linux.intel.com \
--cc=kalhan.trisal@intel.com \
--cc=khali@linux-fr.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=q1.kim@samsung.com \
--cc=soni.trilok@gmail.com \
--cc=xing.z.zhang@intel.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).