mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: 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 17:59:37 +0100	[thread overview]
Message-ID: <20100831175937.70a59a91@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100831161730.GA30947@core.coreip.homeip.net>

> > 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.
> 
> Would there even be an argument which subsystem to use if IIO->input
> bridge existed today? Because if the answer is "no" then push into input
> is driven by convenience and not because it is the right solution. 

Probably because most of these devices have nothing to do with industrial
I/O at all.

> If application does take something as an input it does not make it
> necessarily a human interface device. By this reasoning cameras should
> be represented as an input devices (why, some applications take input

That's not what I asked. 

> I really believe that input should represent purely human interface
> devices, not arbitrary data acquisition devices.

That tends to make little sense where the API is the same and
applications benefit enormously from consistency. I'd rather have an
input->IIO bridge because that is the real world today !

The question is what does the API make *sense* for. Not what can you use
the API for. Unix (and Linux) are enormously powerful because of the use
of common interfaces and APIs.

So a voltmeter really makes no sense. It's not a set of keys and it
doesn't give X/Y/Z style readings. Nor does a camera. But a lot of things
do fit this to varying degrees.

I'm actually more dubious than Linus about ALS - because ALS tends not
produce 'events' but to be sampled, and there are significant power
implications to unnecessary polling.

See it as a curse of success - because you got the API right and made it
flexible people want to use it. And the more it's used the less special
code is needed in user or kernel space for PDAs and phones - instead they
just work.

> > In a game
> > context can I suggest the Zombies game is an example ?
> 
> I am not familiar with this game, sorry.

It uses GPS and networking to stage an 'in real world' zombie dodging
game.

Alan

  reply	other threads:[~2010-08-31 16:42 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
2010-08-31 16:17                   ` Dmitry Torokhov
2010-08-31 16:59                     ` Alan Cox [this message]
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=20100831175937.70a59a91@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=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®