From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Felipe Balbi <me@felipebalbi.com>, Hemanth V <hemanthv@ti.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, igor.stoppa@nokia.com,
kai.svahn@nokia.com, mathias.nyman@nokia.com
Subject: Re: Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver)
Date: Tue, 31 Aug 2010 10:53:37 +0100 [thread overview]
Message-ID: <20100831105337.7ba1dcaa@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100830205011.GB28711@core.coreip.homeip.net>
> > My hope is that we can make use of a well known and uniform
> > API for all input devices in a device, be it a keypad,
> > touchscreen, accelerometer, magnetometer, gyro, or whatever.
> >
>
> If only we could agree what input devices are...
Is that the right test for some of these devices.
Surely the question is "what devices can be meaningfully represented by
the input API".
The device range is always going to be quite large and people want to use
the API because it means things just work. They can wire their home made
surfboard unit and tilt sensors up to the PC and tuxracer just goes. They
can wire pedals and a current meter to it and use it as the speed input in
bzflag to simulate bicycle tanks etc..
Alan
next prev parent reply other threads:[~2010-08-31 9:35 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 6:52 [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver Hemanth V
2010-05-21 11:57 ` Jonathan Cameron
2010-05-21 14:13 ` Hemanth V
2010-08-13 12:47 ` Hemanth V
2010-08-13 13:34 ` Murphy, Dan
2010-08-16 9:45 ` Hemanth V
2010-08-29 18:24 ` Dmitry Torokhov
2010-08-29 18:49 ` Dmitry Torokhov
2010-08-30 16:04 ` Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver) Felipe Balbi
2010-08-30 16:28 ` Dmitry Torokhov
2010-08-30 17:10 ` Felipe Balbi
2010-08-30 17:21 ` Dmitry Torokhov
2010-08-30 18:52 ` Felipe Balbi
2010-08-30 20:50 ` Dmitry Torokhov
2010-08-31 9:53 ` Alan Cox [this message]
2010-08-30 17:41 ` Jonathan Cameron
2010-08-30 20:40 ` Alan Cox
2010-08-30 20:44 ` Dmitry Torokhov
2010-08-30 21:28 ` Linus Torvalds
2010-08-30 21:43 ` Dmitry Torokhov
2010-08-30 22:05 ` Linus Torvalds
2010-08-30 22:43 ` Dmitry Torokhov
2010-08-31 5:15 ` Felipe Balbi
2010-08-31 9:44 ` Alan Cox
2010-08-31 12:35 ` Jonathan Cameron
2010-08-31 16:17 ` Dmitry Torokhov
2010-08-31 16:59 ` Alan Cox
2010-08-31 17:09 ` Dmitry Torokhov
2010-08-31 17:24 ` Mohamed Ikbel Boulabiar
2010-08-31 18:14 ` Jonathan Cameron
2010-08-31 22:21 ` Chris Hudson
2010-09-24 13:02 ` Pavel Machek
2010-09-24 13:26 ` Jonathan Cameron
2010-08-31 18:03 ` Jonathan Cameron
2010-08-31 18:20 ` Jonathan Cameron
2010-09-14 7:12 ` Pavel Machek
2010-08-31 9:46 ` Alan Cox
2010-08-31 12:51 ` Jonathan Cameron
2010-08-31 18:18 ` Daniel Barkalow
2010-09-03 10:32 ` [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver Hemanth V
2010-09-03 16:34 ` Dmitry Torokhov
2010-09-06 9:03 ` Hemanth V
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=20100831105337.7ba1dcaa@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=hemanthv@ti.com \
--cc=igor.stoppa@nokia.com \
--cc=kai.svahn@nokia.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mathias.nyman@nokia.com \
--cc=me@felipebalbi.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
all inboxes | Powered by JetHome®