- 16 Nov, 2018 9 commits
-
-
Song Qiang authored
Signed-off-by:
Song Qiang <songqiang1304521@gmail.com> Reviewed-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com>
-
Heiko Stuebner authored
This commit add support for STMicroelectronics lis3de accelerometer. Datasheet for this device can be found here: https://www.st.com/resource/en/datasheet/lis3de.pdfSigned-off-by:
Heiko Stuebner <heiko.stuebner@bq.com> Acked-by:
-
Parthiban Nallathambi authored
Adding device tree binding for vcnl4035 and vendor prefix for Vishay Intertechnology Signed-off-by:
Parthiban Nallathambi <pn@denx.de> Reviewed-by:
-
Parthiban Nallathambi authored
Add support for VCNL4035, which is capable of Ambient light sensing (ALS) and proximity function. This patch adds support only for ALS function Signed-off-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Signed-off-by:
-
Kuninori Morimoto authored
This patch updates license to use SPDX-License-Identifier instead of verbose license text. Signed-off-by:
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Signed-off-by:
-
Kuninori Morimoto authored
This patch updates license to use SPDX-License-Identifier instead of verbose license text. Signed-off-by:
-
Kuninori Morimoto authored
This patch updates license to use SPDX-License-Identifier instead of verbose license text. Signed-off-by:
-
Giuliano Belinassi authored
Previously, all pattern_masks and patterns in the chip_info table were hardcoded. Now they are generated using the PAT macros, as described in the datasheets. Signed-off-by:
Giuliano Belinassi <giuliano.belinassi@usp.br> Signed-off-by:
-
Giuliano Belinassi authored
Only the ad778x have the 'gain' status bit. Check it before updating through a new variable is_ad778x in chip_info. Signed-off-by:
Alexandru Ardelean <alexandru.ardelean@analog.com> Signed-off-by:
-
- 11 Nov, 2018 23 commits
-
-
Nishad Kamdar authored
The RD/WR pin and CONVST pin are logical inputs to the AD78xx chip as per the datasheet. Hence convert them to outputs. Signed-off-by:
Nishad Kamdar <nishadkamdar@gmail.com> Signed-off-by:
-
Nishad Kamdar authored
AD7818 does not support busy_pin functionality as per datasheet. Hence drop busy_pin when AD7818 is used. Signed-off-by:
-
Martin Blumenstingl authored
Channel 6 of the SAR ADC can be switched between two inputs: SAR_ADC_CH6 input (an actual pad on the SoC) and the signal from the temperature sensor inside the SoC. To get usable results from the temperature sensor we need to read the corresponding calibration data from the eFuse and pass it to the SAR ADC registers. If the temperature sensor is not calibrated (the eFuse data contains a bit for this) then the driver will only register the iio_chan_spec's for voltage measurements. This only enables the temperature sensor for the Meson8 SoC. Meson8b and Meson8m2 SoCs can be supported in the future as well but we first need a way to pass the fifth TSC (temperature sensor coefficient) bit to the HHI register area (apart from that the infrastructure as already implemented for Meson8 can be used). On the 64-bit SoCs (GXBB, GXL and GXM) the temperature sensor inside SAR ADC is firmware-controlled (by BL30, we can simply use the SCPI hwmon driver to get the chip temperature). To keep the devicetree interface backwards compatible we simply skip the temperature sensor initialization if no eFuse nvmem cell is passed via devicetree. The public documentation for the SAR ADC IP block does not explain how to use the registers to read the temperature. The logic from this patch is based on reading and understanding Amlogic's GPL kernel sources. Signed-off-by:
Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by:
-
Martin Blumenstingl authored
The 32-bit Meson8 SoC can use the SAR ADC to read the chip temperature. This requires setting the correct TSC (temperature sensor coefficient), which is programmed into the eFuse during the manufacturing process. Meson8b and Meson8m2 are not supported yet because they have a 5-bit TSC and only the first four bits are stored inside the SAR ADC registers. Signed-off-by:
-
Matheus Tavares authored
This patch adds a channel type check at the beginning of the ad2s90_read_raw function. Since ad2s90 has only one channel, it just checks if the given channel is the expected one and if not, return -EINVAL. Signed-off-by:
Matheus Tavares <matheus.bernardino@usp.br> Signed-off-by:
-
Victor Colombo authored
This patch adds the IIO_CHAN_INFO_SCALE mask to ad2s90_chan and implements the relative read behavior at ad2s90_read_raw. Signed-off-by:
Victor Colombo <victorcolombo@gmail.com> Signed-off-by:
-
Matheus Tavares authored
Previously, devm_iio_device_register was being called before the spi_setup call and the spi_device's max_speed_hz and mode assignments. This could lead to a race condition since the driver was still being set up after it was already made ready to use. To fix it, this patch moves the device registration to the end of ad2s90_probe. Signed-off-by:
-
Matheus Tavares authored
This patch removes an initial assignment to the variable ret at probe, that was always overwritten. Signed-off-by:
-
Matheus Tavares authored
Previously, ad2s90_probe ignored the return code from spi_setup, not handling its possible failure. This patch makes ad2s90_probe check if the code is an error code and, if so, do the following: - Call dev_err with an appropriate error message. - Return the spi_setup's error code. Note: The 'return ret' statement could be out of the 'if' block, but this whole block will be moved up in the function in the patch: 'staging:iio:ad2s90: Move device registration to the end of probe'. Signed-off-by:
-
Matheus Tavares authored
Previously, when spi_read returned an error code inside ad2s90_read_raw, the code was ignored and IIO_VAL_INT was returned. This patch makes the function return the error code returned by spi_read when it fails. Signed-off-by:
-
Renato Lui Geh authored
Variable val subtracted an uninitialized value on IIO_CHAN_INFO_OFFSET. This was fixed by assigning the correct value instead. Signed-off-by:
Renato Lui Geh <renatogeh@gmail.com> Acked-by:
-
Nishad Kamdar authored
Add device tree table for matching vendor ID. Note that as the driver is still heavily in flux and there are some non obvious aspects to a comprehensive binding, that binding will be submitted at a later date (before leaving staging!) Signed-off-by:
-
Nishad Kamdar authored
Drop gpioin flag which decides how the GPIOs are controlled as the GPIOs must be outputs for the host as per the datasheet. Removes need for platform data so that is dropped as well. Signed-off-by:
-
Nishad Kamdar authored
Use the gpiod interface instead of the deprecated old non-descriptor interface. Signed-off-by:
-
Matt Ranostay authored
Report the step range of the respective potentiometers that are possible to userspace. Signed-off-by:
Matt Ranostay <matt.ranostay@konsulko.com> Signed-off-by:
-
Charles-Antoine Couret authored
Description how to invoke ti-dac7311 driver from device tree file. Signed-off-by:
Charles-Antoine Couret <charles-antoine.couret@essensium.com> Reviewed-by:
-
Charles-Antoine Couret authored
It is a driver for Texas Instruments 8/10/12-bit 1-channel compatible with DAC6311 and DAC5311 chips. Datasheet of this chip: http://www.ti.com/lit/ds/symlink/dac7311.pdfSigned-off-by:
-
Martin Kelly authored
Add DT binding documentation for the LSM9DS1 magnetometer. Signed-off-by:
Martin Kelly <martin@martingkelly.com> Reviewed-by:
-
Slawomir Stepien authored
The type promotion will kick in, so the comparison will work. Signed-off-by:
Slawomir Stepien <sst@poczta.fm> Signed-off-by:
-
Martin Kelly authored
LIS3MDL and LSM9DS1 are missing BDU settings in their register maps, so add them. I don't have a LIS3MDL sensor to test, but this works correctly on the LSM9DS1, which has the same register map. Signed-off-by:
-
Martin Kelly authored
Update the sensor settings to support the LSM9DS1 sensor. Although the LSM9DS1 accelerometer and gyroscope are coupled together to use the same FIFO, the magnetometer is separate and can be cleanly supported without refactoring the existing driver. Signed-off-by:
-
Martin Kelly authored
Add a comment clarifying better when to use <device_name> vs <device_name>-magn in compatibility strings. Signed-off-by:
-
Matt Ranostay authored
More concise to have a pointer to tpl0102_cfg struct in the iio_priv data than an integer to an index of an array. Signed-off-by:
-
- 03 Nov, 2018 7 commits
-
-
Charles-Antoine Couret authored
Description how to invoke ad7949 driver from device tree file. Signed-off-by:
-
Charles-Antoine Couret authored
Compatible with AD7682 and AD7689 chips. It is a Analog Devices ADC driver 14/16 bits 4/8 channels with SPI protocol Datasheet of the device: http://www.analog.com/media/en/technical-documentation/data-sheets/AD7949.pdfSigned-off-by:
-
Victor Colombo authored
This patch fixes the checkpatch.pl warning: WARNING: Blank lines aren't necessary before a close brace '}' Signed-off-by:
-
Victor Colombo authored
This patch fixes the checkpatch.pl warning: WARNING: No space is necessary after a cast Signed-off-by:
-
Dan O'Donovan authored
This updates the ti-adc128s052.c file to use SPDX-License-Identifier instead of more verbose license text. Signed-off-by:
Dan O'Donovan <dan@emutex.com> Reviewed-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
-
Nicola Lunghi authored
ACPI _HID AANT1280 matches an ADC124S101 present on E3940 SKUs of the UP Squared board. Add it to the driver. Signed-off-by:
Nicola Lunghi <nicola.lunghi@emutex.com> [javier@emutex.com: fix up commit message and one checkpatch warning] Signed-off-by:
Javier Arteaga <javier@emutex.com> Signed-off-by:
-
Javier Arteaga authored
The datasheets for ADC122S021 and ADC124S021 list two more pin-compatible alternatives for each device. Add their IDs as compatible strings. Suggested-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
-
- 21 Oct, 2018 1 commit
-
-
Nishad Kamdar authored
Use the gpiod interface for rdwr_pin, convert_pin and busy_pin instead of the deprecated old non-descriptor interface. Note that Phil Reid identified that some of this code would never have worked. A follow up patch can fix that as this is just a direct change of interface. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
