From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>
Subject: Re: [PATCH v2 2/3] iio: ABI: add ABI file for the LTC2688 DAC
Date: Sun, 16 Jan 2022 12:20:34 +0000 [thread overview]
Message-ID: <20220116122034.7db81c50@jic23-huawei> (raw)
In-Reply-To: <20220115092705.491-3-nuno.sa@analog.com>
On Sat, 15 Jan 2022 10:27:04 +0100
Nuno Sá <nuno.sa@analog.com> wrote:
> Define the sysfs interface for toggle or dither capable channels. Dither
> capable channels will have the extended interface:
>
> * out_voltageY_dither_en
> * out_voltageY_dither_raw
> * out_voltageY_dither_offset
> * out_voltageY_dither_raw_available
> * out_voltageY_dither_frequency
> * out_voltageY_dither_frequency_available
> * out_voltageY_dither_phase
> * out_voltageY_dither_phase_available
>
> Toggle enabled channels will have:
>
> * out_voltageY_toggle_en
> * out_voltageY_raw0
> * out_voltageY_raw1
> * out_voltageY_symbol
Maybe worth just stating the normal interface here as well because
it's not clear from these examples if
out_voltageY_raw still exists for toggle enabled channels (I'm assuming not?)
>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
ABI seems good to me, just a few comments on details of the documentation.
Thanks,
Jonathan
> ---
> .../ABI/testing/sysfs-bus-iio-dac-ltc2688 | 80 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 81 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688 b/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
> new file mode 100644
> index 000000000000..38d1df81c6dc
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
> @@ -0,0 +1,80 @@
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_en
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Dither enable. Write 1 to enable dither or 0 to disable it.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_raw
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + This raw, unscaled value refers to the dither signal amplitude.
> + The same scale as in out_voltageY_raw applies. However, the
> + offset might be different as it's always 0 for this attribute.
We'll have to be careful if we ever generalize these docs but what you have here
is fine whilst it applies to just this device.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_raw_available
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Available range for dither raw amplitude values.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_offset
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Offset applied to out_voltageY_dither_raw. Read only attribute
> + always set to 0.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_frequency
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Sets the dither signal frequency.
Units.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_frequency_available
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Returns the available values for the dither frequency.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_phase
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Sets the dither signal phase.
Units. Radians, or refer to the main _phase docs and say it's the same.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_dither_phase_available
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Returns the available values for the dither phase.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_toggle_en
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Toggle enable. Write 1 to enable toggle or 0 to disable it.
Say why this is useful (presumably toggle with a clock rather than via _symbol)
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw0
> +KernelVersion: 5.17
> +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. The same scale, offset, etc applies.
Same as what?
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_raw1
> +KernelVersion: 5.17
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Same as out_voltageY_raw0 but referring to the DAC output code
> + in INPUT_B.
You could combine this with previous and have two what lines. Might allow
a slightly more compact clear description.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_symbol
Ah. That answers one of my binding related questions :) You have kept
software control as an option for toggle.
> +KernelVersion: 5.17
> +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_raw
_raw0
> + and out_voltageY_raw1 through software. Writing 0 will select
> + out_voltageY_raw while 1 selects out_voltageY_raw1.
_raw0
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 16e344d52b1e..16a7fd7f98ee 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11187,6 +11187,7 @@ M: Nuno Sá <nuno.sa@analog.com>
> L: linux-iio@vger.kernel.org
> S: Supported
> W: http://ez.analog.com/community/linux-device-drivers
> +F: Documentation/ABI/testing/sysfs-bus-iio-dac-ltc2688
> F: drivers/iio/dac/ltc2688.c
>
> LTC2947 HARDWARE MONITOR DRIVER
next prev parent reply other threads:[~2022-01-16 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 9:27 [PATCH v2 0/3] Add support for LTC2688 Nuno Sá
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 [this message]
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=20220116122034.7db81c50@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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