From: Abhinav Jain <jain.abhinav177@gmail.com>
To: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
alexandru.ardelean@analog.com, jlc23@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, Marcelo.Schmitt@analog.com,
dumitru.ceclan@analog.com, Jonathan.Santos@analog.com,
dragos.bogdan@analog.com,
Abhinav Jain <jain.abhinav177@gmail.com>
Subject: [PATCH v1 0/2] Add MAX22530-MAX22532 ADC Support
Date: Tue, 26 Aug 2025 02:54:50 +0530 [thread overview]
Message-ID: <cover.1756115378.git.jain.abhinav177@gmail.com> (raw)
Hello iio/maintainers,
This patch series adds initial support for the Analog Devices Maxim family
of MAX22530-MAX22532 ADCs. These are galvanically isolated, 4-channel,
multiplexed, 12-bit, analog-to-digital converters (ADC) in the MAXSafe™
family product line. An integrated, isolated, DC-DC converter powers all
fieldside circuitry, and this allows field-side diagnostics even when no
input signal is present.
The first patch adds the device tree documentation for the ADC. The DT
binding has been verified with DT_BINDING_CHECK. The second patch adds the
read functionality for raw and average ADC values from registers.
The code was tested with Raspberry Pi5 and MAX22531_EVKIT_A. With the
current driver version, it is possible to do single-shot read of ADC
sample data. On a preliminary version of the max22531 driver with
debugfs_reg_access callbacks, it was also possible to read/write from/to
different device registers and obtain the expected results.
Details of the test setup can be found at
https://wiki.analog.com/resources/tools-software/linux-drivers/iio-adc/max22531
This code was developed as part of the GSoC project for Linux
Foundation. Many thanks to my mentors Marcelo Schmitt, Ceclan Dumitru,
Jonathan Santos & Dragos Bogdan for their guidance and reviews
throughout the course of this programme.
Abhinav Jain (2):
dt-bindings: iio: adc: Add device tree binding for MAX22531 ADC
iio: adc: Add initial support for MAX22531 ADC
.../bindings/iio/adc/adi,max22531.yaml | 75 +++++++
MAINTAINERS | 8 +
drivers/iio/adc/Kconfig | 10 +
drivers/iio/adc/Makefile | 1 +
drivers/iio/adc/max22531.c | 191 ++++++++++++++++++
5 files changed, 285 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,max22531.yaml
create mode 100644 drivers/iio/adc/max22531.c
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
--
2.34.1
next reply other threads:[~2025-08-25 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 21:24 Abhinav Jain [this message]
2025-08-25 21:25 ` [PATCH v1 1/2] dt-bindings: iio: adc: Add device tree binding for MAX22531 ADC Abhinav Jain
2025-08-26 17:55 ` Conor Dooley
2025-08-28 11:27 ` Krzysztof Kozlowski
2025-08-25 21:25 ` [PATCH v1 2/2] iio: adc: Add initial support " Abhinav Jain
2025-08-26 13:10 ` kernel test robot
2025-08-31 12:27 ` Jonathan Cameron
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=cover.1756115378.git.jain.abhinav177@gmail.com \
--to=jain.abhinav177@gmail.com \
--cc=Jonathan.Santos@analog.com \
--cc=Marcelo.Schmitt@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=dumitru.ceclan@analog.com \
--cc=jlc23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).