From: Jonathan Cameron <jic23@cam.ac.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dima Zavin <dmitriyz@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Amit Kucheria <amit.kucheria@verdurent.com>,
Jean Delvare <khali@linux-fr.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [GIT PULL] Ambient Light Sensors subsystem
Date: Wed, 03 Mar 2010 17:51:14 +0000 [thread overview]
Message-ID: <4B8EA192.5070108@cam.ac.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1003030859360.3627@localhost.localdomain>
Cc'ing Input list and maintainer.
>
> On Tue, 2 Mar 2010, Dima Zavin wrote:
>>
>> I definitely see the need for what you guys are trying to accomplish.
>> For example, currently, we use an input device for reporting events,
>> and a separate misc device node for control
>> (enable/disable/configure). It's definitely suboptimal, but there
>> currently isn't anything there would let us do things cleanly.
>
> I have to say, I personally don't see why something like an ambient light
> sensor _isn't_ just an input device.
>
> What's the difference between a physical "increase screen brightness" key,
> and a "ambient light sensor"? Absolutely none as far as I can tell.
>
> And for something like an X server, it sounds a lot more natural to just
> have another input device than to have yet abother event reporting
> interface.
>
> And quite frankly, the "explanations" I see in this thread for why it
> needs to be a subsystem of its own don't actually explain anything or make
> sense. They seem to boil down to "we just did it this way" without
> actually answering any of the issues brought up.
>
> Linus
>
next prev parent reply other threads:[~2010-03-03 17:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 19:41 [GIT PULL] Ambient Light Sensors subsystem 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 [this message]
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=4B8EA192.5070108@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=amit.kucheria@verdurent.com \
--cc=dmitriyz@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-input@vger.kernel.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