kernel.git/drivers/iio/magnetometer, branch linux-4.13.y

iio: magnetometer: st_magn: remove ihl property for LSM303AGR

2017-08-20T14:21:49Z

Remove IRQ active low support for LSM303AGR since the sensor does not support that capability for data-ready line Fixes: a9fd053b56c6 (iio: st_sensors: support active-low interrupts) Signed-off-by: Lorenzo Bianconi Reviewed-by: Linus Walleij Cc: Signed-off-by: Jonathan Cameron

iio: magnetometer: st_magn: fix status register address for LSM303AGR

2017-08-20T14:21:48Z

Fixes: 97865fe41322 (iio: st_sensors: verify interrupt event to status) Signed-off-by: Lorenzo Bianconi Reviewed-by: Linus Walleij Cc: Signed-off-by: Jonathan Cameron

iio: magnetometer: st_magn_spi: fix spi_device_id table

2017-06-11T14:07:40Z

Remove LSM303DLHC, LSM303DLM from st_magn_id_table since LSM303DL series does not support spi interface Fixes: 872e79add756 (iio: magn: Add STMicroelectronics magn driver) Signed-off-by: Lorenzo Bianconi Signed-off-by: Jonathan Cameron

Merge 4.11-rc4 into staging-next

2017-03-27T07:11:25Z

We need the IIO fixes in here as well to handle merge issues. Signed-off-by: Greg Kroah-Hartman

iio: magnetometer: mag3110: Add OF device ID table

2017-03-19T10:57:24Z

The driver doesn't have a struct of_device_id table but supported devices are registered via Device Trees. This is working on the assumption that a I2C device registered via OF will always match a legacy I2C device ID and that the MODALIAS reported will always be of the form i2c:. But this could change in the future so the correct approach is to have an OF device ID table if the devices are registered via OF. Signed-off-by: Javier Martinez Canillas Signed-off-by: Jonathan Cameron

iio: magnetometer: bmc150_magn_i2c: Add OF device ID table

2017-03-19T10:50:10Z

iio: magnetometer: ak8974: remove incorrect __exit markups

2017-03-05T13:52:01Z

Even if bus is not hot-pluggable, devices can be unbound from the driver via sysfs, so we should not be using __exit annotations on remove() methods. The only exception is drivers registered with platform_driver_probe() which specifically disables sysfs bind/unbind attributes. Signed-off-by: Dmitry Torokhov Reviewed-by: Linus Walleij Cc: Signed-off-by: Jonathan Cameron

iio: magnetometer: mag3110: claim direct mode during raw writes

2017-01-21T12:20:40Z

Driver was checking for direct mode but not locking it. Use claim/release helper functions to guarantee the device stays in direct mode during raw writes. Signed-off-by: Alison Schofield Acked-by: Peter Meerwald-Stadler Signed-off-by: Jonathan Cameron

iio: magnetometer: ak8974: remove redundant zero timeout check

2017-01-14T13:10:04Z

At the end of the delay loop timeout will always be zero and hence the check for !timeout will always be true. Remove the redundant check and the redundant return 0 at the end of the function. Fixes CoverityScan CID#1357168 ("Logically dead code") Signed-off-by: Colin Ian King Reviewed-by: Linus Walleij Signed-off-by: Jonathan Cameron

iio: magnetometer: separate the values of attributes based on their usage type for HID compass sensor

2016-11-24T20:41:30Z

There are 2 usage types (Magnetic Flux and Heading data field) for HID compass sensor, thus the values of offset, scale, and sensitivity should be separated according to their respective usage type. The changes made are as below: 1. Hysteresis: A struct hid_sensor_common rot_attributes is created in struct magn_3d_state to contain the sensitivity for IIO_ROT. 2. Scale: scale_pre_decml and scale_post_decml are separated for IIO_MAGN and IIO_ROT. 3. Offset: Same as scale, value_offset is separated for IIO_MAGN and IIO_ROT. For sensitivity, HID_USAGE_SENSOR_ORIENT_MAGN_FLUX and HID_USAGE_SENSOR_ORIENT_MAGN_HEADING are used for sensivitity fields based on the HID Sensor Usages specifications. Hence, these changes are added on the sensitivity field. Signed-off-by: Ooi, Joyce Acked-by: Srinivas Pandruvada Signed-off-by: Jonathan Cameron