From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felipe Balbi Subject: Re: Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver) Date: Mon, 30 Aug 2010 13:52:18 -0500 Message-ID: <3fe11bc61e6a844b926ec4d32cec1474@secure211.sgcpanel.com> References: <15445.10.24.255.17.1274424777.squirrel@dbdmail.itg.ti.com> <20100829184904.GC26209@core.coreip.homeip.net> <36abcb34cfbf34724d9a581a75b53e76@secure211.sgcpanel.com> <20100830162855.GA17325@core.coreip.homeip.net> <20100830172143.GA28275@core.coreip.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from ns1.siteground211.com ([209.62.36.12]:39890 "EHLO serv01.siteground211.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752052Ab0H3SwQ (ORCPT ); Mon, 30 Aug 2010 14:52:16 -0400 In-Reply-To: <20100830172143.GA28275@core.coreip.homeip.net> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Dmitry Torokhov Cc: Hemanth V , 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 Hi, On Mon, 30 Aug 2010 10:21:44 -0700, Dmitry Torokhov wrote: > My response to this - are gyroscopes will _only_ be used to turn around > in a game? Are proximity sensor is _only_ usable as a trigger in FPS? > Won't we ever see such chips controlling technological processes? similarly, will accelerometers always be used as input devices ? of course not, they have been used e.g. to spin down hard disks on laptops when they are shaken too hard. Still they have quite a fair bit of usage as input devices; you've seen it yourself, right ? in the end of the day, when you put those on mobile devices like e.g. cellphones, app developers will be really keen on creating new ways for interacting with apps (be it a game or not) using those devices, so I will agree with Jonathan that, maybe, having two separate drivers for different purposes would make sense, although that might cause a bit of trouble if user ends up enabling the wrong driver when building custom kernel for his device. 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. -- balbi