[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AAA12EC.1090204@cam.ac.uk>
Date: Fri, 11 Sep 2009 10:05:48 +0100
From: Jonathan Cameron <jic23@....ac.uk>
To: Jean Delvare <khali@...ux-fr.org>
CC: Zhang Rui <rui.zhang@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"alan@...ux.intel.com" <alan@...ux.intel.com>,
"lenb@...nel.org" <lenb@...nel.org>, "pavel@....cz" <pavel@....cz>,
"Cory T. Tusar" <ctusar@...eon-central.com>,
"Trisal, Kalhan" <kalhan.trisal@...el.com>,
linux-acpi <linux-acpi@...r.kernel.org>
Subject: Re: RFC: Light sensors, unifying current options?
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists