From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Dima Zavin <dmitriyz@google.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Jonathan Cameron <jic23@cam.ac.uk>,
torvalds@linux-foundation.org,
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: Wed, 3 Mar 2010 14:07:19 +0100 [thread overview]
Message-ID: <63386a3d1003030507l25e32ec2u92610cf40a91e538@mail.gmail.com> (raw)
In-Reply-To: <404ea8001003030229j7b22329bgd24ac39255e78bde@mail.gmail.com>
2010/3/3 Dima Zavin <dmitriyz@google.com>:
> there are plenty of
> drivers floating out there from many OEMs/vendors
Bad for them that they didn't work on integrating these to the
mainline kernel and creating proper subsystems for them
earlier.
> that are not ALSs,
> but essentially need a similar interface (e.g. proximity sensor).
I have a proximity sensor driver pending here on top of GPIO,
creating an input-on-top-of-GPIO driver framework. Too much
to do but here is the userspace interface:
diff --git a/include/linux/input.h b/include/linux/input.h
index a5802c9..cbe8a98 100644
--- a/include/linux/input.h
+++ b/include/linux/input.h
@@ -644,6 +644,7 @@ struct input_absinfo {
#define SW_RADIO SW_RFKILL_ALL /* deprecated */
#define SW_MICROPHONE_INSERT 0x04 /* set = inserted */
#define SW_DOCK 0x05 /* set = plugged into dock */
+#define SW_PROXIMITY 0x06 /* set = prox. sensor detects object */
#define SW_MAX 0x0f
#define SW_CNT (SW_MAX+1)
--
Comes in through /dev/input/event* something, simple.
I have heard about proximity sensors returning more than a binary
value, do you have one of those?
Yours,
Linus Walleij
next prev parent reply other threads:[~2010-03-03 13:07 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 [this message]
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
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=63386a3d1003030507l25e32ec2u92610cf40a91e538@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=dmitriyz@google.com \
--cc=jic23@cam.ac.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
all inboxes | Powered by JetHome®