iio: accel: bma400: Add buffer, step and activity/inactivity
Subsystems (2)
v5 cover iio: accel: bma400: Add buffer, step and activity/inactivity
This patch series adds trigger buffer support with data ready interrupt, separate channel for step counter, an event for step change interrupt, activity recognition and activity/inactivity event support.
changes since v4
1/10 - Added Reviewed-by tag.
2/10 - No change.
3/10 - No change.
4/10 - Using __aligned(IIO_ALIGN) instead of ____cacheline_aligned.
Added another entry to bma400_avail_scan_masks() only for accelerometer axis reading. Now temperature will be read only if requested by user.
Added Reviewed-by.
5/10 - Checking regmap_update_bits() and return if error occrus.
6/10 - Using IIO_MOD_EVENT_CODE() instead of IIO_EVENT_CODE().
Pushing all the events that occurred by checking status register and then in the end returning HANDLED so that none of the events are missed.
7/10 - Using IIO_MOD_EVENT_CODE() instead of IIO_EVENT_CODE().
8/10 - Using set_mask_bits() instead of FIELD_PREP().
9/10 - Added new channel for tap and modifiers for single and double tap.
10/10- Added bma400 single and double tap support.
Removed debugfs patch.
changes since v3
1. Removed all the unnecessary mutex locking for regmap.
2. Corrected the mutex locking and unlocking for device private data members.
3. Mutex locking and unlocking is used to protect the device private structure members.
4. Using DMA safe buffer for regmap_bulk_write() and regmap_bulk_read().
1/9: Fixed the comment.
3/9: Added () for the function name in the comment.
4/9: Handling error cases with goto in bma400_trigger_handler().
Mutex locking and unlocking is used to protect the data->buffer.
Using DMA safe buffer for regmap_bulk_read().
Mutex locking and unlocking is used to protect the data->status in
bma400_interrupt.5/9: Using DMA safe buffers to read steps value by allocating memory internally.
Using DMA safe buffers for regmap_bulk_write().
Removed the lock for regmap().
6/9: Removed the duplication of code for enabling step, added function to handle
the step enable.
7/9: Removed the lock for regmap().
Mutex locking and unlocking is used to protect the data members.
8/9: Removed the lock for regmap().
9/9. Added __be16 duration in struct bma400_data.
Fixed the warning - impossible condition '(reg < 0) => (0-255 < 0)' Fixed error: call to __compiletime_assert_272
changes since v2
1. Reordering of header includes in the separate patch.
2. Matching the IIO syntax for multiline comment.
3. Following the preference in the interrupt handler for returning.
4. Add support for activity recognition.
5. Add support for debugfs to access registers from userspace.
6. Add support for activity and inactivity events
changes since v1
1. Added comment section that describes the math for scale calculation.
2. Added separate devm_add_action_or_reset() calls to disable regulator and to put the sensor in power down mode.
3. Remove the err_reg_disable and out, goto labels and returning directly if error occurs.
4. Added mutex calls while putting sensor in power down.
5. Added ___cacheline_aligned for device data.
6. Ordering the header includes.
7. Handling erroneous and spurious interrupts in the interrupt handler by returning IRQ_NONE.
8. Using dev_err_probe() instead of dev_err().
9. Configured the interrupt to open drain.
10. Using le16_to_cpu() to fix the sparse warning.
11. Checking the step change event is enabled or not.
12. Enabling the step change event will also enable the step channel.
13. Using FIELD_GET() instead of bitwise operation.
14. Removal of dead code in the _event_config().
Jagath Jog J (10):
iio: accel: bma400: Fix the scale min and max macro values
iio: accel: bma400: Reordering of header files
iio: accel: bma400: conversion to device-managed function
iio: accel: bma400: Add triggered buffer support
iio: accel: bma400: Add separate channel for step counter
iio: accel: bma400: Add step change event
iio: accel: bma400: Add activity recognition support
iio: accel: bma400: Add support for activity and inactivity events
iio: Add channel for tap and new modifiers for single and double tap
iio: accel: bma400: Add support for single and double tap events
Documentation/ABI/testing/sysfs-bus-iio | 11 + drivers/iio/accel/Kconfig | 2 + drivers/iio/accel/bma400.h | 61 +- drivers/iio/accel/bma400_core.c | 886 ++++++++++++++++++++++-- drivers/iio/accel/bma400_i2c.c | 10 +- drivers/iio/accel/bma400_spi.c | 8 +- drivers/iio/industrialio-core.c | 3 + include/uapi/linux/iio/types.h | 3 + tools/iio/iio_event_monitor.c | 6 + 9 files changed, 923 insertions(+), 67 deletions(-)
Signature · 1 line
2.17.1
PATCH v5 1/10 iio: accel: bma400: Fix the scale min and max macro values
Changing the scale macro values to match the bma400 sensitivity for 1 LSB of all the available ranges.
--- drivers/iio/accel/bma400.h | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-)
drivers/iio/accel/bma400.h +21 -2
@@ -83,8 +83,27 @@#define BMA400_ACC_ODR_MIN_WHOLE_HZ 25#define BMA400_ACC_ODR_MIN_HZ 12 -#define BMA400_SCALE_MIN 38357 -#define BMA400_SCALE_MAX 306864 +/* +* BMA400_SCALE_MIN macro value represents m/s^2 for 1 LSB before +* converting to micro values for +-2g range. +* +* For +-2g - 1 LSB = 0.976562 milli g = 0.009576 m/s^2 +* For +-4g - 1 LSB = 1.953125 milli g = 0.019153 m/s^2 +* For +-16g - 1 LSB = 7.8125 milli g = 0.076614 m/s^2 +* +* The raw value which is used to select the different ranges is determined +* by the first bit set position from the scale value, so BMA400_SCALE_MIN +* should be odd. +* +* Scale values for +-2g, +-4g, +-8g and +-16g are populated into bma400_scales +* array by left shifting BMA400_SCALE_MIN. +* e.g.: +* To select +-2g = 9577 << 0 = raw value to write is 0. +* To select +-8g = 9577 << 2 = raw value to write is 2. +* To select +-16g = 9577 << 3 = raw value to write is 3. +*/ +#define BMA400_SCALE_MIN 9577 +#define BMA400_SCALE_MAX 76617#define BMA400_NUM_REGULATORS 2#define BMA400_VDD_REGULATOR 0
Signature · 1 line
2.17.1
PATCH v5 2/10 iio: accel: bma400: Reordering of header files
In reply to Jagath Jog JReordering of header files and removing the iio/sysfs.h since custom attributes are not being used in the driver.
--- drivers/iio/accel/bma400_core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/iio/accel/bma400_core.c +2 -2
@@ -13,14 +13,14 @@#include <linux/bitops.h> #include <linux/device.h> -#include <linux/iio/iio.h> -#include <linux/iio/sysfs.h> #include <linux/kernel.h> #include <linux/module.h> #include <linux/mutex.h> #include <linux/regmap.h> #include <linux/regulator/consumer.h> +#include <linux/iio/iio.h> +#include "bma400.h" /*
Signature · 1 line
2.17.1
PATCH v5 3/10 iio: accel: bma400: conversion to device-managed function
In reply to Jagath Jog JThis is a conversion to device-managed by using devm_iio_device_register() inside probe function. Previously the bma400 was not put into power down mode in some error paths in probe where it now is, but that should cause no harm.
The dev_set_drvdata() call, bma400_remove() function and hooks in the I2C and SPI driver struct is removed as devm_iio_device_register() function is used to automatically unregister on driver detach.
--- drivers/iio/accel/bma400.h | 2 - drivers/iio/accel/bma400_core.c | 77 ++++++++++++++++----------------- drivers/iio/accel/bma400_i2c.c | 8 ---- drivers/iio/accel/bma400_spi.c | 6 --- 4 files changed, 38 insertions(+), 55 deletions(-)
drivers/iio/accel/bma400.h +0 -2
@@ -113,6 +113,4 @@ extern const struct regmap_config bma400_regmap_config;int bma400_probe (struct device *dev,struct regmap *regmap,const char *name); -void bma400_remove (struct device *dev); -#endif
drivers/iio/accel/bma400_core.c +38 -39
147 lines not on this page · raw message
drivers/iio/accel/bma400_i2c.c +0 -8
@@ -27,13 +27,6 @@ static int bma400_i2c_probe(struct i2c_client *client,return bma400_probe (&client->dev, regmap, id->name); } -static int bma400_i2c_remove (struct i2c_client *client) -{ -bma400_remove (&client->dev); - -return 0 ; -} -static const struct i2c_device_id bma400_i2c_ids[] = { {"bma400" ,0 }, { }
@@ -52,7 +45,6 @@ static struct i2c_driver bma400_i2c_driver = { .of_match_table = bma400_of_i2c_match, }, .probe = bma400_i2c_probe, - .remove = bma400_i2c_remove, .id_table = bma400_i2c_ids, };
drivers/iio/accel/bma400_spi.c +0 -6
@@ -87,11 +87,6 @@ static int bma400_spi_probe(struct spi_device *spi)return bma400_probe (&spi->dev, regmap, id->name); } -static void bma400_spi_remove (struct spi_device *spi) -{ -bma400_remove (&spi->dev); -} -static const struct spi_device_id bma400_spi_ids[] = { {"bma400" ,0 }, { }
@@ -110,7 +105,6 @@ static struct spi_driver bma400_spi_driver = { .of_match_table = bma400_of_spi_match, }, .probe = bma400_spi_probe, - .remove = bma400_spi_remove, .id_table = bma400_spi_ids, };
Signature · 1 line
2.17.1
PATCH v5 4/10 iio: accel: bma400: Add triggered buffer support
In reply to Jagath Jog JAdded trigger buffer support to read continuous acceleration and temperature data from device with data ready interrupt which is mapped to INT1 pin.
--- drivers/iio/accel/Kconfig | 2 + drivers/iio/accel/bma400.h | 10 +- drivers/iio/accel/bma400_core.c | 177 +++++++++++++++++++++++++++++++- drivers/iio/accel/bma400_i2c.c | 2 +- drivers/iio/accel/bma400_spi.c | 2 +- 5 files changed, 185 insertions(+), 8 deletions(-)
drivers/iio/accel/Kconfig +2 -0
@@ -204,6 +204,8 @@ config BMA220 config BMA400 tristate "Bosch BMA400 3-Axis Accelerometer Driver" select REGMAP + select IIO_BUFFER + select IIO_TRIGGERED_BUFFER select BMA400_I2C if I2C select BMA400_SPI if SPI help
drivers/iio/accel/bma400.h +9 -1
@@ -62,6 +62,13 @@#define BMA400_ACC_CONFIG2_REG 0x1b#define BMA400_CMD_REG 0x7e +/* Interrupt registers */ +#define BMA400_INT_CONFIG0_REG 0x1f +#define BMA400_INT_CONFIG1_REG 0x20 +#define BMA400_INT1_MAP_REG 0x21 +#define BMA400_INT_IO_CTRL_REG 0x24 +#define BMA400_INT_DRDY_MSK BIT(7) +/* Chip ID of BMA 400 devices found in the chip ID register. */ #define BMA400_ID_REG_VAL 0x90
@@ -111,6 +118,7 @@extern const struct regmap_config bma400_regmap_config; -int bma400_probe (struct device *dev,struct regmap *regmap,const char *name); +int bma400_probe (struct device *dev,struct regmap *regmap,int irq, +const char *name);#endif
drivers/iio/accel/bma400_core.c +172 -5
247 lines not on this page · raw message
drivers/iio/accel/bma400_i2c.c +1 -1
@@ -24,7 +24,7 @@ static int bma400_i2c_probe(struct i2c_client *client,return PTR_ERR (regmap); } -return bma400_probe (&client->dev, regmap, id->name); +return bma400_probe (&client->dev, regmap, client->irq, id->name); }static const struct i2c_device_id bma400_i2c_ids[] = {
drivers/iio/accel/bma400_spi.c +1 -1
@@ -84,7 +84,7 @@ static int bma400_spi_probe(struct spi_device *spi)if (ret)dev_err (&spi->dev,"Failed to read chip id register\n" ); -return bma400_probe (&spi->dev, regmap, id->name); +return bma400_probe (&spi->dev, regmap, spi->irq, id->name); }static const struct spi_device_id bma400_spi_ids[] = {
Signature · 1 line
2.17.1
PATCH v5 5/10 iio: accel: bma400: Add separate channel for step counter
In reply to Jagath Jog JAdded channel for step counter which can be enable or disable through the sysfs interface.
--- drivers/iio/accel/bma400.h | 2 + drivers/iio/accel/bma400_core.c | 69 +++++++++++++++++++++++++++++++-- 2 files changed, 67 insertions(+), 4 deletions(-)
drivers/iio/accel/bma400.h +2 -0
@@ -53,6 +53,8 @@#define BMA400_STEP_CNT1_REG 0x16#define BMA400_STEP_CNT3_REG 0x17#define BMA400_STEP_STAT_REG 0x18 +#define BMA400_STEP_INT_MSK BIT(0) +#define BMA400_STEP_RAW_LEN 0x03/* * Read-write configuration registers
drivers/iio/accel/bma400_core.c +65 -4
117 lines not on this page · raw message
Signature · 1 line
2.17.1
Jonathan Cameron
maintainerRe: [PATCH v5 05/10] iio: accel: bma400: Add separate channel for step counter
Quoted 6 lines · On Thu, 5 May 2022 19:00:16 +0530 Jagath Jog J <[email protected]> wrote:
Added channel for step counter which can be enable or disable through the sysfs interface.
Signed-off-by Jagath Jog J <[email protected]>---
drivers/iio/accel/bma400_core.c static int bma400_set_power_mode(struct bma400_data *data, · line 599
Quoted 10 lines
drivers/iio/accel/bma400_core.c +10
-0+static int bma400_enable_steps (struct bma400_data *data,int val) +{ +int ret; + +if (data->steps_enabled == val) +return 0 ; + + ret =regmap_update_bits (data->regmap,BMA400_INT_CONFIG1_REG , +BMA400_STEP_INT_MSK , +FIELD_PREP (BMA400_STEP_INT_MSK , !!val));
This gives a dubious x & !y warning
So I've changed it to val ? 1 : 0
Jonathan
Quoted 5 lines
drivers/iio/accel/bma400_core.c +5
-0+if (ret) +return ret; + data->steps_enabled = val; +return ret; +}
PATCH v5 6/10 iio: accel: bma400: Add step change event
In reply to Jagath Jog JAdded support for event when there is a detection of step change. INT1 pin is used to interrupt and event is pushed to userspace.
--- drivers/iio/accel/bma400.h | 2 + drivers/iio/accel/bma400_core.c | 76 +++++++++++++++++++++++++++++++++ 2 files changed, 78 insertions(+)
drivers/iio/accel/bma400.h +2 -0
@@ -39,6 +39,7 @@#define BMA400_INT_STAT0_REG 0x0e#define BMA400_INT_STAT1_REG 0x0f#define BMA400_INT_STAT2_REG 0x10 +#define BMA400_INT12_MAP_REG 0x23/* Temperature register */ #define BMA400_TEMP_DATA_REG 0x11
@@ -55,6 +56,7 @@#define BMA400_STEP_STAT_REG 0x18#define BMA400_STEP_INT_MSK BIT(0)#define BMA400_STEP_RAW_LEN 0x03 +#define BMA400_STEP_STAT_MASK GENMASK(9, 8)/* * Read-write configuration registers
drivers/iio/accel/bma400_core.c +76 -0
130 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH v5 7/10 iio: accel: bma400: Add activity recognition support
In reply to Jagath Jog JAdd support for activity recognition like STILL, WALKING, RUNNING and these events are pushed to the userspace whenever the STEP interrupt occurs.
--- drivers/iio/accel/bma400_core.c | 85 +++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+)
drivers/iio/accel/bma400_core.c +85 -0
@@ -67,6 +67,12 @@ struct bma400_sample_freq {int uhz; }; +enum bma400_activity { +BMA400_STILL , +BMA400_WALKING , +BMA400_RUNNING , +}; +struct bma400_data {struct device *dev;struct regmap *regmap;
@@ -80,6 +86,7 @@ struct bma400_data {struct iio_trigger *trig;int steps_enabled;bool step_event_en; +bool activity_event_en;/* Correct time stamp alignment */ struct {__le16 buff[3 ];
@@ -184,6 +191,12 @@ static const struct iio_event_spec bma400_step_detect_event = { .mask_separate = BIT(IIO_EV_INFO_ENABLE), }; +static const struct iio_event_spec bma400_activity_event = { + .type =IIO_EV_TYPE_CHANGE , + .dir =IIO_EV_DIR_NONE , + .mask_shared_by_type =BIT (IIO_EV_INFO_ENABLE ), +}; +#define BMA400_ACC_CHANNEL (_index, _axis) { \ .type = IIO_ACCEL, \ .modified = 1, \
@@ -205,6 +218,16 @@ static const struct iio_event_spec bma400_step_detect_event = { }, \ } +#define BMA400_ACTIVITY_CHANNEL(_chan2) { \ + .type = IIO_ACTIVITY, \ + .modified = 1, \ + .channel2 = _chan2, \ + .info_mask_separate = BIT(IIO_CHAN_INFO_PROCESSED), \ + .scan_index = -1, /* No buffer support */ \ + .event_spec = &bma400_activity_event, \ + .num_event_specs = 1, \ +} +static const struct iio_chan_spec bma400_channels[] = {BMA400_ACC_CHANNEL (0 ,X ),BMA400_ACC_CHANNEL (1 ,Y ),
@@ -229,6 +252,9 @@ static const struct iio_chan_spec bma400_channels[] = { .event_spec = &bma400_step_detect_event, .num_event_specs = 1, }, +BMA400_ACTIVITY_CHANNEL (IIO_MOD_STILL ), +BMA400_ACTIVITY_CHANNEL (IIO_MOD_WALKING ), +BMA400_ACTIVITY_CHANNEL (IIO_MOD_RUNNING ), IIO_CHAN_SOFT_TIMESTAMP(4), };
@@ -669,6 +695,20 @@ static void bma400_power_disable(void *data_ptr) ERR_PTR(ret)); } +static enum iio_modifier bma400_act_to_mod (enum bma400_activity activity) +{ +switch (activity) { +case BMA400_STILL : +return IIO_MOD_STILL ; +case BMA400_WALKING : +return IIO_MOD_WALKING ; +case BMA400_RUNNING : +return IIO_MOD_RUNNING ; +default : +return IIO_NO_MOD ; + } +} +static int bma400_init (struct bma400_data *data) {unsigned int val;
@@ -766,6 +806,7 @@ static int bma400_read_raw(struct iio_dev *indio_dev, int *val2, long mask) {struct bma400_data *data =iio_priv (indio_dev); +unsigned int activity;int ret;switch (mask) {
@@ -778,6 +819,21 @@ static int bma400_read_raw(struct iio_dev *indio_dev,return ret;case IIO_STEPS :return bma400_get_steps_reg (data, val); +case IIO_ACTIVITY : + ret =regmap_read (data->regmap,BMA400_STEP_STAT_REG , + &activity); +if (ret) +return ret; +/* +* The device does not support confidence value levels, +* so we will always have 100% for current activity and +* 0% for the others. +*/ +if (chan->channel2 ==bma400_act_to_mod (activity)) + *val =100 ; +else + *val =0 ; +return IIO_VAL_INT ;default :return -EINVAL ; }
@@ -927,6 +983,8 @@ static int bma400_read_event_config(struct iio_dev *indio_dev,switch (chan->type) {case IIO_STEPS :return data->step_event_en; +case IIO_ACTIVITY : +return data->activity_event_en;default :return -EINVAL ; }
@@ -964,6 +1022,18 @@ static int bma400_write_event_config(struct iio_dev *indio_dev, ret =bma400_steps_event_enable (data, state);mutex_unlock (&data->mutex);return ret; +case IIO_ACTIVITY : +mutex_lock (&data->mutex); +if (!data->step_event_en) { + ret =bma400_steps_event_enable (data, true); +if (ret) { +mutex_unlock (&data->mutex); +return ret; + } + } + data->activity_event_en = state; +mutex_unlock (&data->mutex); +return 0 ;default :return -EINVAL ; }
@@ -1049,6 +1119,7 @@ static irqreturn_t bma400_interrupt(int irq, void *private)struct iio_dev *indio_dev = private;struct bma400_data *data =iio_priv (indio_dev);s64 timestamp =iio_get_time_ns (indio_dev); +unsigned int act;int ret;/* Lock to protect the data->status */
@@ -1069,6 +1140,20 @@ static irqreturn_t bma400_interrupt(int irq, void *private)IIO_EV_TYPE_CHANGE , IIO_EV_DIR_NONE), timestamp); + +if (data->activity_event_en) { + ret =regmap_read (data->regmap,BMA400_STEP_STAT_REG , + &act); +if (ret) + goto unlock_err; + +iio_push_event (indio_dev, +IIO_MOD_EVENT_CODE (IIO_ACTIVITY ,0 , +bma400_act_to_mod (act), +IIO_EV_TYPE_CHANGE , +IIO_EV_DIR_NONE ), + timestamp); + } }if (FIELD_GET (BMA400_INT_DRDY_MSK ,le16_to_cpu (data->status))) {
Signature · 1 line
2.17.1
PATCH v5 8/10 iio: accel: bma400: Add support for activity and inactivity events
In reply to Jagath Jog JAdd support for activity and inactivity events for all axis based on the threshold, duration and hysteresis value set from the userspace. INT1 pin is used to interrupt and event is pushed to userspace.
--- drivers/iio/accel/bma400.h | 11 ++ drivers/iio/accel/bma400_core.c | 232 +++++++++++++++++++++++++++++++- 2 files changed, 242 insertions(+), 1 deletion(-)
drivers/iio/accel/bma400.h +11 -0
@@ -94,6 +94,17 @@#define BMA400_ACC_ODR_MIN_WHOLE_HZ 25#define BMA400_ACC_ODR_MIN_HZ 12 +/* Generic interrupts register */ +#define BMA400_GEN1INT_CONFIG0 0x3f +#define BMA400_GEN2INT_CONFIG0 0x4A +#define BMA400_GEN_CONFIG1_OFF 0x01 +#define BMA400_GEN_CONFIG2_OFF 0x02 +#define BMA400_GEN_CONFIG3_OFF 0x03 +#define BMA400_GEN_CONFIG31_OFF 0x04 +#define BMA400_INT_GEN1_MSK BIT(2) +#define BMA400_INT_GEN2_MSK BIT(3) +#define BMA400_GEN_HYST_MSK GENMASK(1, 0) +/* * BMA400_SCALE_MIN macro value represents m/s^2 for 1 LSB before * converting to micro values for +-2g range.
drivers/iio/accel/bma400_core.c +231 -1
298 lines not on this page · raw message
Signature · 1 line
2.17.1
Jonathan Cameron
maintainerRe: [PATCH v5 08/10] iio: accel: bma400: Add support for activity and inactivity events
Quoted 5 lines · On Thu, 5 May 2022 19:00:19 +0530 Jagath Jog J <[email protected]> wrote:
Add support for activity and inactivity events for all axis based on the threshold, duration and hysteresis value set from the userspace. INT1 pin is used to interrupt and event is pushed to userspace.
Signed-off-by Jagath Jog J <[email protected]>
I've applied the first 8 patches to the togreg branch of iio.git.
Most of the time it's a bad idea to introduce significant new features in later versions of patch set as it means people mostly don't spot that there is something new to look at.
That particular feature is also defining new and non trivial ABI.
I'll take a look at it and offer some initial comments, but to get proper review it needs to be a new series with a clear rational in a cover letter etc.
Jonathan
Quoted 340 lines
--- drivers/iio/accel/bma400.h | 11 ++ drivers/iio/accel/bma400_core.c | 232 +++++++++++++++++++++++++++++++- 2 files changed, 242 insertions(+), 1 deletion(-)drivers/iio/accel/bma400.h +11
-0@@ -94,6 +94,17 @@#define BMA400_ACC_ODR_MIN_WHOLE_HZ 25#define BMA400_ACC_ODR_MIN_HZ 12 +/* Generic interrupts register */ +#define BMA400_GEN1INT_CONFIG0 0x3f +#define BMA400_GEN2INT_CONFIG0 0x4A +#define BMA400_GEN_CONFIG1_OFF 0x01 +#define BMA400_GEN_CONFIG2_OFF 0x02 +#define BMA400_GEN_CONFIG3_OFF 0x03 +#define BMA400_GEN_CONFIG31_OFF 0x04 +#define BMA400_INT_GEN1_MSK BIT(2) +#define BMA400_INT_GEN2_MSK BIT(3) +#define BMA400_GEN_HYST_MSK GENMASK(1, 0) +/* * BMA400_SCALE_MIN macro value represents m/s^2 for 1 LSB before * converting to micro values for +-2g range. drivers/iio/accel/bma400_core.c +231
-1@@ -87,6 +87,7 @@ struct bma400_data {int steps_enabled;bool step_event_en;bool activity_event_en; +unsigned int generic_event_en;/* Correct time stamp alignment */ struct {__le16 buff[3 ];@@ -94,6 +95,7 @@ struct bma400_data {s64 ts__aligned(8) ; } buffer__aligned(IIO_ALIGN) ;__le16 status; +__be16 duration; };static bool bma400_is_writable_reg (struct device *dev,unsigned int reg)@@ -197,6 +199,25 @@ static const struct iio_event_spec bma400_activity_event = { .mask_shared_by_type = BIT(IIO_EV_INFO_ENABLE), }; +static const struct iio_event_spec bma400_accel_event[] = { + { + .type =IIO_EV_TYPE_MAG , + .dir =IIO_EV_DIR_FALLING , + .mask_shared_by_type =BIT (IIO_EV_INFO_VALUE ) | +BIT (IIO_EV_INFO_PERIOD ) | +BIT (IIO_EV_INFO_HYSTERESIS ) | +BIT (IIO_EV_INFO_ENABLE ), + }, + { + .type =IIO_EV_TYPE_MAG , + .dir =IIO_EV_DIR_RISING , + .mask_shared_by_type =BIT (IIO_EV_INFO_VALUE ) | +BIT (IIO_EV_INFO_PERIOD ) | +BIT (IIO_EV_INFO_HYSTERESIS ) | +BIT (IIO_EV_INFO_ENABLE ), + }, +}; +#define BMA400_ACC_CHANNEL (_index, _axis) { \ .type = IIO_ACCEL, \ .modified = 1, \@@ -216,6 +237,8 @@ static const struct iio_event_spec bma400_activity_event = { .storagebits = 16, \ .endianness = IIO_LE, \ }, \ + .event_spec = bma400_accel_event, \ + .num_event_specs = ARRAY_SIZE(bma400_accel_event) \ }#define BMA400_ACTIVITY_CHANNEL (_chan2) { \@@ -981,6 +1004,17 @@ static int bma400_read_event_config(struct iio_dev *indio_dev,struct bma400_data *data =iio_priv (indio_dev);switch (chan->type) { +case IIO_ACCEL : +switch (dir) { +case IIO_EV_DIR_RISING : +return FIELD_GET (BMA400_INT_GEN1_MSK , + data->generic_event_en); +case IIO_EV_DIR_FALLING : +return FIELD_GET (BMA400_INT_GEN2_MSK , + data->generic_event_en); +default : +return -EINVAL ; + }case IIO_STEPS :return data->step_event_en;case IIO_ACTIVITY :@@ -1008,6 +1042,65 @@ static int bma400_steps_event_enable(struct bma400_data *data, int state)return 0 ; } +static int bma400_activity_event_en (struct bma400_data *data, +enum iio_event_direction dir, +int state) +{ +int ret, reg, msk, value, field_value; + +switch (dir) { +case IIO_EV_DIR_RISING : + reg =BMA400_GEN1INT_CONFIG0 ; + msk =BMA400_INT_GEN1_MSK ; + value =2 ; +set_mask_bits (&field_value,BMA400_INT_GEN1_MSK , +FIELD_PREP (BMA400_INT_GEN1_MSK , state)); +break ; +case IIO_EV_DIR_FALLING : + reg =BMA400_GEN2INT_CONFIG0 ; + msk =BMA400_INT_GEN2_MSK ; + value =0 ; +set_mask_bits (&field_value,BMA400_INT_GEN2_MSK , +FIELD_PREP (BMA400_INT_GEN2_MSK , state)); +break ; +default : +return -EINVAL ; + } + +/* Enabling all axis for interrupt evaluation */ + ret =regmap_write (data->regmap, reg,0xF8 ); +if (ret) +return ret; + +/* OR combination of all axis for interrupt evaluation */ + ret =regmap_write (data->regmap, reg +BMA400_GEN_CONFIG1_OFF , value); +if (ret) +return ret; + +/* Initial value to avoid interrupts while enabling*/ + ret =regmap_write (data->regmap, reg +BMA400_GEN_CONFIG2_OFF ,0x0A ); +if (ret) +return ret; + +/* Initial duration value to avoid interrupts while enabling*/ + ret =regmap_write (data->regmap, reg +BMA400_GEN_CONFIG31_OFF ,0x0F ); +if (ret) +return ret; + + ret =regmap_update_bits (data->regmap,BMA400_INT1_MAP_REG , msk, + field_value); +if (ret) +return ret; + + ret =regmap_update_bits (data->regmap,BMA400_INT_CONFIG0_REG , msk, + field_value); +if (ret) +return ret; + +set_mask_bits (&data->generic_event_en, msk, field_value); +return 0 ; +} + static int bma400_write_event_config(struct iio_dev *indio_dev, const struct iio_chan_spec *chan, enum iio_event_type type,@@ -1017,6 +1110,11 @@ static int bma400_write_event_config(struct iio_dev *indio_dev,int ret;switch (chan->type) { +case IIO_ACCEL : +mutex_lock (&data->mutex); + ret =bma400_activity_event_en (data, dir, state); +mutex_unlock (&data->mutex); +return ret;case IIO_STEPS :mutex_lock (&data->mutex); ret =bma400_steps_event_enable (data, state);@@ -1039,6 +1137,122 @@ static int bma400_write_event_config(struct iio_dev *indio_dev, } } +static int get_gen_config_reg (enum iio_event_direction dir) +{ +switch (dir) { +case IIO_EV_DIR_FALLING : +return BMA400_GEN2INT_CONFIG0 ; +case IIO_EV_DIR_RISING : +return BMA400_GEN1INT_CONFIG0 ; +default : +return -EINVAL ; + } +} + +static int bma400_read_event_value (struct iio_dev *indio_dev, +const struct iio_chan_spec *chan, +enum iio_event_type type, +enum iio_event_direction dir, +enum iio_event_info info, +int *val,int *val2) +{ +struct bma400_data *data =iio_priv (indio_dev); +int ret, reg; + +switch (chan->type) { +case IIO_ACCEL : + reg =get_gen_config_reg (dir); +if (reg <0 ) +return -EINVAL ; + + *val2 =0 ; +switch (info) { +case IIO_EV_INFO_VALUE : + ret =regmap_read (data->regmap, + reg +BMA400_GEN_CONFIG2_OFF , + val); +if (ret) +return ret; +return IIO_VAL_INT ; +case IIO_EV_INFO_PERIOD : +mutex_lock (&data->mutex); + ret =regmap_bulk_read (data->regmap, + reg +BMA400_GEN_CONFIG3_OFF , + &data->duration, +sizeof (data->duration)); +if (ret) { +mutex_unlock (&data->mutex); +return ret; + } + *val =be16_to_cpu (data->duration); +mutex_unlock (&data->mutex); +return IIO_VAL_INT ; +case IIO_EV_INFO_HYSTERESIS : + ret =regmap_read (data->regmap, reg, val); +if (ret) +return ret; + *val =FIELD_GET (BMA400_GEN_HYST_MSK , *val); +return IIO_VAL_INT ; +default : +return -EINVAL ; + } +default : +return -EINVAL ; + } +} + +static int bma400_write_event_value (struct iio_dev *indio_dev, +const struct iio_chan_spec *chan, +enum iio_event_type type, +enum iio_event_direction dir, +enum iio_event_info info, +int val,int val2) +{ +struct bma400_data *data =iio_priv (indio_dev); +int reg, ret; + +switch (chan->type) { +case IIO_ACCEL : + reg =get_gen_config_reg (dir); +if (reg <0 ) +return -EINVAL ; + +switch (info) { +case IIO_EV_INFO_VALUE : +if (val <1 || val >255 ) +return -EINVAL ; + +return regmap_write (data->regmap, + reg +BMA400_GEN_CONFIG2_OFF , + val); +case IIO_EV_INFO_PERIOD : +if (val <1 || val >65535 ) +return -EINVAL ; + +mutex_lock (&data->mutex); +put_unaligned_be16 (val, &data->duration); + ret =regmap_bulk_write (data->regmap, + reg +BMA400_GEN_CONFIG3_OFF , + &data->duration, +sizeof (data->duration)); +mutex_unlock (&data->mutex); +return ret; +case IIO_EV_INFO_HYSTERESIS : +if (val <0 || val >3 ) +return -EINVAL ; + +return regmap_update_bits (data->regmap, reg, +BMA400_GEN_HYST_MSK , +FIELD_PREP (BMA400_GEN_HYST_MSK , + val)); +default : +return -EINVAL ; + } +default : +return -EINVAL ; + } +} +static int bma400_data_rdy_trigger_set_state (struct iio_trigger *trig,bool state) {@@ -1071,6 +1285,8 @@ static const struct iio_info bma400_info = { .write_raw_get_fmt = bma400_write_raw_get_fmt, .read_event_config = bma400_read_event_config, .write_event_config = bma400_write_event_config, + .write_event_value = bma400_write_event_value, + .read_event_value = bma400_read_event_value, };static const struct iio_trigger_ops bma400_trigger_ops = {@@ -1119,7 +1335,7 @@ static irqreturn_t bma400_interrupt(int irq, void *private)struct iio_dev *indio_dev = private;struct bma400_data *data =iio_priv (indio_dev);s64 timestamp =iio_get_time_ns (indio_dev); -unsigned int act; +unsigned int act, ev_dir =IIO_EV_DIR_NONE ;int ret;/* Lock to protect the data->status */ @@ -1134,6 +1350,20 @@ static irqreturn_t bma400_interrupt(int irq, void *private)if (ret || !data->status) goto unlock_err; +if (FIELD_GET (BMA400_INT_GEN1_MSK ,le16_to_cpu (data->status))) + ev_dir =IIO_EV_DIR_RISING ; + +if (FIELD_GET (BMA400_INT_GEN2_MSK ,le16_to_cpu (data->status))) + ev_dir =IIO_EV_DIR_FALLING ; + +if (ev_dir !=IIO_EV_DIR_NONE ) { +iio_push_event (indio_dev, +IIO_MOD_EVENT_CODE (IIO_ACCEL ,0 , +IIO_MOD_X_OR_Y_OR_Z , +IIO_EV_TYPE_MAG , ev_dir), + timestamp); + } +if (FIELD_GET (BMA400_STEP_STAT_MASK ,le16_to_cpu (data->status))) { iio_push_event(indio_dev, IIO_MOD_EVENT_CODE(IIO_STEPS, 0, IIO_NO_MOD,
PATCH v5 9/10 iio: Add channel for tap and new modifiers for single and double tap
In reply to Jagath Jog JAdd new channel type for tap and also add new modifiers for single and double tap. This channel and modifiers may be used by accelerometer sensors to express single and double tap events. For directional tap, modifiers like IIO_MOD_(X/Y/Z) can be used along with rising and falling direction.
--- Documentation/ABI/testing/sysfs-bus-iio | 11 +++++++++++ drivers/iio/industrialio-core.c | 3 +++ include/uapi/linux/iio/types.h | 3 +++ tools/iio/iio_event_monitor.c | 6 ++++++ 4 files changed, 23 insertions(+)
Documentation/ABI/testing/sysfs-bus-iio +11 -0
@@ -2030,3 +2030,14 @@ Description: Available range for the forced calibration value, expressed as: - a range specified as "[min step max]" + +What: /sys/.../events/in_tap_single_change_en +What: /sys/.../events/in_tap_double_change_en +KernelVersion: 5.19 +Contact: [email protected] +Description: + Accelerometer device detects single or double taps and generate + events when threshold for minimum tap amplitide passes. + E.g. a single tap event is generated when acceleration value + crosses the minimum tap amplitude value set. Where tap threshold + value is set by using in_tap_change_value.
drivers/iio/industrialio-core.c +3 -0
@@ -87,6 +87,7 @@ static const char * const iio_chan_type_name_spec[] = { [IIO_POSITIONRELATIVE] = "positionrelative", [IIO_PHASE] = "phase", [IIO_MASSCONCENTRATION] = "massconcentration", + [IIO_TAP ] ="tap" };static const char *const iio_modifier_names[] = {
@@ -134,6 +135,8 @@ static const char * const iio_modifier_names[] = { [IIO_MOD_ETHANOL] = "ethanol", [IIO_MOD_H2] = "h2", [IIO_MOD_O2] = "o2", + [IIO_MOD_TAP_SINGLE] = "single", + [IIO_MOD_TAP_DOUBLE] = "double", };/* relies on pairs of these shared then separate */
include/uapi/linux/iio/types.h +3 -0
@@ -47,6 +47,7 @@ enum iio_chan_type {IIO_POSITIONRELATIVE ,IIO_PHASE ,IIO_MASSCONCENTRATION , + IIO_TAP, }; enum iio_modifier {
@@ -95,6 +96,8 @@ enum iio_modifier {IIO_MOD_ETHANOL ,IIO_MOD_H2 ,IIO_MOD_O2 , +IIO_MOD_TAP_SINGLE , + IIO_MOD_TAP_DOUBLE, }; enum iio_event_type {
tools/iio/iio_event_monitor.c +6 -0
@@ -59,6 +59,7 @@ static const char * const iio_chan_type_name_spec[] = { [IIO_POSITIONRELATIVE] = "positionrelative", [IIO_PHASE] = "phase", [IIO_MASSCONCENTRATION] = "massconcentration", + [IIO_TAP] = "tap", };static const char *const iio_ev_type_text[] = {
@@ -122,6 +123,8 @@ static const char * const iio_modifier_names[] = { [IIO_MOD_PM4] = "pm4", [IIO_MOD_PM10] = "pm10", [IIO_MOD_O2] = "o2", + [IIO_MOD_TAP_SINGLE] = "single", + [IIO_MOD_TAP_DOUBLE] = "double", };static bool event_is_known (struct iio_event_data *event)
@@ -164,6 +167,7 @@ static bool event_is_known(struct iio_event_data *event)case IIO_POSITIONRELATIVE :case IIO_PHASE :case IIO_MASSCONCENTRATION : +case IIO_TAP :break ;default :return false;
@@ -215,6 +219,8 @@ static bool event_is_known(struct iio_event_data *event)case IIO_MOD_PM4 :case IIO_MOD_PM10 :case IIO_MOD_O2 : +case IIO_MOD_TAP_SINGLE : +case IIO_MOD_TAP_DOUBLE :break ;default :return false;
Signature · 1 line
2.17.1
Jonathan Cameron
maintainerRe: [PATCH v5 09/10] iio: Add channel for tap and new modifiers for single and double tap
On Thu, 5 May 2022 19:00:20 +0530
Jagath Jog J <[email protected]> wrote:
Strangely the last time I can remember discussion around how to support tap detection was way back in the early days of IIO, perhaps 10 years ago. I don't recall us ever coming to a conclusion on how to do it.
Quoted 5 lines
Add new channel type for tap and also add new modifiers for single and double tap. This channel and modifiers may be used by accelerometer sensors to express single and double tap events. For directional tap, modifiers like
IIO_MOD_(X/Y/Z)can be used along with rising and falling direction.
Not sure how that would work seeing as there is only one modifier field and it's not a bitmap.
The event code would need to encode both what type of tap and the direction and there aren't two fields in which to do that.
One way I can see this 'might' work would be to use the event type to encode tap and the direction could be 'abused' to encode single vs double (or other events like this)
in_accel_x_tap_singlein_accel_x_tap_double
We could possibly be more generic and have the 'type' as 'event' or something like that allowing us to use the 7 bit direction field to encode different detectable events (I'm not that keen on the name event though, could maybe map it to gesture which would cover some of the other motion pattern detection devices out there)
That would give us
in_accel_x_event_singletapin_accel_y_event_doubletap
etc.
How ever we move forwards we do it this want to be in a new series with a nice bold title to attract that attention of people who don't really care about he bma400 but do care about tap detection; it's
a common feature of accelerometers.
Jonathan
Quoted 110 lines
Signed-off-by Jagath Jog J <[email protected]>--- Documentation/ABI/testing/sysfs-bus-iio | 11 +++++++++++ drivers/iio/industrialio-core.c | 3 +++ include/uapi/linux/iio/types.h | 3 +++ tools/iio/iio_event_monitor.c | 6 ++++++ 4 files changed, 23 insertions(+)Documentation/ABI/testing/sysfs-bus-iio +11
-0@@ -2030,3 +2030,14 @@ Description: Available range for the forced calibration value, expressed as: - a range specified as "[min step max]" + +What: /sys/.../events/in_tap_single_change_en +What: /sys/.../events/in_tap_double_change_en +KernelVersion: 5.19 +Contact: [email protected] +Description: + Accelerometer device detects single or double taps and generate + events when threshold for minimum tap amplitide passes. + E.g. a single tap event is generated when acceleration value + crosses the minimum tap amplitude value set. Where tap threshold + value is set by using in_tap_change_value.drivers/iio/industrialio-core.c +3
-0@@ -87,6 +87,7 @@ static const char * const iio_chan_type_name_spec[] = { [IIO_POSITIONRELATIVE] = "positionrelative", [IIO_PHASE] = "phase", [IIO_MASSCONCENTRATION] = "massconcentration", + [IIO_TAP ] ="tap" };static const char *const iio_modifier_names[] = {@@ -134,6 +135,8 @@ static const char * const iio_modifier_names[] = { [IIO_MOD_ETHANOL] = "ethanol", [IIO_MOD_H2] = "h2", [IIO_MOD_O2] = "o2", + [IIO_MOD_TAP_SINGLE] = "single", + [IIO_MOD_TAP_DOUBLE] = "double", };/* relies on pairs of these shared then separate */ include/uapi/linux/iio/types.h +3
-0@@ -47,6 +47,7 @@ enum iio_chan_type {IIO_POSITIONRELATIVE ,IIO_PHASE ,IIO_MASSCONCENTRATION , + IIO_TAP, }; enum iio_modifier {@@ -95,6 +96,8 @@ enum iio_modifier {IIO_MOD_ETHANOL ,IIO_MOD_H2 ,IIO_MOD_O2 , +IIO_MOD_TAP_SINGLE , + IIO_MOD_TAP_DOUBLE, }; enum iio_event_type {tools/iio/iio_event_monitor.c +6
-0@@ -59,6 +59,7 @@ static const char * const iio_chan_type_name_spec[] = { [IIO_POSITIONRELATIVE] = "positionrelative", [IIO_PHASE] = "phase", [IIO_MASSCONCENTRATION] = "massconcentration", + [IIO_TAP] = "tap", };static const char *const iio_ev_type_text[] = {@@ -122,6 +123,8 @@ static const char * const iio_modifier_names[] = { [IIO_MOD_PM4] = "pm4", [IIO_MOD_PM10] = "pm10", [IIO_MOD_O2] = "o2", + [IIO_MOD_TAP_SINGLE] = "single", + [IIO_MOD_TAP_DOUBLE] = "double", };static bool event_is_known (struct iio_event_data *event)@@ -164,6 +167,7 @@ static bool event_is_known(struct iio_event_data *event)case IIO_POSITIONRELATIVE :case IIO_PHASE :case IIO_MASSCONCENTRATION : +case IIO_TAP :break ;default :return false;@@ -215,6 +219,8 @@ static bool event_is_known(struct iio_event_data *event)case IIO_MOD_PM4 :case IIO_MOD_PM10 :case IIO_MOD_O2 : +case IIO_MOD_TAP_SINGLE : +case IIO_MOD_TAP_DOUBLE :break ;default :return false;
Re: [PATCH v5 09/10] iio: Add channel for tap and new modifiers for single and double tap
Hi Jonathan,
Thanks for accepting the patches.
Quoted 38 lines · Jonathan Cameron
On Thu, 5 May 2022 19:00:20 +0530
Jagath Jog J <[email protected]> wrote:Strangely the last time I can remember discussion around how to support tap detection was way back in the early days of IIO, perhaps 10 years ago. I don't recall us ever coming to a conclusion on how to do it.
Quoted 5 lines
Add new channel type for tap and also add new modifiers for single and double tap. This channel and modifiers may be used by accelerometer sensors to express single and double tap events. For directional tap, modifiers like
IIO_MOD_(X/Y/Z)can be used along with rising and falling direction.Not sure how that would work seeing as there is only one modifier field and it's not a bitmap.
The event code would need to encode both what type of tap and the direction and there aren't two fields in which to do that.One way I can see this 'might' work would be to use the event type to encode tap and the direction could be 'abused' to encode single vs double (or other events like this)
in_accel_x_tap_singlein_accel_x_tap_doubleWe could possibly be more generic and have the 'type' as 'event' or something like that allowing us to use the 7 bit direction field to encode different detectable events (I'm not that keen on the name event though, could maybe map it to gesture which would cover some of the other motion pattern detection devices out there)
That would give us
in_accel_x_event_singletapin_accel_y_event_doubletap
Quoted 6 lines
etc.
How ever we move forwards we do it this want to be in a new series with a nice bold title to attract that attention of people who don't really care about he bma400 but do care about tap detection; it's
a common feature of accelerometers.
Sure, I will try to make a new series for tap events with the given inputs and send the RFC first to get all the comments from everyone.
Quoted 116 lines
Jonathan
Quoted 110 lines
Signed-off-by Jagath Jog J <[email protected]>--- Documentation/ABI/testing/sysfs-bus-iio | 11 +++++++++++ drivers/iio/industrialio-core.c | 3 +++ include/uapi/linux/iio/types.h | 3 +++ tools/iio/iio_event_monitor.c | 6 ++++++ 4 files changed, 23 insertions(+)Documentation/ABI/testing/sysfs-bus-iio +11
-0@@ -2030,3 +2030,14 @@ Description: Available range for the forced calibration value, expressed as: - a range specified as "[min step max]" + +What: /sys/.../events/in_tap_single_change_en +What: /sys/.../events/in_tap_double_change_en +KernelVersion: 5.19 +Contact: [email protected] +Description: + Accelerometer device detects single or double taps and generate + events when threshold for minimum tap amplitide passes. + E.g. a single tap event is generated when acceleration value + crosses the minimum tap amplitude value set. Where tap threshold + value is set by using in_tap_change_value.drivers/iio/industrialio-core.c +3
-0@@ -87,6 +87,7 @@ static const char * const iio_chan_type_name_spec[] = { [IIO_POSITIONRELATIVE] = "positionrelative", [IIO_PHASE] = "phase", [IIO_MASSCONCENTRATION] = "massconcentration", + [IIO_TAP ] ="tap" };static const char *const iio_modifier_names[] = {@@ -134,6 +135,8 @@ static const char * const iio_modifier_names[] = { [IIO_MOD_ETHANOL] = "ethanol", [IIO_MOD_H2] = "h2", [IIO_MOD_O2] = "o2", + [IIO_MOD_TAP_SINGLE] = "single", + [IIO_MOD_TAP_DOUBLE] = "double", };/* relies on pairs of these shared then separate */ include/uapi/linux/iio/types.h +3
-0@@ -47,6 +47,7 @@ enum iio_chan_type {IIO_POSITIONRELATIVE ,IIO_PHASE ,IIO_MASSCONCENTRATION , + IIO_TAP, }; enum iio_modifier {@@ -95,6 +96,8 @@ enum iio_modifier {IIO_MOD_ETHANOL ,IIO_MOD_H2 ,IIO_MOD_O2 , +IIO_MOD_TAP_SINGLE , + IIO_MOD_TAP_DOUBLE, }; enum iio_event_type {tools/iio/iio_event_monitor.c +6
-0@@ -59,6 +59,7 @@ static const char * const iio_chan_type_name_spec[] = { [IIO_POSITIONRELATIVE] = "positionrelative", [IIO_PHASE] = "phase", [IIO_MASSCONCENTRATION] = "massconcentration", + [IIO_TAP] = "tap", };static const char *const iio_ev_type_text[] = {@@ -122,6 +123,8 @@ static const char * const iio_modifier_names[] = { [IIO_MOD_PM4] = "pm4", [IIO_MOD_PM10] = "pm10", [IIO_MOD_O2] = "o2", + [IIO_MOD_TAP_SINGLE] = "single", + [IIO_MOD_TAP_DOUBLE] = "double", };static bool event_is_known (struct iio_event_data *event)@@ -164,6 +167,7 @@ static bool event_is_known(struct iio_event_data *event)case IIO_POSITIONRELATIVE :case IIO_PHASE :case IIO_MASSCONCENTRATION : +case IIO_TAP :break ;default :return false;@@ -215,6 +219,8 @@ static bool event_is_known(struct iio_event_data *event)case IIO_MOD_PM4 :case IIO_MOD_PM10 :case IIO_MOD_O2 : +case IIO_MOD_TAP_SINGLE : +case IIO_MOD_TAP_DOUBLE :break ;default :return false;
PATCH v5 10/10 iio: accel: bma400: Add support for single and double tap events
In reply to Jagath Jog JAdd support for single and double tap events based on the tap threshold value and minimum quite time value between the taps. INT1 pin is used to interrupt and event is pushed to userspace.
--- drivers/iio/accel/bma400.h | 11 ++ drivers/iio/accel/bma400_core.c | 176 ++++++++++++++++++++++++++++++++ 2 files changed, 187 insertions(+)
drivers/iio/accel/bma400.h +11 -0
@@ -40,6 +40,7 @@#define BMA400_INT_STAT1_REG 0x0f#define BMA400_INT_STAT2_REG 0x10#define BMA400_INT12_MAP_REG 0x23 +#define BMA400_INT_ENG_OVRUN_MSK BIT(4)/* Temperature register */ #define BMA400_TEMP_DATA_REG 0x11
@@ -105,6 +106,16 @@#define BMA400_INT_GEN2_MSK BIT(3)#define BMA400_GEN_HYST_MSK GENMASK(1, 0) +/* TAP config registers */ +#define BMA400_TAP_CONFIG 0x57 +#define BMA400_TAP_CONFIG1 0x58 +#define BMA400_S_TAP_MSK BIT(2) +#define BMA400_D_TAP_MSK BIT(3) +#define BMA400_INT_S_TAP_MSK BIT(10) +#define BMA400_INT_D_TAP_MSK BIT(11) +#define BMA400_TAP_SEN_MSK GENMASK(2, 0) +#define BMA400_TAP_QUITE_MSK GENMASK(3, 2) +/* * BMA400_SCALE_MIN macro value represents m/s^2 for 1 LSB before * converting to micro values for +-2g range.
drivers/iio/accel/bma400_core.c +176 -0
248 lines not on this page · raw message
Signature · 1 line
2.17.1