- 23 Nov, 2022 40 commits
-
-
Jagan Teki authored
Add saradc compatible string for rockchip rv1126. Cc: linux-iio@vger.kernel.org Cc: Jonathan Cameron <jic23@kernel.org> Signed-off-by:
Jagan Teki <jagan@edgeble.ai> Acked-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Link: https://lore.kernel.org/r/20221108041400.157052-4-jagan@edgeble.aiSigned-off-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com>
-
Rob Herring authored
'contains' applies to arrays, but 'adi,dc-dc-mode' is a scalar. So drop 'contains' from the 'if' schema. Signed-off-by:
Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20221111212846.4104059-1-robh@kernel.orgSigned-off-by:
-
Lorenzo Bianconi authored
Add device bindings for lsm6dsv16x IMU sensor. Use lsm6dsv as fallback device for lsm6dsv16x since it implements all the features currently supported by lsm6dsv16x. Signed-off-by:
Lorenzo Bianconi <lorenzo@kernel.org> Acked-by:
-
Lorenzo Bianconi authored
Add support to STM LSM6DSV16X (accelerometer and gyroscope) Mems sensor. The LSM6DSV16X sensor can use LSM6DSV as fallback device since it implements all the LSM6DSV16X features currently implemented in st_lsm6dsx. Datasheet: https://www.st.com/resource/en/datasheet/lsm6dsv16x.pdfSigned-off-by:
-
Gwendal Grignou authored
From https://treexy.com/products/driver-fusion/database/sensors/semtech/sx9360-proximity/ sx9360 SAR sensor can be presented with ACPI ID SAMM0208. Whilst this does not appear to be an official ACPI ID, it is in the wild (perhaps due to a typo on the SAM PnP ID). Reported-by:
Jordi Torres <majosamaso@gmail.com> Signed-off-by:
Gwendal Grignou <gwendal@chromium.org> Link: https://lore.kernel.org/r/20221105225157.10081-1-gwendal@chromium.orgSigned-off-by:
-
Jonathan Cameron authored
Only used within this file, so should be marked static. Fixes: 2aebc223 ("iio: temperature: mlx90632 Add runtime powermanagement modes") Signed-off-by:
Crt Mori <cmo@melexis.com> Link: https://lore.kernel.org/r/20221105125108.383193-3-jic23@kernel.org
-
Jonathan Cameron authored
This call can fail so handling is necessary even if it is very unlikely. Reported-by:
coverity-bot <keescook+coverity-bot@chromium.org> Addresses-Coverity-ID: 1527134 ("Error handling issues") Fixes: 2aebc223 ("iio: temperature: mlx90632 Add runtime powermanagement modes") Signed-off-by:
-
Cosmin Tanislav authored
Add support for the following parts: * LTC2984 * LTC2986 * LTM2985 The LTC2984 is a variant of the LTC2983 with EEPROM. The LTC2986 is a variant of the LTC2983 with only 10 channels, EEPROM and support for active analog temperature sensors. The LTM2985 is software-compatible with the LTC2986. Signed-off-by:
Cosmin Tanislav <cosmin.tanislav@analog.com> Link: https://lore.kernel.org/r/20221103130041.2153295-14-demonsingur@gmail.comSigned-off-by:
-
Cosmin Tanislav authored
Add support for the following parts: * LTC2984 * LTC2986 * LTM2985 The LTC2984 is a variant of the LTC2983 with EEPROM. The LTC2986 is a variant of the LTC2983 with only 10 channels, EEPROM and support for active analog temperature sensors. The LTM2985 is software-compatible with the LTC2986. Signed-off-by:
-
Cosmin Tanislav authored
Examples should use the generic IIO node name of temperature-sensor. Fix it. Signed-off-by:
-
Cosmin Tanislav authored
The 'adi,mux-delay-config-us' property is broken. It was supposed to be in us, but the value is actually written directly to the register. Describe the fact that it is broken and how it actually works. Signed-off-by:
-
Cosmin Tanislav authored
Some descriptions are too verbose, while others are too succint. Rewrite them all. Signed-off-by:
-
Cosmin Tanislav authored
Excitation cannot be set to auto-range when using a custom thermistor or Steinhart sensor type. Default it to 1000nA to match the driver and remove the auto-range value from the enum. Signed-off-by:
-
Cosmin Tanislav authored
The driver will error out when current rotation is enabled but the RTD is not 4-wire. Require it in the binding too. Signed-off-by:
-
Cosmin Tanislav authored
The driver will error out when a custom sensor type is used but a custom sensor table is not provided. Require it in the binding too. Signed-off-by:
-
Cosmin Tanislav authored
Give a little bit of information on what each item in the matrix is supposed to be. Also, some matrices put the 'minItems' and 'maxItems' keywords in the wrong level. They should be on the same level as the 'items' keyword. Fix it. Signed-off-by:
-
Cosmin Tanislav authored
Not needed, so why have them? Signed-off-by:
-
Cosmin Tanislav authored
Addresses should be in hex, fix it. Although the driver initially specified 1-20, it can be made free-range since the address is supposed to match reg, onto which we can impose restrictions based on the compatible property value. Signed-off-by:
-
Cosmin Tanislav authored
Binding properties should have default values to let the reader know if they should change it. Add them based on driver logic. Signed-off-by:
-
Cosmin Tanislav authored
regmap_bulk_write() does not guarantee implicit DMA-safety, even though the current implementation duplicates the given buffer. Do not rely on it. Fixes: f110f318 ("iio: temperature: Add support for LTC2983") Signed-off-by:
-
Bagas Sanjaya authored
Sphinx reports two warnings on sysfs documentation for AD4130 driver: Documentation/ABI/testing/sysfs-bus-iio-adc-ad4130:2: WARNING: Unexpected indentation. Documentation/ABI/testing/sysfs-bus-iio-adc-ad4130:2: WARNING: Block quote ends without a blank line; unexpected unindent. These are due to misformatting of sinc* modes list. Format it with bullet list. Since each entry spans multiple lines, separate each with a blank line. Fixes: 62094060 ("iio: adc: ad4130: add AD4130 driver") Signed-off-by:
Bagas Sanjaya <bagasdotme@gmail.com> Link: https://lore.kernel.org/r/20221106140233.74112-1-bagasdotme@gmail.comSigned-off-by:
-
Ramona Bolboaca authored
Add support for ADXL359 device in already existing ADXL355 driver. Datasheet: https://www.analog.com/media/en/technical-documentation/data-sheets/adxl359.pdfSigned-off-by:
Ramona Bolboaca <ramona.bolboaca@analog.com> Link: https://lore.kernel.org/r/20221031105129.47740-4-ramona.bolboaca@analog.comSigned-off-by:
-
Ramona Bolboaca authored
Update ADXL355 existing documentation with documentation for ADXL359 device. Signed-off-by:
-
Ramona Bolboaca authored
Use warning instead of failing driver probe if invalid device id is detected for ADXL355 device. Signed-off-by:
-
Lorenzo Bianconi authored
Introduce device bindings for LSM6DSV IMU sensor. Signed-off-by:
-
Lorenzo Bianconi authored
Add support to STM LSM6DSV (accelerometer and gyroscope) Mems sensor. Datasheet: https://www.st.com/resource/en/datasheet/lsm6dsv.pdfSigned-off-by:
-
Lorenzo Bianconi authored
There are some hw configuration where irq0 and/or irq1 pins are not connected to the SPI or I2C/I3C controller. In order to avoid polling the output register introduce iio-sw trigger support when irq line is not available (or hw FIFO is not supported). Suggested-by:
Mario Tesi <mario.tesi@st.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Cleanup existing example (generic node name for spmi, use 4-space indentation) and add example for ADCv7 copied from Documentation/devicetree/bindings/thermal/qcom-spmi-adc-tm5.yaml. Signed-off-by:
-
Krzysztof Kozlowski authored
The second compatible item in oneOf is just an enum, not a list. Signed-off-by:
-
Jonathan Cameron authored
As everything else is now handled by devm managed releases the triggered buffer setup and IIO device registration can also be moved over to their devm forms allowing dropping of remove(). Only user of drvdata associated with the struct device was the remove function, so also drop the platform_set_drvdata() call. Signed-off-by:
Nuno Sá <nuno.sa@analog.com> Link: https://lore.kernel.org/r/20221016170950.387751-6-jic23@kernel.org
-
Jonathan Cameron authored
It is presumably safe to call the powerdown whether or not we are in the commented shared state (the driver always did this). The power down was previously out of order wrt to the probe() function so move using devm_ will ensure it occurs after the userspace interfaces are removed. Signed-off-by:
-
Jonathan Cameron authored
As this driver just enables clock in probe() and disables in remove() we can use this new function to replace boilerplate and simplify error paths. Signed-off-by:
-
Jonathan Cameron authored
As the voltage of this regulator is queried, we cannot use the devm_regulator_get_enable() call and have to role our own disable. Signed-off-by:
-
Jonathan Cameron authored
There are lots of uses of this in probe() and we are about to introduce some more, so add a local variable to simplify this. Signed-off-by:
-
Matti Vaittinen authored
The iio_triggered_buffer_setup_ext() and the devm_iio_kfifo_buffer_setup_ext() were changed by commit 15097c7a ("iio: buffer: wrap all buffer attributes into iio_dev_attr") to silently expect that all attributes given in buffer_attrs array are device-attributes. This expectation was not forced by the API - and some drivers did register attributes created by IIO_CONST_ATTR(). When using IIO_CONST_ATTRs the added attribute "wrapping" does not copy the pointer to stored string constant and when the sysfs file is read the kernel will access to invalid location. Change the function signatures to expect an array of iio_dev_attrs to avoid similar errors in the future. Merge conflict resolved whilst applying due to patch crossing with two new drivers (kx022a accelerometer and ad4130 ADC). Signed-off-by:
Matti Vaittinen <mazziesaccount@gmail.com> Tested-by:
Claudiu Beznea <claudiu.beznea@microchip.com> Link: https://lore.kernel.org/r/63f54787a684eb1232f1c5d275a09c786987fe4a.1664782676.git.mazziesaccount@gmail.comSigned-off-by:
-
Matti Vaittinen authored
Slightly simplify by dropping open-coded constant data iio_dev_attr functions and using the IIO_STATIC_CONST_DEVICE_ATTR() instead. Signed-off-by:
-
Matti Vaittinen authored
Slightly simplify by dropping open-coded constant data iio_dev_attr functions and using the IIO_STATIC_CONST_DEVICE_ATTR() instead. Signed-off-by:
-
Matti Vaittinen authored
Slightly simplify by dropping open-coded constant data iio_dev_attr functions and using the IIO_STATIC_CONST_DEVICE_ATTR() instead. Signed-off-by:
-
Matti Vaittinen authored
Slightly simplify by dropping open-coded constant data iio_dev_attr functions and using the IIO_STATIC_CONST_DEVICE_ATTR() instead. Signed-off-by:
-
Matti Vaittinen authored
Add IIO_STATIC_CONST_DEVICE_ATTR macro for creating an read-only iio_dev_attr which returns constant value. This macro is intended to be used when replacing the IIO_CONST_ATTR - attributes for triggered buffers because the triggered buffer attributes must be of type iio_dev_attr. Signed-off-by:
-
