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: 2nd set of fixes for 6.13 (or 6.14)
Date: Wed, 15 Jan 2025 19:20:07 +0000	[thread overview]
Message-ID: <20250115192007.7e022805@jic23-huawei> (raw)

The following changes since commit e16ebd9d839d1252ff15c29d37b0cf303ddd2662:

  Merge tag 'mhi-fixes-for-v6.13' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mani/mhi into char-misc-linus (2024-12-16 16:30:58 +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.13b

for you to fetch changes up to 012b8276f08a67b9f2e2fd0f35363ae4a75e5267:

  iio: dac: ad3552r-hs: clear reset status flag (2025-01-12 13:36:01 +0000)

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

Given timing so late in cycle and that they are all confined to
specific drivers, it is fine for these to go upstream early in the
6.14 cycle.

hid-sensors
- Handle processed attention channel rather than just returning
  an error.
adi,ad3552r
- Fix output ranges for ad3541r and ad3542r.
- Clear the reset status flag so that we can pick up any resets
  during operation.
adi,ad5791
- Fix a misleading dt binding example where the sense of the
  interrupt was reversed.
adi,ad7606
- Fix some hard coded offsets that should be taking the number of
  channels on a particular part into account. These were missed
  due to some racing changes.
ams,as73211
- Fix an off by one in optimized path for just reading the colour
  channels.
bosch,bme680
- Fix type of variable passed as pointer, ensuring it works on
  big endian systems and doesn't expose uninitialized data.

----------------------------------------------------------------
Angelo Dureghello (2):
      iio: dac: ad3552r-common: fix ad3541/2r ranges
      iio: dac: ad3552r-hs: clear reset status flag

Axel Haslam (1):
      dt-bindings: iio: dac: ad5791: ldac gpio is active low

Dan Carpenter (1):
      iio: chemical: bme680: Fix uninitialized variable in __bme680_read_raw()

Guillaume Stols (1):
      iio: adc: ad7606: Fix hardcoded offset in the ADC channels

Javier Carrasco (1):
      iio: light: as73211: fix channel handling in only-color triggered buffer

Ricardo Ribalda (1):
      iio: hid-sensor-prox: Fix invalid read_raw for attention

 .../devicetree/bindings/iio/dac/adi,ad5791.yaml    |  2 +-
 drivers/iio/adc/ad7606.c                           | 48 +++++++++++++---------
 drivers/iio/adc/ad7606.h                           |  2 +-
 drivers/iio/chemical/bme680_core.c                 |  4 +-
 drivers/iio/dac/ad3552r-common.c                   |  5 +--
 drivers/iio/dac/ad3552r-hs.c                       |  6 +++
 drivers/iio/dac/ad3552r.h                          |  8 ++--
 drivers/iio/light/as73211.c                        | 24 +++++++++--
 drivers/iio/light/hid-sensor-prox.c                |  1 +
 9 files changed, 64 insertions(+), 36 deletions(-)

             reply	other threads:[~2025-01-15 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 19:20 Jonathan Cameron [this message]
2025-01-16 12:46 ` [PULL] IIO: 2nd set of fixes for 6.13 (or 6.14) 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=20250115192007.7e022805@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