From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] 1st set of IIO fixes for 6.6
Date: Thu, 5 Oct 2023 18:20:24 +0100 [thread overview]
Message-ID: <20231005182024.66b68b41@jic23-huawei> (raw)
The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.6a
for you to fetch changes up to fd39d9668f2ce9f4b05ad55e8c8d80c098073e0b:
iio: pressure: ms5611: ms5611_prom_is_valid false negative bug (2023-10-05 18:06:46 +0100)
----------------------------------------------------------------
1st set of IIO fixes for 6.6
Note last minute rebase to fix up a stale Fixes tag. All patches have been
in Linux-next for some time.
adi,ad3552r
- Fix swapped device IDs for the two parts that are supported.
adi,ad7192
- Use the right reference voltage source.
adi,ad7292
- Fix additionalProperties to be false, not true.
adi,ad74413
- Add missing Kconfig depends on IIO_BUFFER and IIO_TRIGGERED_BUFFER
adi,admv1013
- Fix up some corner cases for the mixer vgate register value.
bosch,bmp280
- Fix a null pointer dereference caused by a wrong boolean operator.
bosch,bno055
- Add missing Kconfig depends on IIO_BUFFER and IIO_TRIGGERED_BUFFER
freescale,imx8eqxp
- Fix some wrong register addresses.
google,cros_ec
- Fix a use after free if very badly timed buffer disable occurs by
holding the device in buffered mode.
infineon,dps310
- Expand a timeout so we don't hit it on working parts.
meas,m5611
- Allow for a ROM CRC of 0 as it is a valid value and there are devices
out there where it happens.
murata,irsd200
- Make sure the buffer used to build up the scan is large enough to take
the timestamp.
rohm,bu27010 binding
- Add a missing required vdd-supply
vishay,vcnl4000
- Don't power down chip in wrong place.
----------------------------------------------------------------
Alexander Zangerl (1):
iio: pressure: ms5611: ms5611_prom_is_valid false negative bug
Alisa-Dariana Roman (1):
iio: adc: ad7192: Correct reference voltage
Antoniu Miclaus (2):
iio: admv1013: add mixer_vgate corner cases
iio: addac: Kconfig: update ad74413r selections
GONG, Ruiqi (1):
iio: irsd200: fix -Warray-bounds bug in irsd200_trigger_handler
Jonathan Cameron (1):
iio: imu: bno055: Fix missing Kconfig dependencies
Krzysztof Kozlowski (1):
dt-bindings: iio: rohm,bu27010: add missing vdd-supply to example
Lakshmi Yadlapati (1):
iio: pressure: dps310: Adjust Timeout Settings
Marcelo Schmitt (1):
iio: dac: ad3552r: Correct device IDs
Mårten Lindahl (1):
iio: light: vcnl4000: Don't power on/off chip in config
Phil Elwell (1):
iio: pressure: bmp280: Fix NULL pointer exception
Philipp Rossak (1):
iio: adc: imx8qxp: Fix address for command buffer registers
Rob Herring (1):
dt-bindings: iio: adc: adi,ad7292: Fix additionalProperties on channel nodes
Tzung-Bi Shih (1):
iio: cros_ec: fix an use-after-free in cros_ec_sensors_push_data()
.../devicetree/bindings/iio/adc/adi,ad7292.yaml | 2 +-
.../bindings/iio/light/rohm,bu27010.yaml | 1 +
drivers/iio/adc/ad7192.c | 29 +++++++++++++++++++---
drivers/iio/adc/imx8qxp-adc.c | 4 +--
drivers/iio/addac/Kconfig | 2 ++
.../common/cros_ec_sensors/cros_ec_sensors_core.c | 6 ++++-
drivers/iio/dac/ad3552r.c | 4 +--
drivers/iio/frequency/admv1013.c | 4 +--
drivers/iio/imu/bno055/Kconfig | 2 ++
drivers/iio/light/vcnl4000.c | 1 -
drivers/iio/pressure/bmp280-core.c | 2 +-
drivers/iio/pressure/dps310.c | 8 +++---
drivers/iio/pressure/ms5611_core.c | 2 +-
drivers/iio/proximity/irsd200.c | 6 ++---
14 files changed, 51 insertions(+), 22 deletions(-)
next reply other threads:[~2023-10-05 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 17:20 Jonathan Cameron [this message]
2023-10-06 15:01 ` [PULL] 1st set of IIO fixes for 6.6 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=20231005182024.66b68b41@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