[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03d301cb5bd4$152287d0$LocalHost@wipblrx0099946>
Date: Fri, 24 Sep 2010 16:04:25 +0530
From: "Hemanth V" <hemanthv@...com>
To: "Jonathan Cameron" <jic23@....ac.uk>,
"LKML" <linux-kernel@...r.kernel.org>, <linux-iio@...r.kernel.org>,
<linux-input@...r.kernel.org>, "Dmitry Torokhov" <dtor@...l.ru>,
"Manuel Stahl" <manuel.stahl@....fraunhofer.de>,
"Jean Delvare" <khali@...ux-fr.org>, "Greg KH" <greg@...ah.com>,
"Alan Cox" <alan@...rguk.ukuu.org.uk>,
"Andrew Morton" <akpm@...ux-foundation.org>, <drivers@...log.com>,
<achew@...dia.com>, "Donggeun Kim" <dg77.kim@...sung.com>
Subject: Re: Sensor event related attribute naming.
----- Original Message -----
From: "Jonathan Cameron" <jic23@....ac.uk>
<snip>
>
> We have had naming conventions in IIO for a while but they have not
> yet been terribly satisfactory. Our latest suggestion, which I'm
> finally happy is general enough whilst remaining clear to be found
> in http://marc.info/?l=linux-iio&m=128394796116223&w=2
>
> Manuel Stahl pointed out that the following summary covers what was
> proposed in a clearer fashion.
>
> <channel>_<limit>_<dir>_<attr>, where
> <channel>: name of the channel, i.e. accel_x0
> <limit>: thresh, mag, roc
> <dir>: rising, falling
> <attr>: en, value, period, mean_period
>
Jonathan, I am trying to understand howto apply this to cma3000. I
have few parameters like below. Would you be able to suggest how
the sysfs entries should look like for the below parameters or are these
still to be defined.
grange: 2000, 8000 mg
sampling frequency : 40, 100, 400 Hz
Modes : Motion detect, Measurement, Free fall
Thanks
Hemanth
--
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