From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] IIO: 1st set of fixes for 6.9
Date: Sun, 21 Apr 2024 18:57:16 +0100 [thread overview]
Message-ID: <20240421185716.72eee37e@jic23-huawei> (raw)
The following changes since commit bfa8f18691ed2e978e4dd51190569c434f93e268:
Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2024-03-22 13:31:07 -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.9a
for you to fetch changes up to 74a72baf204fd509bbe8b53eec35e39869d94341:
iio:imu: adis16475: Fix sync mode setting (2024-04-06 16:46:02 +0100)
----------------------------------------------------------------
IIO: 1st set of fixes for the 6.9 cycle.
adi,asdis16475
- Write the correct field in the register when setting the sync mode.
bosch,bmp280
- Wrong chip specific data being used for the bme280 in the SPI driver.
- Fix that we can't use chip IDs because Bosch reuses them for incompatible
devices (some require a padding byte, others don't).
maxim,max30102 (dt binding)
- Fix incorrect property check to actually match on a device from the
binding rather than a completely different one due to a typo.
memsic,mxc4005
- Fix wrong masking of interrupt register accidentally disabling temperature
compensation. Also hammer initial state to 0 as it's not documented
if interrupts are masked after reset.
- Explicit reset on probe() and resume() as some devices do not power up
correctly without a reset.
----------------------------------------------------------------
Hans de Goede (2):
iio: accel: mxc4005: Interrupt handling fixes
iio: accel: mxc4005: Reset chip on probe() and resume()
Javier Carrasco (1):
dt-bindings: iio: health: maxim,max30102: fix compatible check
Ramona Gradinariu (1):
iio:imu: adis16475: Fix sync mode setting
Vasileios Amoiridis (2):
iio: pressure: Fixes BME280 SPI driver data
iio: pressure: Fixes SPI support for BMP3xx devices
.../bindings/iio/health/maxim,max30102.yaml | 2 +-
drivers/iio/accel/mxc4005.c | 92 ++++++++++++++++++++--
drivers/iio/imu/adis16475.c | 4 +-
drivers/iio/pressure/bmp280-core.c | 1 +
drivers/iio/pressure/bmp280-spi.c | 13 +--
drivers/iio/pressure/bmp280.h | 1 +
6 files changed, 95 insertions(+), 18 deletions(-)
next reply other threads:[~2024-04-21 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 17:57 Jonathan Cameron [this message]
2024-04-24 4:27 ` [PULL] IIO: 1st set of fixes for 6.9 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=20240421185716.72eee37e@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).