v2: - Add device id in any-motion trigger - Removed string comparison for trigger name to identify trigger source - Prevent disabling any motion interrupts when both any motion trigger and events are on, but any one of them is disabled via sysfs - Switch on chan->type - Created new function to raw read axis - Explanation why need to power on for changing sampling freq and scale v1: - Runtime PM: Removed module parameter for delay configuration Use RTPM autosuspend delay feature. This allows sysfs configuration of autosuspend time. - Trigger As suggested, there are two triggers: - data_ready : Trigger which will allow all gyro periodic sampled data to be received by user space - any-motion: When used, will configure the chipset so that data is pushed only when there is any motion, allowing system to enter deeper idle power states - Events ROC type events will send direction instead of either. Also both events and data triggers can be enabled together. - Addition of unbuffered TEMP read interface - Misc error message corrections as suggested by Peter Meerwald TBD: Add sysfs attribute to trigger to configure thresholds. Currently the triggers don't have feature to add sysfs attributes unlike IIO device. But this has to be a RFC patch on top. v0: Base version for review Srinivas Pandruvada (2): iio:gyro:bmg160 Gyro Sensor driver iio:gyro:bmg160 documentation .../ABI/testing/sysfs-bus-iio-gyro-bmg160 | 9 + drivers/iio/gyro/Kconfig | 11 + drivers/iio/gyro/Makefile | 1 + drivers/iio/gyro/bmg160.c | 1174 ++++++++++++++++++++ 4 files changed, 1195 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 create mode 100644 drivers/iio/gyro/bmg160.c -- 1.9.1 -- 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
