linux-toradex.git/include/linux/iio/trigger.h, branch v4.14-rc3

PATCH] iio: Fix some documentation warnings

2017-08-20T14:21:46+00:00

The kerneldoc description for the trig_readonly field of struct iio_dev
lacked a colon, leading to this doc build warning:

  ./include/linux/iio/iio.h:603: warning: No description found for parameter 'trig_readonly'

A similar issue for iio_trigger_set_immutable() in trigger.h yielded:

  ./include/linux/iio/trigger.h:151: warning: No description found for parameter 'indio_dev'
  ./include/linux/iio/trigger.h:151: warning: No description found for parameter 'trig'

Fix the formatting and silence the warnings.

Signed-off-by: Jonathan Corbet 
Signed-off-by: Jonathan Cameron

iio:trigger: Add helper function to verify that a trigger belongs to the same device

2016-09-27T19:32:55+00:00

Some triggers can only be attached to the IIO device that corresponds to
the same physical device. Currently each driver that requires this
implements its own trigger validation function.

Introduce a new helper function called iio_trigger_validate_own_device()
that can be used to do this check. Having a common implementation avoids
code duplication and unnecessary boiler-plate code.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Jonathan Cameron

iio: trigger: helpers to determine own trigger

2016-09-10T15:49:14+00:00

This adds a helper function to the IIO trigger framework:

iio_trigger_using_own(): for an IIO device, this tells
  whether the device is using itself as a trigger.
  This is true if the indio device:
  (A) supplies a trigger and
  (B) has assigned its own buffer poll function to use this
      trigger.

This helper function is good when constructing triggered,
buffered drivers that can either use its own hardware *OR*
an external trigger such as a HRTimer or even the trigger from
a totally different sensor.

Under such circumstances it is important to know for example
if the timestamp from the same trigger hardware should be used
when populating the buffer: if iio_trigger_using_own() is true,
we can use this timestamp, else we need to pick a unique
timestamp directly in the trigger handler.

For this to work of course IIO devices registering hardware
triggers must follow the convention to set the parent device
properly, as as well as setting the parent of the IIO device
itself.

When a new poll function is attached, we check if the parent
device of the IIO of the poll function is the same as the
parent device of the trigger and in that case we conclude that
the hardware is using itself as trigger.

Cc: Giuseppe Barba 
Cc: Denis Ciocca 
Cc: Crestez Dan Leonard 
Cc: Gregor Boirie 
Signed-off-by: Linus Walleij 
Signed-off-by: Jonathan Cameron

iio:trigger: add resource managed (un)register

2016-09-04T14:42:37+00:00

Add resource managed devm_iio_trigger_register() and
devm_iio_triger_unregister() to automatically clean up registered triggers
allocated by IIO drivers, thus leading to simplified IIO drivers code.

Signed-off-by: Gregor Boirie 
Signed-off-by: Jonathan Cameron

iio: trigger: allow immutable triggers to be assigned

2016-09-03T14:31:55+00:00

There are times when an assigned trigger to a device shouldn't ever
change after intialization.

Examples of this being used is when an provider device has a trigger
that is assigned to an ADC, which uses it populate data into a callback
buffer.

Signed-off-by: Matt Ranostay 
Signed-off-by: Jonathan Cameron

iio: declare struct to fix warning

2015-08-08T11:28:46+00:00

When compile iio related driver the following warning shown:

include/linux/iio/trigger.h:35:34: warning: 'struct iio_trigger'
declared inside parameter list
  int (*set_trigger_state)(struct iio_trigger *trig, bool state);

include/linux/iio/trigger.h:38:18: warning: 'struct iio_dev'
declared inside parameter list
           struct iio_dev *indio_dev);

'struct iio_dev' and 'struct iio_trigger' was used before declaration,
forward declaration for these structs to fix warning.

Signed-off-by: Pengyu Ma 
Acked-by: Daniel Baluta 
Signed-off-by: Jonathan Cameron

iio:trigger: modify return value for iio_trigger_get

2014-08-25T20:47:22+00:00

Instead of a void function, return the trigger pointer.

Whilst not in of itself a fix, this makes the following set of
7 fixes cleaner than they would otherwise be.

Signed-off-by: Srinivas Pandruvada 
Signed-off-by: Jonathan Cameron 
Cc: Stable@vger.kernel.org

iio: Remove timestamp argument from iio_trigger_poll() and iio_trigger_poll_chained()

2014-06-14T15:25:59+00:00

argument has been ignored; adjust drivers accordingly

Signed-off-by: Peter Meerwald 
Signed-off-by: Jonathan Cameron

iio:trigger: Fix use_count race condition

2013-07-20T09:18:53+00:00

When using more than one trigger consumer it can happen that multiple threads
perform a read-modify-update cycle on 'use_count' concurrently. This can cause
updates to be lost and use_count can get stuck at non-zero value, in which case
the IIO core assumes that at least one thread is still running and will wait for
it to finish before running any trigger handlers again. This effectively renders
the trigger disabled and a reboot is necessary before it can be used again. To
fix this make use_count an atomic variable. Also set it to the number of
consumers before starting the first consumer, otherwise it might happen that
use_count drops to 0 even though not all consumers have been run yet.

Signed-off-by: Lars-Peter Clausen 
Tested-by: Denis Ciocca 
Signed-off-by: Jonathan Cameron

iio:trigger: Use dev_{set,get}_drvdata for private data management

2013-03-25T21:06:10+00:00

Use dev_{set,get}_drvdata for managing private data attached to a trigger
instead of using a custom field in the iio_trigger struct.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Jonathan Cameron