linux-toradex.git/drivers/iio/imu, branch v4.1.15

iio: adis16480: Fix scale factors

2015-09-21T17:05:28+00:00

commit 7abad1063deb0f77d275c61f58863ec319c58c5c upstream.

The different devices support by the adis16480 driver have slightly
different scales for the gyroscope and accelerometer channels.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Jonathan Cameron 
Signed-off-by: Greg Kroah-Hartman

iio: adis16400: Fix adis16448 gyroscope scale

2015-09-21T17:05:28+00:00

commit 8166537283b31d7abaae9e56bd48fbbc30cdc579 upstream.

Use the correct scale for the adis16448 gyroscope output.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Jonathan Cameron 
Signed-off-by: Greg Kroah-Hartman

iio: inv-mpu: Specify the expected format/precision for write channels

2015-08-03T16:29:01+00:00

commit 6a3c45bb5a385be7049a7725a4fe93eaa76915f4 upstream.

The gyroscope needs IIO_VAL_INT_PLUS_NANO for the scale channel and
unless specified write returns MICRO by default.
This needs to be properly specified so that write operations into scale
have the expected behaviour.

Signed-off-by: Adriana Reus 
Signed-off-by: Jonathan Cameron 
Signed-off-by: Greg Kroah-Hartman

iio: adis16400: Fix burst transfer for adis16448

2015-05-16T10:01:20+00:00

The adis16448, unlike the other chips in this family, in addition to the
hardware channels also sends out the DIAG_STAT register in burst mode
before them. Handle that case by skipping over the first 2 bytes before we
pass the received data to the buffer.

Signed-off-by: Lars-Peter Clausen 
Fixes: 76ada52f7f5d ("iio:adis16400: Add support for the adis16448")
Cc: 
Signed-off-by: Jonathan Cameron

iio: adis16400: Fix burst mode

2015-05-16T10:00:50+00:00

There are a few issues with the burst mode support. For one we don't setup
the rx buffer, so the buffer will never be filled and all samples will read
as the zero. Furthermore the tx buffer has the wrong type, which means the
driver sends the wrong command and not the right data is returned.

The final issue is that in burst mode all channels are transferred. Hence
the length of the transfer length should be the number of hardware
channels * 2 bytes. Currently the driver uses indio_dev->scan_bytes for
this. But if the timestamp channel is enabled the scan_bytes will be larger
than the burst length. Fix this by just calculating the burst length based
on the number of hardware channels.

Signed-off-by: Paul Cercueil 
Signed-off-by: Lars-Peter Clausen 
Fixes: 5eda3550a3cc ("staging:iio:adis16400: Preallocate transfer message")
Cc: 
Signed-off-by: Jonathan Cameron

iio: adis16400: Compute the scan mask from channel indices

2015-05-16T09:58:36+00:00

We unfortunately can't use ~0UL for the scan mask to indicate that the
only valid scan mask is all channels selected. The IIO core needs the exact
mask to work correctly and not a super-set of it. So calculate the masked
based on the channels that are available for a particular device.

Signed-off-by: Paul Cercueil 
Signed-off-by: Lars-Peter Clausen 
Fixes: 5eda3550a3cc ("staging:iio:adis16400: Preallocate transfer message")
Cc: 
Signed-off-by: Jonathan Cameron

iio: adis16400: Use != channel indices for the two voltage channels

2015-05-16T09:57:07+00:00

Previously, the two voltage channels had the same ID, which didn't cause
conflicts in sysfs only because one channel is named and the other isn't;
this is still violating the spec though, two indexed channels should never
have the same index.

Signed-off-by: Paul Cercueil 
Signed-off-by: Lars-Peter Clausen 
Cc: 
Signed-off-by: Jonathan Cameron

iio: adis16400: Report pressure channel scale

2015-05-16T09:54:35+00:00

Add the scale for the pressure channel, which is currently missing.

Signed-off-by: Lars-Peter Clausen 
Fixes: 76ada52f7f5d ("iio:adis16400: Add support for the adis16448")
Cc: 
Signed-off-by: Jonathan Cameron

Merge 4.0-rc7 into staging-next

2015-04-07T09:03:02+00:00

We want those fixes (iio primarily) into the -next branch to help with
merge and testing issues.

Signed-off-by: Greg Kroah-Hartman

iio: imu: Use iio_trigger_get for indio_dev->trig assignment

2015-03-28T13:51:40+00:00

This patch uses iio_trigger_get to increment the reference
count of trigger device, to avoid incorrect assignment.
Can result in a null pointer dereference during removal if the
trigger has been changed before removal.

This patch refers to a similar situation encountered through the
following discussion:
http://www.spinics.net/lists/linux-iio/msg13669.html

Signed-off-by: Darshana Padmadas 
Cc: 
Signed-off-by: Jonathan Cameron