- May 22, 2016
-
-
Matt Ranostay authored
TI ADS1115 is a 16-bit resolution ADC that is register map compatible with the ADS1015 device. Signed-off-by:
Matt Ranostay <matt.ranostay@intel.com> Acked-by:
Daniel Baluta <daniel.baluta@intel.com> Acked-by:
Crt Mori <cmo@melexis.com> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
Daniel Baluta authored
BMM150 is register compatible with magnetometer part of BMC156. Datasheet is at: http://www.mouser.com/ds/2/783/BST-BMM150-DS001-01-786480.pdf Signed-off-by:
-
- May 15, 2016
-
-
Tiberiu Breana authored
This commit adds basic support for the Bosch Sensortec BMA220 digital triaxial acceleration sensor. The device datasheet can be found here: http://www.mouser.com/pdfdocs/BSTBMA220DS00308.PDF Includes: - raw readings - ACPI detection - power management Signed-off-by:
Tiberiu Breana <tiberiu.a.breana@intel.com> Signed-off-by:
-
Matt Ranostay authored
Actually I2C_FUNC_SMBUS_WORD_DATA isn't need for this device, and regmap handles all single byte reads transparently. Signed-off-by:
Matt Ranostay <mranostay@gmail.com> Signed-off-by:
-
- May 04, 2016
-
-
Martin Kepplinger authored
This adds the following sysfs files according to the iio ABI: -rw-r--r-- 4096 in_accel_oversampling_ratio -r--r--r-- 4096 in_accel_oversampling_ratio_available Internally, the device knows about 4 different power modes that differ in oversampling ratio (and power consumption). We just show the user what oversampling ratio(s) is/are available, depending on the current frequency. The referenced table in the datasheets makes it easier to understand. Signed-off-by:
Martin Kepplinger <martink@posteo.de> Signed-off-by:
Christoph Muellner <christoph.muellner@theobroma-systems.com> Signed-off-by:
-
Daniel Baluta authored
Signed-off-by:
-
Daniel Baluta authored
We register a new device type named "dummy", this will create a configfs entry under: * /config/iio/devices/dummy. Creating dummy devices is now as simple as: $ mkdir /config/iio/devices/dummy/my_dummy_device Signed-off-by:
-
Daniel Baluta authored
This is similar with support for creating triggers via configfs. Devices will be hosted under: * /config/iio/devices We allow users to register "device types" under: * /config/iio/devices/<device_types>/ Signed-off-by:
-
Andrew F. Davis authored
Rename this definition, no functional changes. Signed-off-by:
Andrew F. Davis <afd@ti.com> Signed-off-by:
-
Andrew F. Davis authored
These definitions are not currently used and if the functionality they represent is needed the values should be added back to a table for easy userspace use. Signed-off-by:
-
Andrew F. Davis authored
The current channel number for the LEDs should match the stage number that they are active during, fix this here. Signed-off-by:
-
Andrew F. Davis authored
Currently the TIA gain settings are exported to userspace as sysfs entries that do not clearly represent their internal relation to the sampling stages. The gain settings are enabled on a per-stage basis, this can be seen in figure 24 of the current AFE4404 datasheet. These gain settings should therefore be tied to the channels that are read during these stages. Make this change here. Signed-off-by:
-
Andrew F. Davis authored
These drivers can use regmap fields to access fields in registers, this allows us to remove some macros/defines and simplify code, do this here. Signed-off-by:
-
Andrew F. Davis authored
These AFEs have 4 ADC mesuring stages (called LED2, ALED2, LED1, and ALED1 in the datasheet), we map these as channels, these stages can serve different purposes depending on the application. For instance the AFE4404 has an additional LED (LED3), this LED can be timed to be active during stage 2 (or anystage, but the datasheet describes this case and the name of the stage reflects this use). This ability is used further in upcoming parts that tie the front-end gain and the LED timings together. For these reasons we remove explicit naming the channels. Without channel names it is best that the index numbers are in order to match the stage number, reorder the channel numbers. Signed-off-by:
-
Andrew F. Davis authored
Input channel LED3 is only an alias for stage ALED2, this virtual channel does nothing for us, remove this channel. Signed-off-by:
-
Andrew F. Davis authored
No channel in the afe4403 driver has IIO_CHAN_INFO_OFFSET set so remove the handlers for this. Signed-off-by:
-
Andrew F. Davis authored
The LED channels are not scannable and so scan_index should be negative, fix this here. Signed-off-by:
-
Andrew F. Davis authored
Locking the two gain stages to the same setting adds no value for us, so initialize them as unlocked and remove the sysfs for unlocking them. This also allows us to greatly simplify showing and setting the gain registers. Signed-off-by:
-
Andrew F. Davis authored
The drivers set some register values during initialization that can be set at runtime, these defaults were used in testing but are not necessary, remove these. Signed-off-by:
-
Andrew F. Davis authored
The drivers DT tables are not built-in when OF is not enabled, this does not save us enough to justify ugly ifdefs. Clean this up. Signed-off-by:
-
Andrew F. Davis authored
Fix kernel-doc formatting for structs, and while we are making little fixes, clarify the module description and update the copywrite. Signed-off-by:
-
Daniel Baluta authored
Signed-off-by:
-
Stefan Wahren authored
Disabling of the touchscreen IRQs should be done in mxs_lradc_disable_ts. So disable only the masked virtual channels in mxs_lradc_hw_stop and finally remove the unused function mxs_lradc_irq_en_mask. Signed-off-by:
Stefan Wahren <stefan.wahren@i2se.com> Reviewed-by:
Marek Vasut <marex@denx.de> Tested-by:
-
Stefan Wahren authored
After using devm_input_allocate_device for registration the function mxs_lradc_ts_unregister isn't necessary anymore since mxs_lradc_ts_close already does the job. Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com> Acked-by:
-
Stefan Wahren authored
This patch simplifies the TS registration of mxs-lradc by using devm_input_allocate_device. Signed-off-by:
-
Constantin Musca authored
Minimal implementation of an IIO driver for the Freescale MMA7660FC 3-axis accelerometer. Datasheet: http://www.nxp.com/files/sensors/doc/data_sheet/MMA7660FC.pdf Includes: - ACPI support; - read_raw for x,y,z axes; - reading and setting the scale (range) parameter. - power management Signed-off-by:
Constantin Musca <constantin.musca@intel.com> Reviewed-by:
-
- May 02, 2016
-
-
Crestez Dan Leonard authored
The device has simple 8-bit registers but the driver incorrectly uses block or word reads without checking functionality bits. Fix by using i2c_smbus_read_i2c_block_data_or_emulated instead of i2c_smbus_read_i2c_block_data or i2c_smbus_read_word_data. This will check functionality bits and use the fastest available transfer method. Signed-off-by:
Crestez Dan Leonard <leonard.crestez@intel.com> Signed-off-by:
-
- Apr 26, 2016
-
-
Crestez Dan Leonard authored
This device is a package containing a MPU6050-like sensor and an AK8975 magnetometer. The magnetometer component is supported by the existing ak8975 driver. This patch also rephrases the Kconfig descriptions. Signed-off-by:
Ge Gao <ggao@invensense.com> Signed-off-by:
-
Crestez Dan Leonard authored
Signed-off-by:
-
Crestez Dan Leonard authored
This can be used to distinguish mpu6500. This is a warning rather than an error because the differences are mostly irrelevant and it's nice to avoid breaking users with slightly incorrect ACPI/DT. Signed-off-by:
-
Crestez Dan Leonard authored
This field was unused and incorrect for mpu6500. Signed-off-by:
-
Crestez Dan Leonard authored
The hw_info array was indexed by enum inv_devices chip_type despite the fact that the enumeration had more members than the array and was ordered differently. The patch cleans this up and adds explicit chip_types to i2c/spi/acpi IDs. It also adds some stricter checks inside the driver core. This happened to work so far because the differences between the supported models are very minor. Signed-off-by:
-
Akinobu Mita authored
This adds ability to control the oversampling ratio of the temperature and pressure measurement for both bmp180 and bmp280. Signed-off-by:
Akinobu Mita <akinobu.mita@gmail.com> Acked-by:
Vlad Dogaru <vlad.dogaru@intel.com> Cc: Christoph Mair <christoph.mair@gmail.com> Signed-off-by:
-
Akinobu Mita authored
This adds support for the BMP180 to the bmp280 iio driver. The BMP180 has already been supported by misc/bmp085 driver but it doesn't use iio framework. This change adds the kconfig dependency not to be selected both of them in order to avoid any issues. Signed-off-by:
-
- Apr 24, 2016
-
-
Crestez Dan Leonard authored
Signed-off-by:
-
Crestez Dan Leonard authored
This patch exposes ALSTIM as illuminance_integration_time and ALSPGA as illuminance_scale. Changing ALSTIM also changes the number of bits available in the data register. This is handled inside raw value reading because: * It's very easy to shift a few bits * It allows SCALE and INT_TIME to be completely independent controls * Buffer support requires constant scan_type.realbits per-channel Signed-off-by:
-
Crestez Dan Leonard authored
This is exposed as an output channel with "led" as an extend_name. Other sensors also have support for controlling an external LED. It's not clear that simply exposing an undecorated output channel is the correct approach. Signed-off-by:
-
Crestez Dan Leonard authored
The proximity sensor relies on sending pulses to an external IR led and it is disabled by default on powerup. The driver will enable it with a default power setting. Signed-off-by:
-
Crestez Dan Leonard authored
This just adds support for reporting illuminance with default settings. Important default registers are written on probe because the device otherwise lacks a reset function. Signed-off-by:
-
Tiberiu Breana authored
Signed-off-by:
-
