[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <488885FB.5070500@cam.ac.uk>
Date: Thu, 24 Jul 2008 14:39:07 +0100
From: Jonathan Cameron <jic23@....ac.uk>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: Eric Piel <eric.piel@...mplin-utc.net>,
Jonathan Cameron <Jonathan.Cameron@...il.com>,
mgross@...ux.intel.com, 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)
Dmitry Torokhov wrote:
> On Thu, Jul 24, 2008 at 01:45:31PM +0100, Jonathan Cameron wrote:
>>>> 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.
>>
>
> /proc/bus/input is a legacy interface (pre-sysfs). Newer subsystems
> should try to stay in /sys/.
Ah, I'd assumed it was there to provide a centralized way of discovering
what was there. I guess it's just a matter of scanning your way through
the contents of /sys/class/input (and equivalent iio) then to find out
what is present and what is supported by each device.
Messier in a sense but guess it will work.
Ah well,
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