From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] 1st set of IIO fixes for 6.7
Date: Mon, 11 Dec 2023 19:35:16 +0000 [thread overview]
Message-ID: <20231211193516.2a884b3f@jic23-huawei> (raw)
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.7a
for you to fetch changes up to 408d4b33c2440600418a1eb9c89eaa27cf5867ad:
iio: adc: MCP3564: fix hardware identification logic (2023-12-04 13:54:10 +0000)
----------------------------------------------------------------
First set of IIO fixes for the 6.7 cycle.
Usual mixed bunch of driver bugs. The core bug probably isn't hit
with upstream drivers, but good to get fix in place anyway.
iio-core
- Fix potential freeing of wrong iio buffer when multiple buffers used.
adi,adis16475
- Add missing spi_device_id table need for module auto-loading
- Fix untended BIT(BIT()) due to wrong macro definitions.
amlogic,meson
- Add a chip specific config for AXG soc familly which needs
a vref_select to work.
freescale,mp6050
- Fix eating of error code on failure to read from sensor.
kionixq,kx022a
- Fix scaling to comply with ABI (m/s^2 rather than micro m/s^2)
measspec,ms_sensors
- Fix wrong conversion times due to strange value mapping.
microchip,mcp3564
- Fix previously impossible to fail check on limits.
- Fix identification logic.
nxp,imx93
- Add missing channels for i.mx95.
ti,am335x
- Fix handling of error for tiadc_request_dma().
ti,tmag5273
- Fix incorrect temperature offset.
----------------------------------------------------------------
David Lechner (1):
iio: triggered-buffer: prevent possible freeing of wrong buffer
George Stark (1):
iio: adc: meson: add separate config for axg SoC family
Haibo Chen (1):
iio: adc: imx93: add four channels for imx93 adc
Javier Carrasco (3):
iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table
iio: tmag5273: fix temperature offset
iio: adc: MCP3564: fix calib_bias and calib_scale range checks
Marius Cristea (1):
iio: adc: MCP3564: fix hardware identification logic
Matti Vaittinen (1):
iio: kx022a: Fix acceleration value scaling
Nuno Sa (2):
iio: imu: adis16475: add spi_device_id table
iio: imu: adis16475: use bit numbers in assign_bit()
Su Hui (1):
iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw
Wadim Egorov (1):
iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma()
drivers/iio/accel/kionix-kx022a.c | 37 +++++--
drivers/iio/adc/imx93_adc.c | 4 +
drivers/iio/adc/mcp3564.c | 8 +-
drivers/iio/adc/meson_saradc.c | 16 ++-
drivers/iio/adc/ti_am335x_adc.c | 4 +-
drivers/iio/buffer/industrialio-triggered-buffer.c | 10 ++
drivers/iio/common/ms_sensors/ms_sensors_i2c.c | 4 +-
drivers/iio/imu/adis16475.c | 121 +++++++++++++--------
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 4 +-
drivers/iio/magnetometer/tmag5273.c | 2 +-
10 files changed, 141 insertions(+), 69 deletions(-)
next reply other threads:[~2023-12-11 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 19:35 Jonathan Cameron [this message]
2023-12-12 8:43 ` [PULL] 1st set of IIO fixes for 6.7 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=20231211193516.2a884b3f@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