[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4888796B.9070003@cam.ac.uk>
Date: Thu, 24 Jul 2008 13:45:31 +0100
From: Jonathan Cameron <jic23@....ac.uk>
To: Eric Piel <eric.piel@...mplin-utc.net>
CC: Jonathan Cameron <Jonathan.Cameron@...il.com>,
mgross@...ux.intel.com, Dmitry Torokhov <dtor@...l.ru>,
LKML <linux-kernel@...r.kernel.org>,
LM Sensors <lm-sensors@...sensors.org>,
David Brownell <david-b@...bell.net>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Jean Delvare <khali@...ux-fr.org>,
spi-devel-general@...ts.sourceforge.net,
Ben Nizette <bn@...sdigital.com>
Subject: Re: [spi-devel-general] [Patch 0/4] IndustrialIO subsystem (ADCs,
accelerometers etc)
hat done for the next
>> version (maybe driver specific for now).
> Yes, on a second though, this is a low priority point. If userspace is
> able to know if the hardware has or not freefall detection, it should be
> possible to just implement the software detection in the userspace
> daemon. People might come up with lots of "clever" algorithms for that,
> so it might be better to not do too much in the kernel ;-)
Good point; will leave that one for now.
>
>>
>> At the moment the big missing element of the subsystem is an easy way of
>> querying what is there. (proc interface similar to that for the input
>> subsystem)
> You mean /sys/class/input/, right? Indeed, something inspired by the
> input subsystem should work well.
No, I meant /proc/bus/input/devices which gives machine readable description
of all devices registered with the input subsystem and their capabilities.
Makes it easier to make userspace code reasonably generic.
--
Jonathan
--
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