From: "Hemanth V" <hemanthv@ti.com>
To: Jonathan Cameron <jic23@cam.ac.uk>,
LKML <linux-kernel@vger.kernel.org>,
linux-iio@vger.kernel.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dtor@mail.ru>,
Manuel Stah
Subject: Re: Sensor event related attribute naming.
Date: Fri, 24 Sep 2010 16:04:25 +0530 [thread overview]
Message-ID: <03d301cb5bd4$152287d0$LocalHost@wipblrx0099946> (raw)
In-Reply-To: 4C98C7FE.4050305@cam.ac.uk
----- Original Message -----
From: "Jonathan Cameron" <jic23@cam.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
next prev parent reply other threads:[~2010-09-24 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 14:58 RFC: Sensor event related attribute naming Jonathan Cameron
2010-09-24 10:34 ` Hemanth V [this message]
2010-09-24 11:58 ` Jonathan Cameron
2010-09-27 9:42 ` Jonathan Cameron
2010-09-30 10:06 ` Jonathan Cameron
2010-11-08 14:07 ` Hemanth V
-- strict thread matches above, loose matches on Subject: below --
2010-11-12 10:04 Hemanth V
2010-11-12 15:03 ` Greg KH
2010-11-12 17:32 ` Dmitry Torokhov
2010-11-15 6:40 ` Hemanth V
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='03d301cb5bd4$152287d0$LocalHost@wipblrx0099946' \
--to=hemanthv@ti.com \
--cc=dtor@mail.ru \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).