From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Kim Seer Paller <kimseer.paller@analog.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <noname.nuno@gmail.com>
Subject: Re: [PATCH v2 1/5] iio: ABI: Generalize ABI documentation for DAC
Date: Thu, 23 May 2024 17:52:33 +0100 [thread overview]
Message-ID: <20240523175233.00006e8b@Huawei.com> (raw)
In-Reply-To: <20240523031909.19427-2-kimseer.paller@analog.com>
On Thu, 23 May 2024 11:19:05 +0800
Kim Seer Paller <kimseer.paller@analog.com> wrote:
> Introduces a more generalized ABI documentation for DAC. Instead of
> having separate ABI files for each DAC, we now have a single ABI file
> that covers the common sysfs interface for all DAC.
>
> Co-developed-by: Michael Hennerich <michael.hennerich@analog.com>
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> Signed-off-by: Kim Seer Paller <kimseer.paller@analog.com>
> ---
> Documentation/ABI/testing/sysfs-bus-iio-dac | 61 +++++++++++++++++++
> .../ABI/testing/sysfs-bus-iio-dac-ltc2688 | 31 ----------
> MAINTAINERS | 8 +++
> 3 files changed, 69 insertions(+), 31 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac b/Documentation/ABI/testing/sysfs-bus-iio-dac
> new file mode 100644
> index 000000000000..53d5213520c6
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac
> @@ -0,0 +1,61 @@
> +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_toggle_en
> +KernelVersion: 5.18
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Toggle enable. Write 1 to enable toggle or 0 to disable it. This is
> + useful when one wants to change the DAC output codes. The way it should
> + be done is:
> +
> + - disable toggle operation;
> + - change out_currentY_raw0 and out_currentY_raw1;
Generalize to [0...N] or something like that to allow more symbols.
> + - enable toggle operation.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw0
> +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_raw1
> +KernelVersion: 5.18
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + It has the same meaning as out_currentY_raw. This attribute is
> + specific to toggle enabled channels and refers to the DAC output
> + code in INPUT_A (_raw0) and INPUT_B (_raw1). The same scale and offset
> + as in out_currentY_raw applies.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_currentY_symbol
> +KernelVersion: 5.18
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Performs a SW toggle. This attribute is specific to toggle
> + enabled channels and allows to toggle between out_currentY_raw0
> + and out_currentY_raw1 through software. Writing 0 will select
> + out_currentY_raw0 while 1 selects out_currentY_raw1.
Perhaps write this more generally. The ABI handles more than 2 symbol values.
Performs a SW switch to a predefined output symbol, allowing
switching between current symbol A with output
out_currentY_rawA and new symbol B with output
out_currentY_rawB by writing integer value B.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_toggle_en
> +KernelVersion: 5.18
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Toggle enable. Write 1 to enable toggle or 0 to disable it. This is
> + useful when one wants to change the DAC output codes. The way it should
> + be done is:
> +
> + - disable toggle operation;
> + - change out_voltageY_raw0 and out_voltageY_raw1;
> + - enable toggle operation.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw0
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw1
> +KernelVersion: 5.18
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + It has the same meaning as out_voltageY_raw. This attribute is
> + specific to toggle enabled channels and refers to the DAC output
> + code in INPUT_A (_raw0) and INPUT_B (_raw1). The same scale and offset
> + as in out_voltageY_raw applies.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_symbol
> +KernelVersion: 5.18
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Performs a SW toggle. This attribute is specific to toggle
> + enabled channels and allows to toggle between out_voltageY_raw0
> + and out_voltageY_raw1 through software. Writing 0 will select
> + out_voltageY_raw0 while 1 selects out_voltageY_raw1.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 758c202ec712..b3be54c09159 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -12850,6 +12850,14 @@ S: Maintained
> F: Documentation/devicetree/bindings/iio/dac/lltc,ltc1660.yaml
> F: drivers/iio/dac/ltc1660.c
>
> +LTC2664 IIO DAC DRIVER
> +M: Michael Hennerich <michael.hennerich@analog.com>
> +M: Kim Seer Paller <kimseer.paller@analog.com>
> +L: linux-iio@vger.kernel.org
> +S: Supported
> +W: https://ez.analog.com/linux-software-drivers
> +F: Documentation/ABI/testing/sysfs-bus-iio-dac
As it's a general doc, doesn't really belong in a driver specific entry.
So far we haven't listed these generic docs as having specific maintainers
and people have to rely on history to figure out who to cc.
> +
> LTC2688 IIO DAC DRIVER
> M: Nuno Sá <nuno.sa@analog.com>
> L: linux-iio@vger.kernel.org
next prev parent reply other threads:[~2024-05-23 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 3:19 [PATCH v2 0/5] Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-05-23 3:19 ` [PATCH v2 1/5] iio: ABI: Generalize ABI documentation for DAC Kim Seer Paller
2024-05-23 16:52 ` Jonathan Cameron [this message]
2024-05-23 3:19 ` [PATCH v2 2/5] iio: ABI: add DAC 42kohm_to_gnd powerdown mode Kim Seer Paller
2024-06-03 18:46 ` David Lechner
2024-05-23 3:19 ` [PATCH v2 3/5] dt-bindings: iio: dac: Add adi,ltc2664.yaml Kim Seer Paller
2024-05-23 6:39 ` Krzysztof Kozlowski
2024-05-24 6:28 ` Paller, Kim Seer
2024-05-25 16:49 ` Krzysztof Kozlowski
2024-05-25 17:17 ` Jonathan Cameron
2024-05-23 3:19 ` [PATCH v2 4/5] dt-bindings: iio: dac: Add adi,ltc2672.yaml Kim Seer Paller
2024-05-23 4:24 ` Rob Herring (Arm)
2024-05-23 12:33 ` Rob Herring
2024-05-23 3:19 ` [PATCH v2 5/5] iio: dac: ltc2664: Add driver for LTC2664 and LTC2672 Kim Seer Paller
2024-05-23 17:02 ` Jonathan Cameron
2024-05-28 5:53 ` Paller, Kim Seer
2024-06-02 13:13 ` Jonathan Cameron
2024-05-24 3:28 ` kernel test robot
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=20240523175233.00006e8b@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=kimseer.paller@analog.com \
--cc=krzk+dt@kernel.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=noname.nuno@gmail.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