From: Jonathan Cameron <jic23@cam.ac.uk>
To: linux-iio@vger.kernel.org
Subject: Re: [PATCH 10/13] staging:iio: ABI documentation (partial)
Date: Mon, 29 Mar 2010 14:55:27 +0100 [thread overview]
Message-ID: <4BB0B14F.7070700@cam.ac.uk> (raw)
In-Reply-To: <1269808879-28838-11-git-send-email-jic23@cam.ac.uk>
In the great tradition of replying to ones own patches...
...
> +
> +What: /sys/.../device[n]/device[n]:event[m]
> +KernelVersion: 2.6.35
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Configuration of which hardware generated events are passed up to
> + userspace. Some of these are a bit complex to generalize so this
> + section is a work in progress.
> +
> +What: /sys/.../device[n]:event[m]/dev
> +KernelVersion: 2.6.35
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + major:minor character device numbers for the event line.
> +
> +Taking accel_x0 as an example
> +
> +What: /sys/.../device[n]:event[m]/accel_x0_thresh[_high|_low]
> +KernelVersion: 2.6.35
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Event generated when accel_x0 passes a threshold in correction direction
> + (or stays beyond one). If direction isn't specified, either triggers it.
> + Note driver will assume last p events requested are enabled where p is
> + however many it supports. So if you want to be sure you have
> + set what you think you have, check the contents of these. Drivers
> + may have to buffer any parameters so that they are consistent when a
> + given event type is enabled a future point (and not those for whatever
> + alarm was previously enabled).
> +
> +What: /sys/.../device[n]:event[m]/accel_x0_roc[_high|_low]
> +KernelVersion: 2.6.35
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Same as above but based on the first differential of the value.
> +
> +
> +What: /sys/.../device[n]:event[m]/accel_x0[_thresh|_roc][_high|_low]_period
> +KernelVersion: 2.6.35
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + A period of time (microsecs) for which the condition must be broken
> + before an interrupt is triggered. Applies to all alarms if type is not
> + specified.
> +
> +What: /sys/.../device[n]:event[m]/accel_x0[_thresh|_roc][_high|_low]_value
> +KernelVersion: 2.6.35
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + The actual value of the threshold in raw device units obtained by
> + reverse application of scale and offfset to the acceleration in m/s^2.
> +
These names don't actually conform to those I sent out out in the RFC following the the main
ABI posting and just for a complete inconsistency the naming in lis3l02dq doesn't conform
to either version. I haven't yet checked the other drivers, but I would guess they are a random
mix of the various options as well.
Oops.
I'll fix this up for V2.
Jonathan
next prev parent reply other threads:[~2010-03-29 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 20:41 [PATCH 00/13] Staging: IIO: ABI changes round 1, V1 Jonathan Cameron
2010-03-28 20:41 ` [PATCH 01/13] staging:iio: Add new in_raw definitions for adc channels Jonathan Cameron
2010-03-28 20:41 ` [PATCH 02/13] staging:iio: Add new attrs for sampling frequency available and temp_raw Jonathan Cameron
2010-03-28 20:41 ` [PATCH 03/13] iio:staging:accelerometers move towards the new abi Jonathan Cameron
2010-03-28 20:41 ` [PATCH 04/13] staging:iio: Support functions for scan mask matching Jonathan Cameron
2010-03-28 20:41 ` [PATCH 05/13] staging: iio: Move from class to bus Jonathan Cameron
2010-03-28 20:41 ` [PATCH 06/13] staging:iio: Move event attributes into the event[n] device in sysfs Jonathan Cameron
2010-03-28 20:41 ` [PATCH 07/13] staging:iio: Clean out unused IIO_SCAN_EL and add IIO_SCAN_NAMED_EL_C Jonathan Cameron
2010-03-28 20:41 ` [PATCH 08/13] staging:iio:max1363 move to new abi Jonathan Cameron
2010-03-28 20:41 ` [PATCH 09/13] staging:iio: Documentation, update iio_utils.h for the move to a bus Jonathan Cameron
2010-03-28 20:41 ` [PATCH 10/13] staging:iio: ABI documentation (partial) Jonathan Cameron
2010-03-28 20:41 ` [PATCH 11/13] staging:iio: Directory name changes to match new ABI Jonathan Cameron
2010-03-28 20:41 ` [PATCH 12/13] staging:iio:tsl2563: change lux to illuminance0_input to match new abi Jonathan Cameron
2010-03-28 20:41 ` [PATCH 13/13] staging:iio: Remove naming via IDR's where no longer necessary under " Jonathan Cameron
2010-03-29 13:55 ` Jonathan Cameron [this message]
2010-03-30 14:31 ` [PATCH 08/13] staging:iio:max1363 move to " Jonathan Cameron
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=4BB0B14F.7070700@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-iio@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