From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hemanth V" Subject: Re: Sensor event related attribute naming. Date: Fri, 24 Sep 2010 16:04:25 +0530 Message-ID: <03d301cb5bd4$152287d0$LocalHost@wipblrx0099946> References: <4C98C7FE.4050305@cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: Sender: linux-kernel-owner@vger.kernel.org To: Jonathan Cameron , LKML , linux-iio@vger.kernel.org, linux-input@vger.kernel.org, Dmitry Torokhov , Manuel Stah List-Id: linux-input@vger.kernel.org ----- Original Message ----- From: "Jonathan Cameron" > > 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. > > ___, where > : name of the channel, i.e. accel_x0 > : thresh, mag, roc > : rising, falling > : 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