All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Jonathan Cameron <jic23@cam.ac.uk>, linux-input@vger.kernel.org
Cc: "AnilKumar, Chimata" <anilkumar@ti.com>,
	"greg@kroah.com" <greg@kroah.com>,
	"eric.piel@tremplin-utc.net" <eric.piel@tremplin-utc.net>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital
Date: Wed, 18 Jan 2012 17:11:15 +0000	[thread overview]
Message-ID: <201201181711.15751.arnd@arndb.de> (raw)
In-Reply-To: <b659db7b-2ef1-49b8-9752-a0601226cc6e@email.android.com>

On Wednesday 18 January 2012, Jonathan Cameron wrote:
> Arnd Bergmann <arnd@arndb.de> wrote:
>
> >Any opinions where they should live? input, iio or a new subsystem?
> >
> Personal thought is that straight 3d devices very directed at input
> should go there. Iio has a few wrinkles left for the in kernel
> interfaces needed for a bridge to input. For starters the pull 
> and push data interfaces have not merged yet (in staging) and we
> have not started on in kernel acess to non data events yet(thresholds).
> Still happy to take them when we can support usecases fully. 

Ok, thanks for the information, sounds all reasonable. I think we
can definitely say no to new accelerometer drivers in drivers/misc
then and refer them to iio and input.

In case of lis33ldlh, I would like to see it move out at some point
once the necessary parts of iio have graduated out of staging.
Hopefully it won't be a large amount of work to convert it to
a different internal API.

AnilKumar, what are the existing users of the driver? Is it still
possible to convert them to use iio without causing problems for
people that rely on this driver, or do we have to keep supporting the
current interface?

	Arnd

  reply	other threads:[~2012-01-18 17:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1324617892-14576-1-git-send-email-anilkumar@ti.com>
2011-12-23 11:18 ` [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital Mark Brown
2011-12-28  9:14   ` AnilKumar, Chimata
2012-01-17  7:32 ` AnilKumar, Chimata
2012-01-17 10:54   ` Mark Brown
2012-01-17 16:03     ` greg
2012-01-18  5:48       ` AnilKumar, Chimata
2012-01-17 23:47   ` Andrew Morton
2012-01-18  7:51     ` AnilKumar, Chimata
2012-01-18 14:03   ` Arnd Bergmann
2012-01-18 14:43     ` Jean Delvare
2012-01-18 14:49       ` Arnd Bergmann
2012-01-18 15:00         ` Jean Delvare
2012-01-18 16:47     ` Jonathan Cameron
2012-01-18 17:11       ` Arnd Bergmann [this message]
2012-01-19  5:30         ` AnilKumar, Chimata
2012-01-19  5:30           ` AnilKumar, Chimata
2012-01-19 17:10           ` Arnd Bergmann
2012-01-19 17:29             ` Mark Brown
2012-07-25  8:57             ` AnilKumar, Chimata
2012-07-25  8:57               ` AnilKumar, Chimata
2012-01-18 21:36     ` Andi
2012-01-19 14:26       ` Arnd Bergmann
2012-01-19 17:15         ` Jonathan Cameron
2012-01-19 17:15           ` Jonathan Cameron

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=201201181711.15751.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=anilkumar@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.piel@tremplin-utc.net \
    --cc=greg@kroah.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.