summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/iio/imu
diff options
context:
space:
mode:
authorMartin Kelly <mkelly@xevo.com>2018-04-20 18:54:00 +0200
committerJonathan Cameron <Jonathan.Cameron@huawei.com>2018-04-21 17:24:30 +0200
commit5ec6486daa98ba4bb18542116db7d867986c0ebe (patch)
treea5edf818833df832edec52a40de58f05c80c7b18 /Documentation/devicetree/bindings/iio/imu
parentiio: imu: inv_mpu6050: use set_power_itg function in i2c mux (diff)
downloadlinux-5ec6486daa98ba4bb18542116db7d867986c0ebe.tar.xz
linux-5ec6486daa98ba4bb18542116db7d867986c0ebe.zip
iio:imu: inv_mpu6050: support more interrupt types
Currently, we support only rising edge interrupts, and in fact we assume that the interrupt we're given is rising edge (and things won't work if it's not). However, the device supports rising edge, falling edge, level low, and level high interrupts. Empirically, on my system, switching to level interrupts has fixed a problem I had with significant (~40%) interrupt loss with edge interrupts. This issue is likely related to the SoC I'm using (Allwinner H3), but being able to switch the interrupt type is still a very useful workaround. I tested this with each interrupt type and verified correct behavior in a logic analyzer. Add support for these interrupt types while also eliminating the error case of the device tree and driver using different interrupt types. Signed-off-by: Martin Kelly <mkelly@xevo.com> Acked-by: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'Documentation/devicetree/bindings/iio/imu')
0 files changed, 0 insertions, 0 deletions