From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org, linux-iio@vger.kernel.org
Subject: [PULL] IIO: 2nd set of fixes for 6.17 (or 6.18 merge window given timing)
Date: Tue, 16 Sep 2025 09:04:13 +0100 [thread overview]
Message-ID: <20250916090413.48a78014@jic23-huawei> (raw)
The following changes since commit 1b237f190eb3d36f52dffe07a40b5eb210280e00:
Linux 6.17-rc3 (2025-08-24 12:04:12 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-fixes-for-6.17b
for you to fetch changes up to 3379c900320954d768ed9903691fb2520926bbe3:
iio: dac: ad5421: use int type to store negative error codes (2025-09-01 20:43:43 +0100)
----------------------------------------------------------------
IIO: 2nd set of fixes for the 6.17 cycle (or 6.18 merge window)
adi,ad5360
- Use a signed int type to be able to hold a potential error return.
adi,ad5421
- Use a signed int type to be able to hold a potential error return.
adi,adf4350
- Ensure rules on VCO frequency and prescaler values are met.
- Fix a wrong offset for the clock divisor control field.
xilinx,ams
- Unmask alarms correctly if an event is disabled and re-enabled.
- Fix a wrong register field mask.
----------------------------------------------------------------
Aleksandar Gerasimovski (1):
iio/adc/pac1934: fix channel disable configuration
Michael Hennerich (2):
iio: frequency: adf4350: Fix prescaler usage.
iio: frequency: adf4350: Fix ADF4350_REG3_12BIT_CLKDIV_MODE
Qianfeng Rong (2):
iio: dac: ad5360: use int type to store negative error codes
iio: dac: ad5421: use int type to store negative error codes
Sean Anderson (2):
iio: xilinx-ams: Unmask interrupts after updating alarms
iio: xilinx-ams: Fix AMS_ALARM_THR_DIRECT_MASK
drivers/iio/adc/pac1934.c | 20 +++++++++++++--
drivers/iio/adc/xilinx-ams.c | 47 +++++++++++++++++++----------------
drivers/iio/dac/ad5360.c | 2 +-
drivers/iio/dac/ad5421.c | 2 +-
drivers/iio/frequency/adf4350.c | 20 +++++++++------
include/linux/iio/frequency/adf4350.h | 2 +-
6 files changed, 60 insertions(+), 33 deletions(-)
next reply other threads:[~2025-09-16 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 8:04 Jonathan Cameron [this message]
2025-09-16 8:31 ` [PULL] IIO: 2nd set of fixes for 6.17 (or 6.18 merge window given timing) 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=20250916090413.48a78014@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