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.12 - set 2
Date: Sat, 26 Oct 2024 11:39:27 +0100	[thread overview]
Message-ID: <20241026113927.333b48c1@jic23-huawei> (raw)


The following changes since commit 2471787c1f0dae6721f60ab44be37460635d3732:

  misc: microchip: pci1xxxx: add support for NVMEM_DEVID_AUTO for OTP device (2024-10-13 18:17:57 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 7bd4923940c8d67d9f3f3fde8d7c067e9e804fc6:

  iio: dac: Kconfig: Fix build error for ltc2664 (2024-10-24 18:46:04 +0100)

----------------------------------------------------------------
IIO: Fixes for 6.12, set 2

Usual mixed back of fixes for ancient bugs and some more recently
introduced problems.

gts-helper module
- Memory leak fixes for this library code to handle complex gain cases.
adi,ad7124
- Fix a divide by zero that can be triggered from userspace.
adi,ad7380
- Various supply fixes. Includes some minor rework that simplifies the
  fix though increases the apparent scale of the change.
adi,ad9832
- Avoid a potential divide by zero if clk_get_rate() returns 0.
adi,ltc2642
- Fix wrong Kconfig regmap dependency.
vishay,veml6030
- Fix a scaling problem with decimal part of processed channel.
  Note that only the illuminance channel is fixed as a larger series
  of cleanups not suitable for this point in the rc cycle removes
  the intensity channel anyway.

----------------------------------------------------------------
Javier Carrasco (1):
      iio: light: veml6030: fix microlux value calculation

Jinjie Ruan (3):
      iio: gts-helper: Fix memory leaks in iio_gts_build_avail_scale_table()
      iio: gts-helper: Fix memory leaks for the error path of iio_gts_build_avail_scale_table()
      iio: dac: Kconfig: Fix build error for ltc2664

Julien Stephan (5):
      dt-bindings: iio: adc: ad7380: fix ad7380-4 reference supply
      iio: adc: ad7380: use devm_regulator_get_enable_read_voltage()
      iio: adc: ad7380: add missing supplies
      iio: adc: ad7380: fix supplies for ad7380-4
      docs: iio: ad7380: fix supply for ad7380-4

Zicheng Qu (2):
      staging: iio: frequency: ad9832: fix division by zero in ad9832_calc_freqreg()
      iio: adc: ad7124: fix division by zero in ad7124_set_channel_odr()

 .../devicetree/bindings/iio/adc/adi,ad7380.yaml    |  21 ++++
 Documentation/iio/ad7380.rst                       |  13 +-
 drivers/iio/adc/ad7124.c                           |   2 +-
 drivers/iio/adc/ad7380.c                           | 136 ++++++++++++---------
 drivers/iio/dac/Kconfig                            |   2 +-
 drivers/iio/industrialio-gts-helper.c              |   4 +-
 drivers/iio/light/veml6030.c                       |   2 +-
 drivers/staging/iio/frequency/ad9832.c             |   7 +-
 8 files changed, 121 insertions(+), 66 deletions(-)

             reply	other threads:[~2024-10-26 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 10:39 Jonathan Cameron [this message]
2024-10-29  3:10 ` [PULL] IIO: Fixes for 6.12 - set 2 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=20241026113927.333b48c1@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