linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Felipe Balbi <me@felipebalbi.com>
Cc: 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, matthias.nyman@nokia.com
Subject: Re: Sensors and the input layer (was Re: [RFC] [PATCH V2 1/2] input: CMA3000 Accelerometer driver)
Date: Mon, 30 Aug 2010 09:28:56 -0700	[thread overview]
Message-ID: <20100830162855.GA17325@core.coreip.homeip.net> (raw)
In-Reply-To: <36abcb34cfbf34724d9a581a75b53e76@secure211.sgcpanel.com>

Hi Felipe,

On Mon, Aug 30, 2010 at 11:04:39AM -0500, Felipe Balbi 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 got persuaded that 3-axis accelerometers are most often indended to be
used as input devices so I decided I should take these in (adxl134x is
there). I still think that sensor devices in general are better suited
to IIO subsystem and I hope it will get out of staging soon.

Once it is out of staging we may think about creating a IIO-to-input
bridge (copuld be either in kernel or a userspace solution based on
uinput) to route sensors that are indeed used as HIDs.

Hope this makes sense.

-- 
Dmitry

  reply	other threads:[~2010-08-30 16:28 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 [this message]
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
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=20100830162855.GA17325@core.coreip.homeip.net \
    --to=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 \
    /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;
as well as URLs for NNTP newsgroup(s).