linux-stable.git/drivers/iio, branch v6.18

iio: accel: bmc150: Fix irq assumption regression

2025-11-11T20:22:23+00:00

The code in bmc150-accel-core.c unconditionally calls
bmc150_accel_set_interrupt() in the iio_buffer_setup_ops,
such as on the runtime PM resume path giving a kernel
splat like this if the device has no interrupts:

Unable to handle kernel NULL pointer dereference at virtual
  address 00000001 when read

PC is at bmc150_accel_set_interrupt+0x98/0x194
LR is at __pm_runtime_resume+0x5c/0x64
(...)
Call trace:
bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108
bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc
__iio_update_buffers from enable_store+0x84/0xc8
enable_store from kernfs_fop_write_iter+0x154/0x1b4

This bug seems to have been in the driver since the beginning,
but it only manifests recently, I do not know why.

Store the IRQ number in the state struct, as this is a common
pattern in other drivers, then use this to determine if we have
IRQ support or not.

Cc: stable@vger.kernel.org
Signed-off-by: Linus Walleij 
Reviewed-by: Andy Shevchenko 
Reviewed-by: Nuno Sá 
Signed-off-by: Jonathan Cameron

iio: st_lsm6dsx: Fixed calibrated timestamp calculation

2025-10-27T13:29:12+00:00

The calibrated timestamp is calculated from the nominal value using the
formula:
  ts_gain[ns] ≈ ts_sensitivity - (ts_trim_coeff * val) / 1000.

The values of ts_sensitivity and ts_trim_coeff are not the same for all
devices, so it is necessary to differentiate them based on the part name.
For the correct values please consult the relevant AN.

Fixes: cb3b6b8e1bc0 ("iio: imu: st_lsm6dsx: add odr calibration feature")
Signed-off-by: Mario Tesi 
Acked-by: Lorenzo Bianconi 
Signed-off-by: Jonathan Cameron

iio: humditiy: hdc3020: fix units for thresholds and hysteresis

2025-10-19T10:46:24+00:00

According to the ABI the units after application of scale and offset are
milli degree celsius for temperature thresholds and milli percent for
relative humidity thresholds. Currently the resulting units are degree
celsius for temperature thresholds and hysteresis and percent for relative
humidity thresholds and hysteresis. Change scale factor to fix this issue.

Fixes: 3ad0e7e5f0cb ("iio: humidity: hdc3020: add threshold events support")
Reported-by: Chris Lesiak 
Reviewed-by: Javier Carrasco 
Signed-off-by: Dimitri Fedrau 
Cc: 
Signed-off-by: Jonathan Cameron

iio: humditiy: hdc3020: fix units for temperature and humidity measurement

2025-10-19T10:46:24+00:00

According to the ABI the units after application of scale and offset are
milli degrees for temperature measurements and milli percent for relative
humidity measurements. Currently the resulting units are degree celsius for
temperature measurements and percent for relative humidity measurements.
Change scale factor to fix this issue.

Fixes: c9180b8e39be ("iio: humidity: Add driver for ti HDC302x humidity sensors")
Reported-by: Chris Lesiak 
Suggested-by: Chris Lesiak 
Reviewed-by: Javier Carrasco 
Signed-off-by: Dimitri Fedrau 
Cc: 
Signed-off-by: Jonathan Cameron

iio: imu: st_lsm6dsx: fix array size for st_lsm6dsx_settings fields

2025-10-19T10:46:18+00:00

The `decimator` and `batch` fields of struct st_lsm6dsx_settings
are arrays indexed by sensor type, not by sensor hardware
identifier; moreover, the `batch` field is only used for the
accelerometer and gyroscope.
Change the array size for `decimator` from ST_LSM6DSX_MAX_ID to
ST_LSM6DSX_ID_MAX, and change the array size for `batch` from
ST_LSM6DSX_MAX_ID to 2; move the enum st_lsm6dsx_sensor_id
definition so that the ST_LSM6DSX_ID_MAX value is usable within
the struct st_lsm6dsx_settings definition.

Fixes: 801a6e0af0c6c ("iio: imu: st_lsm6dsx: add support to LSM6DSO")
Signed-off-by: Francesco Lavra 
Acked-by: Lorenzo Bianconi 
Cc: 
Signed-off-by: Jonathan Cameron

iio: accel: fix ADXL355 startup race condition

2025-10-18T13:07:16+00:00

There is an race-condition where device is not full working after SW reset.
Therefore it's necessary to wait some time after reset and verify shadow
registers values by reading and comparing the values before/after reset.
This mechanism is described in datasheet at least from revision D.

Fixes: 12ed27863ea3 ("iio: accel: Add driver support for ADXL355")
Signed-off-by: Valek Andrej 
Signed-off-by: Kessler Markus 
Cc: 
Signed-off-by: Jonathan Cameron

iio: adc: ad7124: fix temperature channel

2025-10-13T07:38:09+00:00

Fix temperature channel not working due to gain and offset not being
initialized.  For channels other than the voltage ones calibration is
skipped (which is OK).  However that results in the calibration register
values tracked in st->channels[i].cfg all being zero.  These zeros are
later written to hardware before a measurement is made which caused the
raw temperature readings to be always 8388608 (0x800000).

To fix it, we just make sure the gain and offset values are set to the
default values and still return early without doing an internal
calibration.

While here, add a comment explaining why we don't bother calibrating
the temperature channel.

Fixes: 47036a03a303 ("iio: adc: ad7124: Implement internal calibration at probe time")
Reviewed-by: Marcelo Schmitt 
Signed-off-by: David Lechner 
Reviewed-by: Uwe Kleine-König 
Cc: 
Signed-off-by: Jonathan Cameron

iio:common:ssp_sensors: Fix an error handling path ssp_probe()

2025-10-13T07:38:09+00:00

If an error occurs after a successful mfd_add_devices() call, it should be
undone by a corresponding mfd_remove_devices() call, as already done in the
remove function.

Fixes: 50dd64d57eee ("iio: common: ssp_sensors: Add sensorhub driver")
Signed-off-by: Christophe JAILLET 
Reviewed-by: Nuno Sá 
Cc: 
Signed-off-by: Jonathan Cameron

iio: adc: ad7280a: fix ad7280_store_balance_timer()

2025-10-13T07:38:08+00:00

Use correct argument to iio_str_to_fixpoint() to parse 3 decimal places.

iio_str_to_fixpoint() has a bit of an unintuitive API where the
fract_mult parameter is the multiplier of the first decimal place as if
it was already an integer.  So to get 3 decimal places, fract_mult must
be 100 rather than 1000.

Fixes: 96ccdbc07a74 ("staging:iio:adc:ad7280a: Standardize extended ABI naming")
Signed-off-by: David Lechner 
Reviewed-by: Nuno Sá 
Cc: 
Signed-off-by: Jonathan Cameron

iio: buffer-dmaengine: enable .get_dma_dev()

2025-10-13T07:38:08+00:00

Wire up the .get_dma_dev() callback to use the DMA buffer infrastructure's
implementation. This ensures that DMABUF operations use the correct DMA
device for mapping, which is essential for proper operation on systems
where memory is mapped above the 32-bit range.

Without this callback, the core would fall back to using the IIO device's
parent, which may not have the appropriate DMA mask configuration for
high memory access.

Fixes: 7a86d469983a ("iio: buffer-dmaengine: Support new DMABUF based userspace API")
Reviewed-by: David Lechner 
Signed-off-by: Nuno Sá 
Cc: 
Signed-off-by: Jonathan Cameron