- 21 Aug, 2016 1 commit
-
-
Aleksei Mamlin authored
Add vendor-prefix for Domintech Co., Ltd. Signed-off-by:
Aleksei Mamlin <mamlinav@gmail.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
- 15 Aug, 2016 8 commits
-
-
Matt Ranostay authored
Enumerate the processed channels (e.g. *_input) as well the raw channels. Signed-off-by:
Matt Ranostay <mranostay@gmail.com> Signed-off-by:
-
Daniel Wagner authored
There is only one waiter for the completion, therefore there is no need to use complete_all(). Let's make that clear by using complete() instead of complete_all(). The usage pattern of the completion is: waiter context waker context sx9500_read_proximity() sx9500_inc_chan_users() sx9500_inc_data_rdy_users() wait_for_completion_interruptible() s9500_irq_thread_handler() complete() reinit_completion() Signed-off-by:Daniel Wagner <daniel.wagner@bmw-carit.de> Signed-off-by:
-
Daniel Wagner authored
There is only one waiter for the completion, therefore there is no need to use complete_all(). Let's make that clear by using complete() instead of complete_all(). The usage pattern of the completion is: waiter context waker context nau7802_read_irq() reinit_completion() nau7802_read_conversion() wait_for_completion_interruptible_timeout() nau7802_eoc_trigger() complete() Signed-off-by: -
Alison Schofield authored
Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. Signed-off-by:
Alison Schofield <amsfield22@gmail.com> Cc: Daniel Baluta <daniel.baluta@gmail.com> Signed-off-by:
-
Alison Schofield authored
hdc100x supports Texas Instruments HDC1000 and HDC1008 relative humidity and temperature sensors. Add these product names to Kconfig. Signed-off-by:
-
Christophe JAILLET authored
It is likely that checking the result of 'pm_runtime_set_active' is expected here. Fixes: f0e5f57d ("iio: light: us8152d: Add power management support") Signed-off-by:
Christophe JAILLET <christophe.jaillet@wanadoo.fr> Signed-off-by:
-
Linus Walleij authored
This adds a driver for the Asahi Kasei AK8974 and its sibling AMI305 magnetometers. It was deployed on scale in 2009 on a multitude of devices. It is distincly different from AK8973 and AK8975 and needs its own driver. This patch is based on the long lost work of Samu Onkalo at Nokia, who made a misc character device driver for the Maemo/MeeGo Nokia devices, before the time of the IIO subsystem. It was mounted in e.g. the Nokia N950, N8, N86, N97 etc. It is also mounted on the ST-Ericsson HREF reference designs. It works nicely in sysfs: $ cat in_magn_x_raw && cat in_magn_y_raw && cat in_magn_z_raw -55 -101 161 And with buffered reads using a simple HRTimer trigger: $ generic_buffer -c10 -a -n ak8974 -t foo iio device number being used is 3 iio trigger number being used is 2 No channels are enabled, enabling all channels Enabling: in_magn_x_en Enabling: in_magn_y_en Enabling: in_magn_z_en Enabling: in_timestamp_en /sys/bus/iio/devices/iio:device3 foo -58.000000 -102.000000 157.000000 946684970985321044 -60.000000 -98.000000 159.000000 946684971012237548 -60.000000 -106.000000 163.000000 946684971032257080 -62.000000 -94.000000 169.000000 946684971052185058 -58.000000 -98.000000 163.000000 946684971072204589 -54.000000 -100.000000 163.000000 946684971092224121 -53.000000 -103.000000 164.000000 946684971112731933 -50.000000 -102.000000 165.000000 946684971132232666 -61.000000 -101.000000 164.000000 946684971152191162 -57.000000 -99.000000 168.000000 946684971172210693 Disabling: in_magn_x_en Disabling: in_magn_y_en Disabling: in_magn_z_en Disabling: in_timestamp_en I cannot currently scale these raw values to gauss. This is because of lack of documentation. I have sent a request for a datasheet to Asahi Kasei. The driver can optionally use a DRDY line IRQ to capture data, else it will sleep and poll. Cc: Samu Onkalo <samu.onkalo@intel.com> Cc: Sebastian Reichel <sre@kernel.org> Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net> Tested-By:
Sebastian Reichel <sre@kernel.org> Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Linus Walleij authored
This adds device tree bindings for the AK8974 magnetometer, similar to those for the AK8975. Cc: devicetree@vger.kernel.org Cc: Samu Onkalo <samu.onkalo@intel.com> Cc: Sebastian Reichel <sre@kernel.org> Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net> Acked-by:
-
- 24 Jul, 2016 5 commits
-
-
William Breathitt Gray authored
The Measurement Computing CIO-DAC is a family of 16-bit and 12-bit analog output devices. The analog outputs are from AD660BN/AD7237 converters with each output buffered by an OP-27. Voltage ranges are configured via physical jumpers on the device. This driver does not support the devices' simulataneous update mode; the XFER jumper option should be deselected for all analog output channels. This driver provides IIO support for the Measurement Computing CIO-DAC family: CIO-DAC16, CIO-DAC08, and PC104-DAC06. The base port addresses for the devices may be configured via the base array module parameter. Signed-off-by:
William Breathitt Gray <vilhelm.gray@gmail.com> Signed-off-by:
-
Alison Schofield authored
Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. Signed-off-by:
-
Alison Schofield authored
Replace the code that guarantees the device stays in direct mode with iio_device_claim_direct_mode() which does same. Signed-off-by:
-
Christophe Chapuis authored
On the Cube i9 tablet, the ACPI id for the Kionix kxcj9 accelerometer is "KIOX000A" (as can be seen in the DSDT of the Cube i9 tablet). It is the same accelerometer, so only adding the ACPI id is needed. Signed-off-by:
Christophe Chapuis <chris.chapuis@gmail.com> Reviewed-by:
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by:
-
Alison Schofield authored
I2C_CLASS_HWMON is for a hardware monitoring chip wanting auto-detection. IIO drivers don't typically use .class. Remove it. Signed-off-by:
Laxman Dewangan <ldewangan@nvidia.com> Acked-by:
Wolfram Sang <wsa@the-dreams.de> Signed-off-by:
-
- 10 Jul, 2016 14 commits
-
-
Peter Meerwald-Stadler authored
Signed-off-by:
Peter Meerwald-Stadler <pmeerw@pmeerw.net> Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
and drop unused PROX_DRIVE Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
Signed-off-by:
-
Peter Meerwald-Stadler authored
VCNL4000, VCNL4010 and VCNL4020 chips are fairly compatible from a software point of view, added features are not yet supported by the driver patch adds a check for the product ID and demotes the corresponding dev_info() to dev_dbg() Signed-off-by:
-
Matt Ranostay authored
Add initial driver support for MAX6675, and MAX31855 thermocouple chips. Cc: Marek Vasut <marex@denx.de> Cc: Matt Porter <mporter@konsulko.com> Signed-off-by:
-
- 05 Jul, 2016 2 commits
-
-
Bijosh Thykkoottathil authored
Removed unwanted return statements from the function mma8452_set_freefall_mode. Signed-off-by:
Bijosh Thykkoottathil <bijosh.t@hotmail.com> Acked-by:
Martin Kepplinger <martink@posteo.de> Signed-off-by:
-
Bijosh Thykkoottathil authored
mma8452_set_freefall_mode can return -ve value in case if i2c_smbus_read_byte_data fails. This function is called from mma8452_probe, and returning -ve value from probe indicates probe failure. Need to call iio_triggered_buffer_cleanup & iio_trigger_cleanup in this case. Signed-off-by:
-
- 04 Jul, 2016 10 commits
-
-
Jonathan Cameron authored
The tree has been in the same location for a long time. Putting it in MAINTAINERS makes it easy for those new to, or less familiar with IIO to find the correct tree to base patches on. Mostly basing on staging-next is fine as well unless working on a very active driver. Signed-off-by: -
Gregor Boirie authored
Some static channels are explicitly initialized with default values. Remove them to enhance readability. Signed-off-by:
Gregor Boirie <gregor.boirie@parrot.com> Tested-by:
-
Gregor Boirie authored
Implement lps22hb temperature sampling channel. Signed-off-by:
-
Gregor Boirie authored
Add support for open drain interrupt line. Signed-off-by:
-
Gregor Boirie authored
Enable support for triggered buffering of temperature samples. Signed-off-by:
-
Gregor Boirie authored
Details scaling factors and offsets applied to raw temperature and pressure samples. Signed-off-by:
-
Gregor Boirie authored
Sampled pressure data are 24 bits long and should be stored in a 32 bits word. Signed-off-by:
-
Gregor Boirie authored
Ensure triggered buffering memory accesses are properly aligned on per channel storagebits boundaries. Signed-off-by:
-
Jonathan Cameron authored
Retire this venerable driver as the basic support is now in the generic st-sensors accelerometer driver. There are a few missing features in the new driver: * Threshold events. * Access to the calibration adjustment registers (patch shortly) In exchange it brings a cleaner and more maintainable code base that actually gets tested more than once every few years. I'll actually be suprised if anyone other than me has a board with one of these on that is running an up to date kernel. Signed-off-by: -
Jonathan Cameron authored
Time to finally kill off the venerable (it was one of my first drivers) lis3l02dq driver in favour of adding support in the st sensors framework. This does loose us the event support that driver always had, but I think that will reappear at some point and in the meantime the maintenance advantages of dropping the 'special' driver for this one part outweigh the issues. It's worth noting this part is ancient and I may well be the only person who still has any on hardware running recent kernels. It has a few 'quirks'. - No WAI register so that just became optional. - A BDU option that really does block updates. Completely. Whatever you do, you don't get any more data with it set. It is documented the same as more modern parts but I presume they are actually clearing for updates after a read of both bytes! - Fixed scale. - It's too quick. Even at slowest rate (280Hz) I can't read out fast enough on my board (stargate 2) to beat new data coming in. Linus' repeat read patch doesn't help in this case. It just means I get 10 readings before dying... So in reality this will get used with software triggers only unless someone has this long out of production device on a quick board. Signed-off-by:
-
