From: Kyle Hsieh <kylehsieh1995@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kyle Hsieh <kylehsieh1995@gmail.com>
Subject: [PATCH v3 0/2] iio: adc: Add support for Texas Instruments ADS112C04
Date: Wed, 05 Aug 2026 13:38:19 +0800 [thread overview]
Message-ID: <20260805-ti-ads112c04-driver-v3-0-49f436829e01@gmail.com> (raw)
This patch series introduces support for the Texas Instruments ADS112C04
Analog-to-Digital Converters.
The ADS112C04 (16-bit) is precision, low-power, delta-sigma ADCs with
an I2C interface. They feature a flexible input multiplexer supporting
single-ended and differential measurements, a programmable gain amplifier,
and an internal voltage reference.
Note: While this chip shares similarities with the ADS112C14 (currently
being upstreamed by David Lechner), the register maps and feature sets
are sufficiently different to warrant a separate driver. However, the
DT bindings and channel parsing logic have been aligned with the
ADS112C14 conventions.
This initial submission provides a minimal feature set (single-shot
conversions and basic DRDY interrupt) covering current use cases.
Signed-off-by: Kyle Hsieh <kylehsieh1995@gmail.com>
---
Changes in v3:
- dt-bindings: iio: adc: ti,ads112c04:
- Resolved dt_binding_check errors by removing redundant $ref for
standard unit suffixes and fixing YAML array syntax.
- Added full hardware capability descriptions (excitation-channels,
excitation-current-nanoamp, burn-out-current-nanoamp,
reference-sources) as suggested by David Lechner.
- Restricted the reg maximum to 11 and updated the regex to
^channel@[0-9a-b]$ to accurately reflect the 12 possible MUX
combinations.
- iio: adc: ti-ads112c04:
- Transitioned all I2C read/write wrappers to use SMBus APIs
(i2c_smbus_read_byte_data, i2c_smbus_read_word_data, etc.) to
gracefully handle I2C errors, NACKs, and Repeated Starts, addressing
feedback from Joshua Crofts and Jonathan Cameron.
- Added forward compatibility checks in probe() and parse_channels()
using dev_err_probe() to return -EOPNOTSUPP for unimplemented DT
properties.
- Reverted devm_request_irq() flags to 0 to let the driver inherit the
trigger type strictly from the DT, per Jonathan Cameron's advice.
- Reduced the data wait timeout to 100ms, reflecting the chip's slowest
data rate of 20 SPS.
- Fixed #include alphabetical sorting, grouped <linux/iio/*> headers,
and added missing headers.
- Fixed variable declaration ordering (reverse xmas tree) and updated
variable naming to vref_mV (SI unit exception).
- Optimized GPIO reset logic using GPIOD_OUT_HIGH.
- Link to v2: https://lore.kernel.org/r/20260731-ti-ads112c04-driver-v2-0-aab0168c3c01@gmail.com
Changes in v2:
- Replaced `vref-supply` with `refp-supply` and `refn-supply` to accurately reflect hardware.
- Refactored the driver to dynamically parse channel configurations and routing from DT child nodes.
- Modernized the driver using kernel macros.
- Handled endianness elegantly.
- Added hardware reset fallback logic.
- Inherited IRQ trigger type from device tree instead of hardcoding.
- Fixed a bug where the MUX software cache could desync from hardware if the I2C write failed.
- Added strict return value checking for all I2C writes during probe.
- Updated the `i2c_device_id` array to use C99 named initializers.
- Link to v1: https://lore.kernel.org/r/20260728-ti-ads112c04-driver-v1-0-475efe4e2b78@gmail.com
---
Kyle Hsieh (2):
dt-bindings: iio: adc: ti,ads112c04: Add binding for ADS112C04
iio: adc: ti-ads112c04: Add support for TI ADS112C04
.../devicetree/bindings/iio/adc/ti,ads112c04.yaml | 146 +++++++
drivers/iio/adc/Kconfig | 10 +
drivers/iio/adc/Makefile | 1 +
drivers/iio/adc/ti-ads112c04.c | 423 +++++++++++++++++++++
4 files changed, 580 insertions(+)
---
base-commit: 4539944e515183668109bdf4d0c3d7d228383d88
change-id: 20260724-ti-ads112c04-driver-be7e89047834
Best regards,
--
Kyle Hsieh <kylehsieh1995@gmail.com>
next reply other threads:[~2026-08-05 5:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 5:38 Kyle Hsieh [this message]
2026-08-05 5:38 ` [PATCH v3 1/2] dt-bindings: iio: adc: ti,ads112c04: Add binding for ADS112C04 Kyle Hsieh
2026-08-05 5:50 ` sashiko-bot
2026-08-05 6:24 ` Rob Herring (Arm)
2026-08-07 20:15 ` David Lechner
2026-08-07 20:23 ` David Lechner
2026-08-05 5:38 ` [PATCH v3 2/2] iio: adc: ti-ads112c04: Add support for TI ADS112C04 Kyle Hsieh
2026-08-05 5:49 ` sashiko-bot
2026-08-07 21:01 ` David Lechner
2026-08-05 6:43 ` [PATCH v3 0/2] iio: adc: Add support for Texas Instruments ADS112C04 Krzysztof Kozlowski
2026-08-05 6:46 ` Krzysztof Kozlowski
2026-08-05 7:44 ` Kyle Hsieh
2026-08-07 20:28 ` David Lechner
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=20260805-ti-ads112c04-driver-v3-0-49f436829e01@gmail.com \
--to=kylehsieh1995@gmail.com \
--cc=andy@kernel.org \
--cc=broonie@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=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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