On 02/09/2016 12:06 PM, Gregor Boirie wrote:
One remaining question is : how do we ensure sample and event timestamps
consistency with respect to clock changes ? 2 suggestions:
* reject the ability to select a new clock as long as an events
chardev is opened
or a buffered samples channel is enabled ;
Actually, this may be the only viable solution since some drivers save
timestamps for
futur usage (see drivers/iio/accel/bmc150-accel-core.c). Changing
reference clock
between 2 timestamping operations would lead to inconsistencies.
* clock may be changed at any time since it could be implemented in an
atomic
way (a simple atomic_t can hold an int / clockid_t if I'm no wrong).
--
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
