- 29 Jun, 2014 1 commit
-
-
Guillaume Morin authored
checkpath.pl was complaining about value_mask: ERROR: Macros with complex values should be enclosed in parenthesis I fixed this by simply removing it since it's not used (as well as another macro). Got rid of the un-necessary error_ret label as well. Signed-off-by:
Guillaume Morin <guillaume@morinfr.org> Reported-by:
Michael Welling <mwelling@ieee.org> Acked-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
- 28 Jun, 2014 1 commit
-
-
Philippe Reynes authored
This driver add partial support of the maxim 1027/1029/1031. Differential mode is not supported. It was tested on armadeus apf27 board. Signed-off-by:
Philippe Reynes <tremyfr@yahoo.fr> Reviewed-by:
Hartmut Knaack <knaack.h@gmx.de> Signed-off-by:
-
- 21 Jun, 2014 2 commits
-
-
Beomho Seo authored
This patch changes API from iio_device_register() to devm_* API. Using API make code simpler. Signed-off-by:
Beomho Seo <beomho.seo@samsung.com> Signed-off-by:
-
Michael Welling authored
This patch provides an iio device driver for the Microchip MCP49x2 series DACs. Signed-off-by:
-
- 16 Jun, 2014 2 commits
-
-
Srinivas Pandruvada authored
Fix unlock at two places. One when i2c error occurs and other when trigger set state when raw read is in progress. kbuild test robot errors: >> >> drivers/iio/accel/kxcjk-1013.c:531:3-9: preceding lock on line 524 >> >> drivers/iio/accel/kxcjk-1013.c:376:4-10: preceding lock on line 368 Signed-off-by:
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Reported-by:
Fengguang Wu <fengguang.wu@intel.com> Signed-off-by:
-
Srinivas Pandruvada authored
Added IIO magnetometer driver for AK09911. In functionality is resembles AK8975 or AK8963. But there are several differences, so instead of modifying existing AK8975 driver and keep it clean, implemented as a separate driver. The key differences are: - Register map is different and have different indexes - AK09911 is a very compact interface with no DRDY pin. So no support of interrupt or GPIO poll - Even for polled mode no mention on ST2 register, which is required in ak8975 driver - mode values are different for fuse access Signed-off-by:
-
- 14 Jun, 2014 17 commits
-
-
Srinivas Pandruvada authored
This patch adds IIO driver for KXCJK 1013 triaxis accelerometer sensor. The specifications for this driver is downloaded from: http://www.kionix.com/sites/default/files/KXCJK-1013%20Specifications%20Rev%202.pdfSigned-off-by:
-
Peter Meerwald authored
argument has been ignored; adjust drivers accordingly Signed-off-by:
Peter Meerwald <pmeerw@pmeerw.net> Signed-off-by:
-
Jimmy Picard authored
This patch fixes coding style reported by checkpatch.pl that missing a blank line after declarations. Signed-off-by:
Jimmy Picard <jimmyp11f155@gmail.com> Signed-off-by:
-
Peter Meerwald authored
periodic rtc trigger initially has frequency 0 it is possible to change trigger frequency on-the-fly, but it is not possible to set frequency back to 0 this patch allows to set trigger frequency to 0, thereby disabling the rtc interrupt Signed-off-by:
-
Peter Meerwald authored
Fix extra space in module description Silence output about trigger frequency when trigger gets enabled/disabled Signed-off-by:
-
Peter Meerwald authored
read() does not return -EAGAIN read() returns -1 and the errno value needs to be checked for -EAGAIN Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
add types recently added Signed-off-by:
-
Peter Meerwald authored
iio-trig-sysfs has left staging with commit e64e7d5cSigned-off-by:
-
Peter Meerwald authored
Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
16-bit pressure and temperature sensor the chip can do I2C and SPI, only the I2C interface is supported by the driver at the moment datasheet: http://www.epcos.com/inf/57/ds/T5400.pdf application note: http://www.epcos.com/blob/993154/download/1/t5403-applicationnote.pdf an out-of-tree driver targetting the input subsystem is at https://github.com/unixphere/t5400, it was rejected here: http://comments.gmane.org/gmane.linux.kernel.input/28107 v2: (thanks Hartmut Knaack) * fix MODE_HIGH, equals 2 * check INT_TIME mask in write_raw() Signed-off-by:
-
- 29 May, 2014 1 commit
-
-
Peter Meerwald authored
has been in use for a long time, but never documented proximity is unit-less, except otherwise stated, see e.g. the as3935 driver where it is meter Signed-off-by:
-
- 25 May, 2014 2 commits
-
-
Toralf Förster authored
spotted by cppcheck Signed-off-by:
Toralf Förster <toralf.foerster@gmx.de> Signed-off-by:
-
Jonathan Cameron authored
Cc: Stable@vger.kernel.org> Reported-by:
Erik Habbinga <Erik.Habbinga@schneider-electric.com> Signed-off-by:
-
- 10 May, 2014 4 commits
-
-
Archana Patni authored
For PROP_REPORT_INTERVAL, the spec does not mandate the presence of the report interval unit in the feature report and expects the default unit of measure to be used as milliseconds. Currently, when the unit is not present, it gets set as zero leading to issues in sampling frequency. This patch sets the unit of measure to the default unit if it is not defined by firmware. Signed-off-by:
Archana Patni <archana.patni@intel.com> Signed-off-by:
Subramony Sesha <subramony.sesha@intel.com> Reviewed-by:
Srinivas Pandruvada <srinivas.pandruvada@intel.com> Signed-off-by:
-
Arnd Bergmann authored
Building the at91 adc driver with CONFIG_INPUT disabled results in this build error: ERROR: "input_event" [drivers/iio/adc/at91_adc.ko] undefined! ERROR: "input_unregister_device" [drivers/iio/adc/at91_adc.ko] undefined! ERROR: "input_free_device" [drivers/iio/adc/at91_adc.ko] undefined! ERROR: "input_register_device" [drivers/iio/adc/at91_adc.ko] undefined! ERROR: "input_set_abs_params" [drivers/iio/adc/at91_adc.ko] undefined! ERROR: "input_allocate_device" [drivers/iio/adc/at91_adc.ko] undefined! To make sure we can build random configurations, this adds a Kconfig dependency on CONFIG_INPUT, as we do for other similar drivers. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Cc: linux-iio@vger.kernel.org Cc: Josh Wu <josh.wu@atmel.com> Cc: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by:
Nicolas Ferre <nicolas.ferre@atmel.com> Signed-off-by:
-
Arnd Bergmann authored
Without ANON_INODES, we get this build error: drivers/built-in.o: In function `iio_event_getfd': :(.text+0x14bf18): undefined reference to `anon_inode_getfd' All other users explicitly select this symbol, so we should do the same thing here. Signed-off-by:
-
Dan Carpenter authored
The "i < " was missing in this condition. Fixes: 5d02edfc ('iio: hid-sensors: Convert units and exponent') Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
- 06 May, 2014 1 commit
-
-
- 05 May, 2014 9 commits
-
-
Greg Kroah-Hartman authored
Merge tag 'iio-for-3.16b' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next Jonathan writes: Second set of IIO new drivers, cleanups and functionality for the 3.16 cycle. This set contains a change to the ABI for the hid-sensors drivers to bring them in line with the long published documentation. Unfortunately, rather than reporting true scale and offset values via sysfs they were reporting some magic numbers that could only be converted to anything useful using the HID sensors specification. I missed this entirely through the introduction of a number of drivers, only picking up on it recently. Srinivas has had user feedback about this as well. The patch set is too large to go as a fix at this stage in the cycle and is not a regression fix as this was never right and so will have to wait for the next merge window. Srinivas assures me that there are relatively few pieces of hardware out there and he has had a number of people contact him to point out that the drivers did not obey the ABI. Hence hopefully the fallout of this, if any will be minor. If we don't fix it now, it will only get worse going forward. There is no sensible way of maintaining the incorrect ABI as it is simply returning the wrong values through the standard interfaces. Non IIO elements * Introduce devm_kmemdup. Does what it says on the tin. New drivers: * hid-sensors rotation devices (output as quaternion) * Freescale MPL115A2 presure and temperature sensor. * Melexis mlx90614 contactless infrared sensor. * Freescale MMA8452Q 3-axis accelerometer. New functionality: * Addition of multiple element callback to allow for sysfs interfaces to access elements such as quaternions which have no useful meaning if all 4 elements are not presented together. Other future usecases for this include rotation matrices. * Support for multiple element buffer entries for exactly the same uses as the sysfs related elements described above. * Quaternion support via the quaternion IIO modifier. * TEMP_AMBIENT and TEMP_OBJECT modifiers to distinguish cases with thermopile devices. * hid-sensors gain sysfs access to the sensor readings. Previously these drivers used the buffered interface only. This change involves some additional hid-sensors core support to read poll values back from the devices to allow the drivers to know roughly how long to wait for a result when polling the sensor. There is also an associated hid-sensors abi to allow the devices to be turned off between reads and powered up on demand. Cleanups and fixes * Hid sensors fix as described above. Result is to make the _scale and _offset attributes applicable in the same way as for all other IIO drivers. * Some additional documentation - mostly covering stuff that graduated from staging without managing to take it's ABI docs with it. * A series of little tidy ups to the exynos_adc driver that make the code nicer to read and improve handling of some corner cases. * A tidy up to mag3110 (logical fix rather than a real one ;). Also enable user offset calibration for this device. * Drop some left over IS_ERR() checks from ad799x that snuck through during the cleanup in the last IIO patch set. * Fix a naming issue from clashing patches in ak8975 - note the clash only occured in the last IIO patch set, hence the fix needs to go through this tree. * A format string missmatch fix in ad7280.c. Unlikely to have ever had an impact so not worth rushing through.
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added an API to allow client drivers to turn ON and OFF sensors for quick read. Added data_read as counting varaible instead of boolean, so that sensor is powered off only when last user released it. Signed-off-by:
-
