From: "Nuno Sá" <nuno.sa@analog.com>
To: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>
Subject: [PATCH v2 0/3] Add support for LTC2688
Date: Sat, 15 Jan 2022 10:27:02 +0100 [thread overview]
Message-ID: <20220115092705.491-1-nuno.sa@analog.com> (raw)
The ABI defined for this driver has some subtleties that were previously
discussed in this RFC [1]. This might not be the final state but,
hopefully, we are close to it:
toggle mode channels:
* out_voltageY_toggle_en
* out_voltageY_raw0
* out_voltageY_raw1
* out_voltageY_symbol
dither mode channels:
* out_voltageY_dither_en
* out_voltageY_dither_raw
* out_voltageY_dither_raw_available
* out_voltageY_dither_offset
* out_voltageY_dither_frequency
* out_voltageY_dither_frequency_available
* out_voltageY_dither_phase
* out_voltageY_dither_phase_available
Default channels won't have any of the above ABIs. A channel is toggle
capable if the devicetree 'adi,toggle-mode' flag is set. For dither, the
assumption is more silent. If 'adi,toggle-mode' is not given and a
channel is associated with a TGPx pin through 'adi,toggle-dither-input',
then the channel is assumed to be dither capable (there's no point in
having a dither capable channel without an input clock).
changes in v2:
ltc2688:
* Use local buffer for regmap read. Do not assume that reg is part of
larger buffer;
* Renamed GPIO to "clr" so that is consistent with the datasheet;
* Renamed 'mask' and 'm' to info. 'mask' is a thing from the past;
* Removed 'LTC2688_CHAN_TOGGLE()' and defined to static ext_info arrays;
* Use 'regmap_set_bits' to set external ref;
* Use FIELD_{PREP|GET} for dither amplitude and channel calibbias where
only 13bits are used;
* Use 'regmap_write()' instead of update_bits for channels settings;
* Init 'val' at the beginning of the channel configuration loop
(and drop mask);
* Comment 'ltc2688_reg_writable()' to account for the special condition;
* Kmemdup default channels so that it can be safely changed per probed
device;
* Replace extended info multiplexer functions by individual functions;
* Use raw0 ABI for toggle channels;
* Use dedicated offset ABI for dither channels;
* Misc changes (spell fixes, blank lines...);
* Have a clock property per channel. Note that we this I moved to OF
since we now have to use 'devm_get_clk_from_child()' which is using
device_node. Note that I could use 'to_of_node()' but mixing of.h and
property.h does not feel like a good idea.
ABI:
* Added out_voltageY_raw0 ABI for toggle mode;
* Added out_voltageY_dither_offset.
Bindings:
* Use standard microvolt unit;
* Added constrains for adi,output-range-microvolt and removed negative
values from the dts example;
* Moved clocks to the channel object;
* Dropped clock-names;
* Add a dependency between 'adi,toggle-dither-input' and 'clocks'.
[1]: https://marc.info/?l=linux-iio&m=163662843603265&w=2
Nuno Sá (3):
iio: dac: add support for ltc2688
iio: ABI: add ABI file for the LTC2688 DAC
dt-bindings: iio: Add ltc2688 documentation
.../ABI/testing/sysfs-bus-iio-dac-ltc2688 | 80 ++
.../bindings/iio/dac/adi,ltc2688.yaml | 147 +++
MAINTAINERS | 9 +
drivers/iio/dac/Kconfig | 11 +
drivers/iio/dac/Makefile | 1 +
drivers/iio/dac/ltc2688.c | 1070 +++++++++++++++++
6 files changed, 1318 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
create mode 100644 Documentation/devicetree/bindings/iio/dac/adi,ltc2688.yaml
create mode 100644 drivers/iio/dac/ltc2688.c
--
2.33.1
next reply other threads:[~2022-01-15 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 9:27 Nuno Sá [this message]
2022-01-15 9:27 ` [PATCH v2 1/3] iio: dac: add support for ltc2688 Nuno Sá
2022-01-15 14:01 ` kernel test robot
2022-01-15 18:15 ` kernel test robot
2022-01-16 12:44 ` Jonathan Cameron
2022-01-16 16:28 ` Sa, Nuno
2022-01-16 17:14 ` Jonathan Cameron
2022-01-15 9:27 ` [PATCH v2 2/3] iio: ABI: add ABI file for the LTC2688 DAC Nuno Sá
2022-01-16 12:20 ` Jonathan Cameron
2022-01-16 16:13 ` Sa, Nuno
2022-01-15 9:27 ` [PATCH v2 3/3] dt-bindings: iio: Add ltc2688 documentation Nuno Sá
2022-01-16 12:01 ` Jonathan Cameron
2022-01-16 16:18 ` Sa, Nuno
2022-01-16 17:34 ` [PATCH v2 0/3] Add support for LTC2688 Jonathan Cameron
2022-01-16 21:25 ` Andy Shevchenko
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=20220115092705.491-1-nuno.sa@analog.com \
--to=nuno.sa@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@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