Re: Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver)
From: Alan Cox <hidden>
Date: 2010-08-30 20:22:36
Also in:
linux-omap, lkml
From: Alan Cox <hidden>
Date: 2010-08-30 20:22:36
Also in:
linux-omap, lkml
On Mon, 30 Aug 2010 11:04:39 -0500 Felipe Balbi [off-list ref] wrote:
Hi Dmitry, When we tried to push N900's accelerometer driver as an input device you commented you didn't want sensors such as accelerometers, magnetometers, proximity, etc on the input layer because "they are not user input", although I didn't fully agree with you, we had to modify the drivers and, I believe, one of them is sitting in staging under the industrial i/o subsystem. Are you now accepting sensor drivers on the input layer ? that will make our life a lot easier but we need some definition to avoid having to re-work drivers when we want to push them to mainline.
I would certainly vote for them being input when they are sometimes used that way - compasses for example do get used by applications (like compass programs, some of the real cool visualisation tools and things like live/game mixed gaming environments) and accelerometers are gaming inputs. Proximity is also input for some stuff although usually of much more interest to the GUI manager than the GUI apps. ALS is more of a dual purpose thing -light levels are input features to the GUI on PDAs, although on many embedded devices they are most definitely part of the IIO subsystem.