From: Andrei Stancovici <andrei.stancovici@analog.com>
To: "Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Liam Beguin" <liambeguin@gmail.com>,
linux@analog.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andrei Stancovici <andrei.stancovici@analog.com>
Subject: [PATCH v3 0/3] iio: adc: add LTC2499 features support
Date: Wed, 2 Sep 2026 09:44:09 +0300 [thread overview]
Message-ID: <20260902064415.132588-1-andrei.stancovici@analog.com> (raw)
This series adds LTC2499 support on top of the existing LTC2497 driver.
It includes:
- a small binding title correction for LTC2499,
- the LTC2499 internal temperature channel,
- the LTC2499 2x conversion speed mode exposed via sampling_frequency.
Validation performed on Raspberry Pi 4 with a DC1012A-A board:
- temperature raw/scale/offset read correctly,
- voltage channels remain sane after temperature reads,
- sampling_frequency 1x/2x switching works,
- pyadi-iio LTC2499 validation passed,
- hardware-in-the-loop M2K validation passed.
Changes in v2:
- guard against regulator_get_voltage() returning 0 in the temperature offset path,
- replace LTC2499 two-byte stack command buffers with a DMA-safe buffer,
- use ABSOLUTE_ZERO_MILLICELSIUS and standard SI unit multipliers,
- make channel-count handling explicit,
- clean up includes and iterator usage,
- update conversion-state handling for interrupted waits,
- clarify conversion-time rounding and LTC2499 configuration behavior.
Changes in v3:
- revert the LTC2499 two-byte command path to a local stack buffer and remove the incorrect DMA-safe rationale
- use a standard zero-value comparison in the temperature offset path
- simplify the temperature offset derivation comments
- simplify the temperature offset computation
- adjust ltc2497_chip_info field placement based on pahole analysis
- apply review-driven comment and formatting cleanups
Andrei Stancovici (3):
dt-bindings: iio: adc: lltc,ltc2497: add LTC2499 to title
iio: adc: ltc2497: add LTC2499 internal temperature channel
iio: adc: ltc2497: add 2x conversion speed mode
.../bindings/iio/adc/lltc,ltc2497.yaml | 2 +-
drivers/iio/adc/ltc2497-core.c | 235 +++++++++++++++++-
drivers/iio/adc/ltc2497.c | 39 +++
drivers/iio/adc/ltc2497.h | 46 +++-
4 files changed, 309 insertions(+), 13 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-02 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 6:44 Andrei Stancovici [this message]
2026-09-02 6:44 ` [PATCH v3 1/3] dt-bindings: iio: adc: lltc,ltc2497: add LTC2499 to title Andrei Stancovici
2026-09-02 6:44 ` [PATCH v3 2/3] iio: adc: ltc2497: add LTC2499 internal temperature channel Andrei Stancovici
2026-09-02 6:44 ` [PATCH v3 3/3] iio: adc: ltc2497: add 2x conversion speed mode Andrei Stancovici
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=20260902064415.132588-1-andrei.stancovici@analog.com \
--to=andrei.stancovici@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=nuno.sa@analog.com \
--cc=robh@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