Re: [PATCH v3 2/6] iio: documentation: Add ABI info for iio event persistence filter

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/04/15 01:06, Kuppuswamy Sathyanarayanan wrote:
> Add ABI info for iio event persistence filter.
> 
> Setting <n> to persistence filter would need atleast
> <n> data values outside the upper/lower threshold
> limits before generating an interrupt.
> 
> Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@xxxxxxxxxxxxxxx>
> ---
>  Documentation/ABI/testing/sysfs-bus-iio | 82 +++++++++++++++++++++++++++++++++
>  1 file changed, 82 insertions(+)
> 
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 9a70c31..590b1d4 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -856,6 +856,88 @@ Description:
>  		met before an event is generated. If direction is not
>  		specified then this period applies to both directions.
>  
Please don't mass document cases unless they are actually in use.  These should
get added as and when they become so.  Often a particular type of event
characteristic is actually only implemented on a small subset of channel types
(where it makes sense).
> +What:		/sys/.../events/in_accel_x_thresh_rising_persistence
> +What:		/sys/.../events/in_accel_x_thresh_falling_persistence
> +hat:		/sys/.../events/in_accel_x_roc_rising_persistence
> +What:		/sys/.../events/in_accel_x_roc_falling_persistence
> +What:		/sys/.../events/in_accel_y_thresh_rising_persistence
> +What:		/sys/.../events/in_accel_y_thresh_falling_persistence
> +What:		/sys/.../events/in_accel_y_roc_rising_persistence
> +What:		/sys/.../events/in_accel_y_roc_falling_persistence
> +What:		/sys/.../events/in_accel_z_thresh_rising_persistence
> +What:		/sys/.../events/in_accel_z_thresh_falling_persistence
> +What:		/sys/.../events/in_accel_z_roc_rising_persistence
> +What:		/sys/.../events/in_accel_z_roc_falling_persistence
> +What:		/sys/.../events/in_anglvel_x_thresh_rising_persistence
> +What:		/sys/.../events/in_anglvel_x_thresh_falling_persistence
> +What:		/sys/.../events/in_anglvel_x_roc_rising_persistence
> +What:		/sys/.../events/in_anglvel_x_roc_falling_persistence
> +What:		/sys/.../events/in_anglvel_y_thresh_rising_persistence
> +What:		/sys/.../events/in_anglvel_y_thresh_falling_persistence
> +What:		/sys/.../events/in_anglvel_y_roc_rising_persistence
> +What:		/sys/.../events/in_anglvel_y_roc_falling_persistence
> +What:		/sys/.../events/in_anglvel_z_thresh_rising_persistence
> +What:		/sys/.../events/in_anglvel_z_thresh_falling_persistence
> +What:		/sys/.../events/in_anglvel_z_roc_rising_persistence
> +What:		/sys/.../events/in_anglvel_z_roc_falling_persistence
> +What:		/sys/.../events/in_magn_x_thresh_rising_persistence
> +What:		/sys/.../events/in_magn_x_thresh_falling_persistence
> +What:		/sys/.../events/in_magn_x_roc_rising_persistence
> +What:		/sys/.../events/in_magn_x_roc_falling_persistence
> +What:		/sys/.../events/in_magn_y_thresh_rising_persistence
> +What:		/sys/.../events/in_magn_y_thresh_falling_persistence
> +What:		/sys/.../events/in_magn_y_roc_rising_persistence
> +What:		/sys/.../events/in_magn_y_roc_falling_persistence
> +What:		/sys/.../events/in_magn_z_thresh_rising_persistence
> +What:		/sys/.../events/in_magn_z_thresh_falling_persistence
> +What:		/sys/.../events/in_magn_z_roc_rising_persistence
> +What:		/sys/.../events/in_magn_z_roc_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_thresh_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_thresh_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_roc_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_roc_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_true_thresh_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_true_thresh_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_true_roc_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_true_roc_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_tilt_comp_thresh_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_magnetic_tilt_comp_roc_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_true_tilt_comp_thresh_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_true_tilt_comp_thresh_falling_persistence
> +What:		/sys/.../events/in_rot_from_north_true_tilt_comp_roc_rising_persistence
> +What:		/sys/.../events/in_rot_from_north_true_tilt_comp_roc_falling_persistence
> +What:		/sys/.../events/in_voltageY_supply_thresh_rising_persistence
> +What:		/sys/.../events/in_voltageY_supply_thresh_falling_persistence
> +What:		/sys/.../events/in_voltageY_supply_roc_rising_persistence
> +What:		/sys/.../events/in_voltageY_supply_roc_falling_persistence
> +What:		/sys/.../events/in_voltageY_thresh_rising_persistence
> +What:		/sys/.../events/in_voltageY_thresh_falling_persistence
> +What:		/sys/.../events/in_voltageY_roc_rising_persistence
> +What:		/sys/.../events/in_voltageY_roc_falling_persistence
> +What:		/sys/.../events/in_tempY_thresh_rising_persistence
> +What:		/sys/.../events/in_tempY_thresh_falling_persistence
> +What:		/sys/.../events/in_tempY_roc_rising_persistence
> +What:		/sys/.../events/in_tempY_roc_falling_persistence
> +What:		/sys/.../events/in_accel_x&y&z_mag_falling_persistence
> +What:		/sys/.../events/in_intensity0_thresh_persistence
> +What:		/sys/.../events/in_proximity0_thresh_persistence
> +What:		/sys/.../events/in_activity_still_thresh_rising_persistence
> +What:		/sys/.../events/in_activity_still_thresh_falling_persistence
> +What:		/sys/.../events/in_activity_walking_thresh_rising_persistence
> +What:		/sys/.../events/in_activity_walking_thresh_falling_persistence
> +What:		/sys/.../events/in_activity_jogging_thresh_rising_persistence
> +What:		/sys/.../events/in_activity_jogging_thresh_falling_persistence
> +What:		/sys/.../events/in_activity_running_thresh_rising_persistence
> +What:		/sys/.../events/in_activity_running_thresh_falling_persistence
> +KernelVersion:	4.0
> +Contact:	linux-iio@xxxxxxxxxxxxxxx
> +Description:
> +		Number of times an event should occur before generating an
> +		interrupt. Persistence filter value can be applied for both
> +		rising/falling threshold based interrupts.
This still needs clarification as reading the discussion I'm still a little unsure
what the condition is.  I don't think Lars' original query ever got cleanly answered.

Taking just the upper threshold...
The interpretations I can think of are:

1) tsl2591 use case (maps directly to period with the sampling frequency taken into
account).  
 - Too much light for N ALS cycling samples.  If it drops below the threshold
   the count is reset.
the tcs part that Daniel referenced is also this use case.

2) A new option which doesn't take account of the signal dropping below the threshold.
   So a count of number of times above the threshold.
 i.e. On each cycle, if over threshold, increment N.
      Evaluate if N is greater than 'persistence' then trigger an event.
  Why this would ever make sense on a light sensor is beyond me ;)  but there
  we are.  We have a related abi for in_steps_change_value, which fires
  an event, only every N steps.  It doesn't really adapt to this case though.

  The name persistence is definitely misleading if this is what the liteon parts
  do as that definitely implies case 1).

Welcome to my life, bludgeoning what appears to new ABI into what we already have!
(not a lot of point in standardized ABI otherwise!)

Jonathan


> +
>  What:		/sys/.../events/in_activity_still_thresh_rising_en
>  What:		/sys/.../events/in_activity_still_thresh_falling_en
>  What:		/sys/.../events/in_activity_walking_thresh_rising_en
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Input]     [Linux Kernel]     [Linux SCSI]     [X.org]

  Powered by Linux