From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
Mike Frysinger <vapier.adi@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [git pull] Input updates for 2.6.34-rc0
Date: Sat, 13 Mar 2010 00:44:19 -0800 [thread overview]
Message-ID: <20100313084419.GE22494@core.coreip.homeip.net> (raw)
In-Reply-To: <201003121555.37998.rgetz@blackfin.uclinux.org>
On Fri, Mar 12, 2010 at 03:55:37PM -0500, Robin Getz wrote:
> On Wed 10 Mar 2010 03:30, Hennerich, Michael pondered:
> > Robin Getz wrote on 2010-03-09:
> > > On Tue 9 Mar 2010 13:20, Dmitry Torokhov pondered:
> > >> On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
> > >>> On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
> > >>>> On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
> > >>>>> On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
> > >>>>>> On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger
> > > wrote:
> > > [snip]
> > >>>>> i understand the ADXL34x is a bit wonky, but what else would you
> > >>>>> propose ? or just leave the driver in limbo forever until people
> > >>>>> forget about it ?
> > >>>>
> > >>>> No, just till we have proper framework for it to be merged into.
> > >>>
> > >>> that sounds fine, but is there actually something in progress for
> > >>> that ? waiting for a framework no one is working on is the same
> > >>> in practice ...
> > >>
> > >> I have high hopes that IIO will fill the needs of these kinds of
> > > devices.
> > >
> > > The fact of things is that many people are using this as pointing device.
> > >
> > > I'm not convinced that IIO is the best place for these types of
> > > things...
> >
> > Very true - this driver was originally targeted and designed as a
> > typical human interface input device.
> >
>
> Dmitry:
>
> Care to comment? I would prefer to come to some sort of conclusion. As Mike
> said - leaving the driver in limbo forever isn't really a solution for
> anyone....
OK, you swayed my opinion about 3-axis accelerometers, I will review the
patch again (although IIRC I was pretty satisfied with it) and apply.
--
Dmitry
next prev parent reply other threads:[~2010-03-13 8:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 8:03 Dmitry Torokhov
2010-03-09 14:44 ` Mike Frysinger
2010-03-09 16:15 ` Cory Maccarrone
2010-03-09 17:53 ` Dmitry Torokhov
2010-03-09 17:51 ` Dmitry Torokhov
2010-03-09 17:58 ` Mike Frysinger
2010-03-09 18:10 ` Dmitry Torokhov
2010-03-09 18:13 ` Mike Frysinger
2010-03-09 18:20 ` Dmitry Torokhov
2010-03-09 19:39 ` Robin Getz
2010-03-10 8:30 ` Hennerich, Michael
2010-03-12 20:55 ` Robin Getz
2010-03-13 8:44 ` Dmitry Torokhov [this message]
2010-03-22 6:37 ` Dmitry Torokhov
2010-03-22 7:44 ` Mike Frysinger
2010-03-09 18:18 ` Jonathan Cameron
2010-03-09 18:21 ` Mike Frysinger
2010-03-09 19:08 ` 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=20100313084419.GE22494@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=akpm@linux-foundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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
all inboxes | Powered by JetHome®