From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, gregkh@linuxfoundation.org
Subject: [PULL] IIO: 1st set of fixes for the 6.15 cycle
Date: Fri, 25 Apr 2025 09:03:16 +0100 [thread overview]
Message-ID: <20250425090316.0c0bde91@jic23-huawei> (raw)
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.15a
for you to fetch changes up to 609bc31eca06c7408e6860d8b46311ebe45c1fef:
iio: adis16201: Correct inclinometer channel resolution (2025-04-21 14:58:31 +0100)
----------------------------------------------------------------
IIO: 1st set of fixes for the 6.15 cycle.
A mixed bunch of fixes for new and ancient issues found.
multiple driver sets:
- Stop leaking wakeup sources on device unbind.
- Various timestamp alignment fixes that came up as part of work to add
runtime checks on buffer sizing. Similarly a DMA buffer safety fix.
hid-sensor-prox
- Fix a bad merge conflict resolution that lost some variable assignments.
- Fix handling of scale when multiple channels present.
- Fix wrong application of exponent in offset calculation.
adi,ad7380
- Disable offload before using the SPI bus.
- Fix a wrong shift on the event threshold.
adi,ad7606
- Check there is a sw_mode_config callback before using it as not
all busses define one.
- Fix missing hold of chip select on in multi word accesses.
adi,ad7861
- Fix wrong logic on storing of mode.
adi,adis16201
- Wrong resolution for inclinometer channel.
adi,adxl367
- Use fresh ODR when setting activity time, not previous value.
bosch,bmi270
- Fix initial sampling frequency configuration which was using the
wrong register mask.
rockchip,saradc
- Fix clock initialization sequence to get frequency after get + enable,
not before.
st,lsm6dsx
- Avoid 2 potential infinite loops if we see empty FIFOs
ti,opt3001
- Fix a deadlock that can occur due to concurrent access to a flag.
----------------------------------------------------------------
Angelo Dureghello (1):
iio: adc: ad7606: fix serial register access
David Lechner (8):
iio: adc: ad7380: disable offload before using SPI bus
iio: adc: ad7606: check for NULL before calling sw_mode_config()
iio: adc: ad7380: fix event threshold shift
iio: imu: inv_mpu6050: align buffer for timestamp
iio: chemical: sps30: use aligned_s64 for timestamp
iio: chemical: pms7003: use aligned_s64 for timestamp
iio: imu: adis16550: align buffers for timestamp
iio: pressure: mprls0025pa: use aligned_s64 for timestamp
Gabriel Shahrouzi (2):
staging: iio: adc: ad7816: Correct conditional logic for store mode
iio: adis16201: Correct inclinometer channel resolution
Gustavo Silva (1):
iio: imu: bmi270: fix initial sampling frequency configuration
Jonathan Cameron (5):
iio: temp: maxim-thermocouple: Fix potential lack of DMA safe buffer.
iio: accel: adxl355: Make timestamp 64-bit aligned using aligned_s64
iio: adc: dln2: Use aligned_s64 for timestamp
iio: adc: ad7768-1: Fix insufficient alignment of timestamp.
iio: adc: ad7266: Fix potential timestamp alignment issue.
Krzysztof Kozlowski (3):
iio: accel: fxls8962af: Fix wakeup source leaks on device unbind
iio: adc: qcom-spmi-iadc: Fix wakeup source leaks on device unbind
iio: imu: st_lsm6dsx: Fix wakeup source leaks on device unbind
Lothar Rubusch (1):
iio: accel: adxl367: fix setting odr for activity time update
Luca Ceresoli (1):
iio: light: opt3001: fix deadlock due to concurrent flag access
Silvano Seva (2):
iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo
iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_tagged_fifo
Simon Xue (1):
iio: adc: rockchip: Fix clock initialization sequence
Zhang Lixu (3):
iio: hid-sensor-prox: Restore lost scale assignments
iio: hid-sensor-prox: support multi-channel SCALE calculation
iio: hid-sensor-prox: Fix incorrect OFFSET calculation
drivers/iio/accel/adis16201.c | 4 +--
drivers/iio/accel/adxl355_core.c | 2 +-
drivers/iio/accel/adxl367.c | 10 ++-----
drivers/iio/accel/fxls8962af-core.c | 7 +++--
drivers/iio/adc/ad7266.c | 2 +-
drivers/iio/adc/ad7380.c | 32 +++++++++++++++-------
drivers/iio/adc/ad7606.c | 11 ++++++--
drivers/iio/adc/ad7606_spi.c | 2 +-
drivers/iio/adc/ad7768-1.c | 2 +-
drivers/iio/adc/dln2-adc.c | 2 +-
drivers/iio/adc/qcom-spmi-iadc.c | 4 ++-
drivers/iio/adc/rockchip_saradc.c | 17 ++++++------
drivers/iio/chemical/pms7003.c | 5 ++--
drivers/iio/chemical/sps30.c | 2 +-
.../iio/common/hid-sensors/hid-sensor-attributes.c | 4 +++
drivers/iio/imu/adis16550.c | 2 +-
drivers/iio/imu/bmi270/bmi270_core.c | 6 ++--
drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c | 2 +-
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c | 6 ++++
drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_core.c | 7 +++--
drivers/iio/light/hid-sensor-prox.c | 22 +++++++++------
drivers/iio/light/opt3001.c | 5 ++--
drivers/iio/pressure/mprls0025pa.h | 17 ++++--------
drivers/iio/temperature/maxim_thermocouple.c | 2 +-
drivers/staging/iio/adc/ad7816.c | 2 +-
25 files changed, 104 insertions(+), 73 deletions(-)
next reply other threads:[~2025-04-25 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 8:03 Jonathan Cameron [this message]
2025-05-01 15:49 ` [PULL] IIO: 1st set of fixes for the 6.15 cycle Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250425090316.0c0bde91@jic23-huawei \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-iio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox