From: Jonathan Cameron <kernel@jic23.retrosnub.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Felipe Balbi <me@felipebalbi.com>, Hemanth V <hemanthv@ti.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"igor.stoppa@nokia.com" <igor.stoppa@nokia.com>,
"kai.svahn@nokia.com" <kai.svahn@nokia.com>,
"matthias.nyman@nokia.com" <matthias.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 13:35:49 +0100 [thread overview]
Message-ID: <4C7CF725.50503@jic23.retrosnub.co.uk> (raw)
In-Reply-To: <20100831104446.321fd4f4@lxorguk.ukuu.org.uk>
On 08/31/10 10:44, Alan Cox wrote:
>> 1. Input transport via evdev is very convenient
>> 2. There is no other standard alternative
>>
>> Once there is standard interface for such sensors they will happily use
>> it and will not look back.
>
> I think the fact that most of the interest in IIO is "how do we make an
> IIO/Input bridge" speaks volumes.
It isn't. Most of the interest on LKML might be, but that is because all
of those interested in the 'industrial' side of things are keeping
their discussion on linux-iio@vger list. Most of the noise on LKML may
be on the input bridge side, but most of the actual work and current
developers / users are not. The needs we have are not all met by input,
(and nor should they be) hence the reason IIO exists.
Take a look at the work Analog have been doing with it. There are
few devices in their set that would fall into the blurred area we are
debating here. 3 phase energy meters for input anyone?
>
>> Sure, for a particular cell phone there is no ambiguity, the sensor has
>> certain functionality assigned that is well known. But does this mean
>> that we should not expect parts being reused at all anymore?
>
> If non-input uses later need non-input interfaces they can switch to that
> with an input bridge when there is one and when it happens, which
> probably won't.
I guess I'll just have to write the bridge :) To put in userspace
code for a particular device should be trivial. It may take a little
more time and thought to get a configurable general version in place.
It may not be the right option for some devices, but it will provide
a means if someone wants to take one of Analog's rather nice IMU's
or a 200G accelerometer and use it to drive their gaming rig ;)
Also, there are always devices using analog sensors connected to
much more general purpose ADCs to further blur the boundaries.
There has to be divide somewhere. Dmitry is merely trying to avoid
a flood of inappropriate drivers.
>
>> I am unsure how you would play a game with GPS as an input device.
>
> In a non-game context take a look at things like the British Museum
> application that allows you to view wherever you are and as it was long
> ago by fishing out a relevant photograph as you walk around. In a game
> context can I suggest the Zombies game is an example ?
>
> Alan
Jonathan
next prev parent reply other threads:[~2010-08-31 12:31 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
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 [this message]
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=4C7CF725.50503@jic23.retrosnub.co.uk \
--to=kernel@jic23.retrosnub.co.uk \
--cc=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=matthias.nyman@nokia.com \
--cc=me@felipebalbi.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®