From: Kim Seer Paller <kimseer.paller@analog.com>
To: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
Michael Hennerich <michael.hennerich@analog.com>
Subject: [PATCH 0/4] Add driver for LTC2664 and LTC2672
Date: Fri, 12 Apr 2024 11:20:58 +0800 [thread overview]
Message-ID: <20240412032102.136071-1-kimseer.paller@analog.com> (raw)
The LTC2664 is a 4 Channel, Voltage Output SoftSpan DAC while LTC2672 is a 5
channel, Current Output Softspan DAC. The ABI defined for the driver:
LTC2664 - toggle mode channels:
* out_voltageY_toggle_en
* out_voltageY_raw0
* out_voltageY_raw1
* out_voltageY_symbol
LTC2672 - toggle mode channels:
* out_currentY_toggle_en
* out_currentY_raw0
* out_currentY_raw1
* out_currentY_symbol
Default channels won't have any of the above ABIs.
Kim Seer Paller (4):
dt-bindings: iio: dac: Add adi,ltc2664.yaml
iio: ABI: add ABI file for the LTC2664 DAC
iio: ABI: add ABI file for the LTC2672 DAC
iio: dac: ltc2664: Add driver for LTC2664 and LTC2672
.../ABI/testing/sysfs-bus-iio-dac-ltc2664 | 30 +
.../ABI/testing/sysfs-bus-iio-dac-ltc2672 | 30 +
.../bindings/iio/dac/adi,ltc2664.yaml | 230 +++++
MAINTAINERS | 11 +
drivers/iio/dac/Kconfig | 11 +
drivers/iio/dac/Makefile | 1 +
drivers/iio/dac/ltc2664.c | 785 ++++++++++++++++++
7 files changed, 1098 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2664
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2672
create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ltc2664.yaml
create mode 100644 drivers/iio/dac/ltc2664.c
base-commit: 27eea4778db8268cd6dc80a5b853c599bd3099f1
--
2.34.1
next reply other threads:[~2024-04-12 3:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 3:20 Kim Seer Paller [this message]
2024-04-12 3:20 ` [PATCH 1/4] dt-bindings: iio: dac: Add adi,ltc2664.yaml Kim Seer Paller
2024-04-12 5:50 ` Krzysztof Kozlowski
2024-04-13 14:54 ` Jonathan Cameron
2024-04-16 14:16 ` Paller, Kim Seer
2024-04-12 21:23 ` David Lechner
2024-04-13 15:06 ` Jonathan Cameron
2024-04-13 15:11 ` Jonathan Cameron
2024-04-13 16:21 ` David Lechner
2024-04-13 17:10 ` Jonathan Cameron
2024-04-16 14:40 ` Paller, Kim Seer
2024-04-20 10:13 ` Jonathan Cameron
2024-04-12 3:21 ` [PATCH 2/4] iio: ABI: add ABI file for the LTC2664 DAC Kim Seer Paller
2024-04-12 21:26 ` David Lechner
2024-04-13 15:25 ` Jonathan Cameron
2024-04-13 20:38 ` David Lechner
2024-04-15 12:45 ` Nuno Sá
2024-04-20 10:22 ` Jonathan Cameron
2024-04-12 3:21 ` [PATCH 3/4] iio: ABI: add ABI file for the LTC2672 DAC Kim Seer Paller
2024-04-13 15:26 ` Jonathan Cameron
2024-04-16 14:18 ` Paller, Kim Seer
2024-04-20 10:23 ` Jonathan Cameron
2024-04-12 3:21 ` [PATCH 4/4] iio: dac: ltc2664: Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-04-13 15:55 ` 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=20240412032102.136071-1-kimseer.paller@analog.com \
--to=kimseer.paller@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).