From: Jonathan Cameron <jic23@kernel.org>
To: Tomas Borquez <tomasborquez13@gmail.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v2 6/6] staging: iio: ad9832: add sysfs documentation
Date: Wed, 31 Dec 2025 18:35:02 +0000 [thread overview]
Message-ID: <20251231183502.26182f0c@jic23-huawei> (raw)
In-Reply-To: <20251230203459.28935-7-tomasborquez13@gmail.com>
On Tue, 30 Dec 2025 17:34:59 -0300
Tomas Borquez <tomasborquez13@gmail.com> wrote:
> Add sysfs ABI documentation for the AD9832/AD9835 Direct Digital
> Synthesizer chips, documenting frequency, phase, output control,
> and pin control attributes.
>
> Signed-off-by: Tomas Borquez <tomasborquez13@gmail.com>
Hi Tomas,
Good docs, one entry of which reminded me we tend to use powerdown for
output devices rather than _en (for enable)
Jonathan
> ---
> .../iio/Documentation/sysfs-bus-iio-frequency | 40 +++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 drivers/staging/iio/Documentation/sysfs-bus-iio-frequency
>
> diff --git a/drivers/staging/iio/Documentation/sysfs-bus-iio-frequency b/drivers/staging/iio/Documentation/sysfs-bus-iio-frequency
> new file mode 100644
> index 000000000000..10627c19bdb7
> --- /dev/null
> +++ b/drivers/staging/iio/Documentation/sysfs-bus-iio-frequency
> @@ -0,0 +1,40 @@
> +What: /sys/bus/iio/devices/iio:deviceX/out_altcurrentY_frequencyZ
> +KernelVersion: 6.19
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Frequency in Hz for symbol Z of channel Y. The active
> + frequency symbol is selected via out_altcurrentY_frequency_symbol.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_altcurrentY_phaseZ
> +KernelVersion: 6.19
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Phase offset in radians for symbol Z of channel Y. Valid range
> + is 0 to 2*PI (exclusive). The active phase symbol is selected
> + via out_altcurrentY_phase_symbol.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_altcurrentY_frequency_symbol
> +KernelVersion: 6.19
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Selects which frequency symbol is active for channel Y.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_altcurrentY_phase_symbol
> +KernelVersion: 6.19
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Selects which phase symbol is active for channel Y.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_altcurrentY_enable
Ah. I probably led you astray on this in an earlier review. Would be _en
and added to the standard docs in sysfs-bus-iio in the block that starts with in_energyY_en
However, I think that might not be the right attribute to use based on this
being more similar to a DAC channel than those which are about enabling internal
accumulators. For a DAC the common terminology is about powerdown (so effectively !enable).
That lines up with the use of SLEEP here on the datasheet.
So I think this should be out_altcurrentY_powerdown and documented in the block
with out_altvoltageY_powerdown in sysfs-bus-iio with a tweak to make the descriptive
text cover currents as well as voltages.
Obviously remember to flip the sense of the control though.
> +KernelVersion: 6.19
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Enables (1) or disables (0) the output for channel Y.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_altcurrentY_pincontrol_en
> +KernelVersion: 6.19
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Enables (1) or disables (0) hardware pin control for frequency
> + and phase symbol selection on channel Y. When enabled, external
> + pins control symbol selection instead of software.
prev parent reply other threads:[~2025-12-31 18:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 20:34 [PATCH v2 0/6] staging: ad9832: driver cleanup Tomas Borquez
2025-12-30 20:34 ` [PATCH v2 1/6] staging: iio: ad9832: cleanup dev_err_probe() Tomas Borquez
2025-12-30 22:47 ` Andy Shevchenko
2025-12-31 18:02 ` Jonathan Cameron
2025-12-30 20:34 ` [PATCH v2 2/6] staging: iio: ad9832: convert to guard(mutex) Tomas Borquez
2025-12-30 22:50 ` Andy Shevchenko
2025-12-31 17:01 ` Tomas Borquez
2025-12-30 20:34 ` [PATCH v2 3/6] staging: iio: ad9832: convert to devm_mutex_init() Tomas Borquez
2026-01-14 1:34 ` Marcelo Schmitt
2025-12-30 20:34 ` [PATCH v2 4/6] staging: iio: ad9832: remove dds.h dependency Tomas Borquez
2025-12-30 22:46 ` Andy Shevchenko
2026-01-04 5:25 ` Tomas Borquez
2026-01-05 15:52 ` Andy Shevchenko
2025-12-31 18:09 ` Jonathan Cameron
2025-12-31 18:11 ` Jonathan Cameron
2026-01-04 5:38 ` Tomas Borquez
2026-01-11 12:13 ` Jonathan Cameron
2025-12-30 20:34 ` [PATCH v2 5/6] staging: iio: ad9832: convert to iio channels and ext_info attrs Tomas Borquez
2025-12-30 22:55 ` Andy Shevchenko
2025-12-31 17:08 ` Tomas Borquez
2026-01-11 12:20 ` Jonathan Cameron
2025-12-31 18:21 ` Jonathan Cameron
2025-12-30 20:34 ` [PATCH v2 6/6] staging: iio: ad9832: add sysfs documentation Tomas Borquez
2025-12-30 22:57 ` Andy Shevchenko
2025-12-31 18:35 ` Jonathan Cameron [this message]
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=20251231183502.26182f0c@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.com \
--cc=tomasborquez13@gmail.com \
/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