From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"alan@linux.intel.com" <alan@linux.intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"pavel@ucw.cz" <pavel@ucw.cz>,
"Cory T. Tusar" <ctusar@videon-central.com>,
"Trisal, Kalhan" <kalhan.trisal@intel.com>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: RFC: Light sensors, unifying current options?
Date: Fri, 11 Sep 2009 10:05:48 +0100 [thread overview]
Message-ID: <4AAA12EC.1090204@cam.ac.uk> (raw)
In-Reply-To: <20090911092049.70887ad0@hyperion.delvare>
Jean Delvare wrote:
> On Fri, 11 Sep 2009 09:55:01 +0800, Zhang Rui wrote:
>> On Thu, 2009-09-10 at 18:05 +0800, Jonathan Cameron wrote:
>>> Some sensors, e.g. tsl2561 use an internal clock to do sampling and hence
>>> have some predefined period in which the reading taken doesn't change.
>>> Perhaps exporting said period would be useful to userspace?
>>>
>> I don't think so.
>> IMO, the tsl2561 driver should handle this, and there is no need to
>> annoy the user space.
>> i.e. users always assume the content of "illuminance" attribute is
>> valid, and it's the driver's job to make this true. We don't need to
>> document this.
>
> I agree with Rui on this. Let's not delegate everything to user-space,
> otherwise it's pointless to write kernel drivers in the first place.
Agreed, if anyone has an application they can add the relevant hooks when
they need them.
next prev parent reply other threads:[~2009-09-11 9:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 13:51 RFC: Light sensors, unifying current options? Jonathan Cameron
2009-09-07 5:26 ` Trisal, Kalhan
2009-09-07 7:28 ` Pavel Machek
2009-09-07 7:32 ` RFC: " Zhang Rui
2009-09-07 8:10 ` Corentin Chary
2009-09-07 11:42 ` Jonathan Cameron
2009-09-09 3:41 ` Zhang Rui
2009-09-09 11:28 ` Jonathan Cameron
2009-09-10 1:34 ` Zhang Rui
2009-09-10 8:23 ` Pavel Machek
2009-09-10 10:10 ` Jonathan Cameron
2009-09-10 10:05 ` Jonathan Cameron
2009-09-11 1:55 ` Zhang Rui
2009-09-11 7:20 ` Jean Delvare
2009-09-11 9:05 ` Jonathan Cameron [this message]
2009-09-11 9:22 ` 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=4AAA12EC.1090204@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=alan@linux.intel.com \
--cc=ctusar@videon-central.com \
--cc=kalhan.trisal@intel.com \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rui.zhang@intel.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