- 08 Aug, 2015 15 commits
-
-
Lars-Peter Clausen authored
The ADIS16266 is mostly register compatible to the ADIS16260. The difference is a different gyroscope scale factor as well not having the relative angular displacement channel. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
Lars-Peter Clausen authored
The ADIS16305 is fully register map compatible to the ADIS16300. Signed-off-by:
-
Lars-Peter Clausen authored
The ADIS16300 has the product ID and serial number registers, they are just not documented. Set the appropriate flags so the driver makes use of them. Signed-off-by:
-
Lars-Peter Clausen authored
The different devices support by the adis16480 driver have slightly different scales for the gyroscope and accelerometer channels. Signed-off-by:
-
Lars-Peter Clausen authored
Add inverse unit conversion macro to convert from standard IIO units to units that might be used by some devices. Those are useful in combination with scale factors that are specified as IIO_VAL_FRACTIONAL. Typically the denominator for those specifications will contain the maximum raw value the sensor will generate and the numerator the value it maps to in a specific unit. Sometimes datasheets specify those in different units than the standard IIO units (e.g. degree/s instead of rad/s) and so we need to do a unit conversion. From a mathematical point of view it does not make a difference whether we apply the unit conversion to the numerator or the inverse unit conversion to the denominator since (x / y) / z = x / (y * z). But as the denominator is typically a larger value and we are rounding both the numerator and denominator to integer values using the later method gives us a better precision (E.g. the relative error is smaller if we round 8000.3 to 8000 rather than rounding 8.3 to 8). This is where in inverse unit conversion macros will be used. Marked for stable as used by some upcoming fixes. Signed-off-by:
-
Lars-Peter Clausen authored
Use the correct scale for the adis16448 gyroscope output. Signed-off-by:
-
Cristina Opriceana authored
Fix kernel docs warnings by adding the missing description for each of the existing function parameters. Signed-off-by:
Cristina Opriceana <cristina.opriceana@gmail.com> Signed-off-by:
-
Cristina Opriceana authored
This patch adds an entry in ABI Documentation for the name attribute issued when a trigger is created. Signed-off-by:
Daniel Baluta <daniel.baluta@intel.com> Signed-off-by:
-
Daniel Baluta authored
This is intended to help developers faster find their way inside the Industrial I/O core and reduce time spent on IIO drivers development. Signed-off-by:
Crt Mori <cmo@melexis.com> Reviewed-by:
-
Pengyu Ma authored
When compile iio related driver the following warning shown: include/linux/iio/trigger.h:35:34: warning: 'struct iio_trigger' declared inside parameter list int (*set_trigger_state)(struct iio_trigger *trig, bool state); include/linux/iio/trigger.h:38:18: warning: 'struct iio_dev' declared inside parameter list struct iio_dev *indio_dev); 'struct iio_dev' and 'struct iio_trigger' was used before declaration, forward declaration for these structs to fix warning. Signed-off-by:Pengyu Ma <pengyu.ma@windriver.com> Acked-by:
-
Hartmut Knaack authored
Drop the local buffer in stk8312_trigger_handler() and use data->buffer instead for bulk reads. Signed-off-by:
Hartmut Knaack <knaack.h@gmx.de> Reviewed-by:
Tiberiu Breana <tiberiu.a.breana@intel.com> Signed-off-by:
-
Hartmut Knaack authored
Adjust some indentation issues to make checkpatch.pl happy in strict mode. Signed-off-by:
-
Hartmut Knaack authored
Adapt some variable types to reduce unnecessary casting. Signed-off-by:
-
Hartmut Knaack authored
Make use of BIT to describe register bits, GENMASK for consecutive bitmasks, rename and sort existing definitions, replace magic value with an expressive definition, drop an unused definition. Signed-off-by:
-
Hartmut Knaack authored
Improve error handling in the following ways: - set return value on error condition to an appropriate error code - return error code immediately in case of an error (slightly changes code structure) - pass up real error code - add missing error handling - return 0 when error have been caught already - put device back in active mode after error occurs Signed-off-by:
-
- 02 Aug, 2015 23 commits
-
-
Hartmut Knaack authored
Revision 1.2 of the datasheet recommends on page 22 to only write non-zero values read from OTP register 0x70 into AFECTRL register. Signed-off-by:
-
Hartmut Knaack authored
Add the still missing dependencies for triggered buffer support. Fixes: 95c12bba ("iio: accel: Add buffer mode for Sensortek STK8312") Signed-off-by:
-
Hartmut Knaack authored
Drop the otherwise unused definition of the channel-array size and use it directly in _probe - makes it a bit more obvious. Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Signed-off-by:
-
Hartmut Knaack authored
Use augmented assignment to subtract the offset for negative temperature values. Specify the amount of private data to be allocated through devm_iio_device_alloc() with sizeof(*priv), as it is shorter and common practice in IIO. Signed-off-by:
-
Hartmut Knaack authored
Mark berlin2_adc_channels array as constant. Signed-off-by:
-
Hartmut Knaack authored
Pass up the real error code returned by platform_get_irq_byname(). Signed-off-by:
-
Joo Aun Saw authored
Signed-off-by:
Joo Aun Saw <jasaw@dius.com.au> Acked-by:
-
Joo Aun Saw authored
Signed-off-by:
-
Irina Tirdea authored
Running generic_buffer without enabling any channel of the sensor will fail without printing any error message. Add an error message that indicates buffer enable failed. Signed-off-by:
Irina Tirdea <irina.tirdea@intel.com> Acked-by:
-
Irina Tirdea authored
When the the sensor data uses 32 bits out of 32, generic_buffer prints the value 0 for all data read. In this case, the mask is shifted 32 bits, which is beyond the size of an integer. This will lead to the mask always being 0. Before printing, the mask is applied to the raw value, thus generating a final value of 0. Fix the mask by shifting a 64 bit value instead of an integer. Signed-off-by:
-
Cristina Opriceana authored
Fix kernel doc for the iio_dev_attr structure by adding its missing field. Signed-off-by:
-
Cristina Opriceana authored
Fix buffer name from kernel doc according to the function parameter. Signed-off-by:
-
Cristina Opriceana authored
Fix kernel docs warnings by adding the missing fields, each with its associated description. Signed-off-by:
-
Cristina Opriceana authored
Fix kernel docs for structures and functions in order to remove some warnings when the documentation gets generated. Signed-off-by:
-
Cristina Opriceana authored
This patch adds the missing fields in kernel docs to remove some warnings that appear when the IIO Documentation DocBook is generated. Signed-off-by:
-
Irina Tirdea authored
When setting the trigger state, the device power state is set through buffer preenable and postdisable hooks. There is no need to also set it in the trigger set state call. Remove duplicate set power state from the trigger set state call. Signed-off-by:
-
Irina Tirdea authored
Runtime resume function is called with the data->mutex lock held. Add a comment to indicate this. Signed-off-by:
-
Hartmut Knaack authored
Define and use a descriptive name for the repetition registers data mask, instead of a 'magic' value. Signed-off-by:
-
Hartmut Knaack authored
Keep the mutex locked, until the content of data->buffer has been pushed out. Signed-off-by:
-
Crt Mori authored
Translates the magic constant numbers to named macros and add some additional comments about their meaning. The diff is made towards togreg branch as that branch seems to have the most recent updates of mlx90614 driver (many are yet to be merged). Signed-off-by:
Peter Meerwald <pmeerw@pmeerw.net> Signed-off-by:
-
Teodora Baluta authored
This patch changes two variables to arrays to improve code readibility. Signed-off-by:
Teodora Baluta <teodora.baluta@intel.com> Signed-off-by:
-
Javier Martinez Canillas authored
The I2C core always reports the MODALIAS uevent as "i2c:<client name" regardless if the driver was matched using the I2C id_table or the of_match_table. So technically there's no need for a driver to export the OF table since currently it's not used. In fact, the I2C device ID table is mandatory for I2C drivers since a i2c_device_id is passed to the driver's probe function even if the I2C core used the OF table to match the driver. And since the I2C core uses different tables, OF-only drivers needs to have duplicated data that has to be kept in sync and also the dev node compatible manufacturer prefix is stripped when reporting the MODALIAS. To avoid the above, the I2C core behavior may be changed in the future to not require an I2C device table for OF-only drivers and report the OF module alias. So, it's better to also export the OF table to prevent breaking module autoloading if that happens. Signed-off-by:
Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by:
-
Javier Martinez Canillas authored
The I2C core always reports the MODALIAS uevent as "i2c:<client name" regardless if the driver was matched using the I2C id_table or the of_match_table. So the driver needs to export the I2C table and this be built into the module or udev won't have the necessary information to auto load the correct module when the device is added. Signed-off-by:
-
- 23 Jul, 2015 2 commits
-
-
Joo Aun Saw authored
Make scale and offset optional by adding -ENOENT check as not all drivers implement them. Signed-off-by:
-
Giuseppe Barba authored
This adds support for the lsm303agr magnetometer. Signed-off-by:
Giuseppe Barba <giuseppe.barba@st.com> Acked-by:
Denis Ciocca <denis.ciocca@st.com> Signed-off-by:
-
