Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] IIO fixes for 6.8 - second set.
Date: Thu, 29 Feb 2024 20:07:03 +0000	[thread overview]
Message-ID: <20240229200703.52697131@jic23-huawei> (raw)

The following changes since commit e20f378d993b1034eebe3ae78e67f3ed10e75356:

  nvmem: include bit index in cell sysfs file name (2024-02-14 16:28:16 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.8b

for you to fetch changes up to 11dadb631007324c7a8bcb2650eda88ed2b9eed0:

  iio: accel: adxl367: fix I2C FIFO data register (2024-02-25 14:31:14 +0000)

----------------------------------------------------------------
IIO: 2nd set of fixes for the 6.8 cycle.

Given this is very late these can wait for the 6.9 cycle if you would
prefer.

adi,adxl367
- Sleep for 15ms after reset to avoid reading before the device is awake.
- Fix FIFO register address.
asc,dlhl60d
- Avoid uninitialized data leak to user-space. Also suppress a false
  positive clang warning by refactoring a loop.
bosch,bmp280
- Fix missing extra byte in SPI reads from BMP38x and BMP390 parts
invensense,mpu6050
- Fix handing of empty FIFO which can happen due to a race condition.
- Make sure frequency can be updated more than once when the FIFO is not
  enabled.

----------------------------------------------------------------
Cosmin Tanislav (2):
      iio: accel: adxl367: fix DEVID read after reset
      iio: accel: adxl367: fix I2C FIFO data register

Jean-Baptiste Maneyrol (2):
      iio: imu: inv_mpu6050: fix FIFO parsing when empty
      iio: imu: inv_mpu6050: fix frequency setting when chip is off

Kees Cook (1):
      iio: pressure: dlhl60d: Initialize empty DLH bytes

Vasileios Amoiridis (1):
      iio: pressure: Fixes BMP38x and BMP390 SPI support

 drivers/iio/accel/adxl367.c                   |  8 +++--
 drivers/iio/accel/adxl367_i2c.c               |  2 +-
 drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c    |  2 ++
 drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c |  5 +++
 drivers/iio/pressure/bmp280-spi.c             | 50 ++++++++++++++++++++++++++-
 drivers/iio/pressure/dlhl60d.c                |  7 ++--
 6 files changed, 66 insertions(+), 8 deletions(-)

             reply	other threads:[~2024-02-29 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 20:07 Jonathan Cameron [this message]
2024-03-02 18:55 ` [PULL] IIO fixes for 6.8 - second set Greg KH
2024-03-02 18:56 ` 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=20240229200703.52697131@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