From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Dima Zavin <dmitriyz@google.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Jonathan Cameron <kernel@jic23.retrosnub.co.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
LKML <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Amit Kucheria <amit.kucheria@verdurent.com>
Subject: Re: [GIT PULL] Ambient Light Sensors subsystem
Date: Sun, 7 Mar 2010 12:49:34 -0800 [thread overview]
Message-ID: <20100307204933.GC17727@core.coreip.homeip.net> (raw)
In-Reply-To: <404ea8001003031508p32641b2bj8781ce2b88e1f9cb@mail.gmail.com>
On Wed, Mar 03, 2010 at 03:08:29PM -0800, Dima Zavin wrote:
>
> As it came up earlier in the thread, adding an ABS_AMBIENT_LIGHT_LEVEL
> or equivalent is much simpler and provides a clean, concise, and
> useful interface to userspace.
>
> Note that for many applications, you actually get configurable
> threshold levels, and the hardware triggers an interrupt when the
> light level crosses those thresholds. This makes using an input device
> very useful, and that is in fact how we use ALS devices today. I have
> several pieces of hardware that do this, and I don't see how this new
> als subsystem helps me handle that problem. With the suggested API,
> I'll have to poll the sysfs files manually to see if they've changed
> (which is suboptimal), or still add a non-standard input device to do
> what I want.
>
OK, so from what you are saying it looks you just like the _interface_,
or transport, that input subsystem provides, not the fact that you
considering the device to be a HID-type device. If this is the case then
this indicates that we need to take another look at the proposed
interface and make sure that it allows proper poll() support.
--
Dmitry
next prev parent reply other threads:[~2010-03-07 20:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 19:41 Jonathan Cameron
2010-03-03 6:13 ` Dima Zavin
2010-03-03 9:34 ` Jean Delvare
2010-03-03 10:29 ` Dima Zavin
2010-03-03 11:02 ` Jean Delvare
2010-03-03 11:10 ` Jonathan Cameron
2010-03-03 13:07 ` Linus Walleij
2010-03-03 10:30 ` Linus Walleij
2010-03-03 11:19 ` Jonathan Cameron
2010-03-03 17:03 ` Linus Torvalds
2010-03-03 17:51 ` Jonathan Cameron
2010-03-03 18:41 ` Dmitry Torokhov
2010-03-03 18:52 ` Linus Torvalds
2010-03-03 19:07 ` Dmitry Torokhov
2010-03-03 19:33 ` Jonathan Cameron
2010-03-03 20:08 ` Jonathan Cameron
2010-03-03 22:02 ` Jean Delvare
2010-03-03 23:08 ` Dima Zavin
2010-03-04 9:22 ` Jean Delvare
2010-03-07 20:49 ` Dmitry Torokhov [this message]
2010-03-08 6:29 ` Dima Zavin
2010-03-05 7:38 ` Amit Kucheria
2010-03-05 10:58 ` Jonathan Cameron
2010-03-03 21:38 ` Dima Zavin
2010-03-03 21:51 ` Linus Torvalds
2010-03-04 11:19 ` Jonathan Cameron
2010-03-07 12:34 ` Jean Delvare
2010-03-07 12:57 ` J.I. Cameron
2010-03-08 9:58 ` Dima Zavin
2010-03-08 10:24 ` Jonathan Cameron
2010-03-07 20:42 ` Dmitry Torokhov
2010-03-08 10:00 ` Jonathan Cameron
2010-03-18 14:34 ` Jon Smirl
2010-03-03 21:56 ` Mike Chan
2010-03-03 22:05 ` Jean Delvare
2010-03-10 20:46 ` Pavel Machek
2010-03-22 0:13 ` Jan Engelhardt
2010-03-22 4:27 ` Dmitry Torokhov
2010-03-03 19:20 ` Jonathan Cameron
2010-03-03 19:29 ` Manu Abraham
2010-03-03 19:45 ` Jonathan Cameron
2010-03-03 20:08 ` Manu Abraham
2010-03-03 20:37 ` 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=20100307204933.GC17727@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=dmitriyz@google.com \
--cc=jic23@cam.ac.uk \
--cc=kernel@jic23.retrosnub.co.uk \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome