From: Tomas Borquez <tomasborquez13@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>
Cc: "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,
"Tomas Borquez" <tomasborquez13@gmail.com>
Subject: [PATCH 5/5] staging: iio: ad9832: add sysfs documentation
Date: Mon, 15 Dec 2025 16:08:06 -0300 [thread overview]
Message-ID: <20251215190806.11003-6-tomasborquez13@gmail.com> (raw)
In-Reply-To: <20251215190806.11003-1-tomasborquez13@gmail.com>
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>
---
.../Documentation/sysfs-bus-iio-dds-ad9832 | 41 +++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 drivers/staging/iio/Documentation/sysfs-bus-iio-dds-ad9832
diff --git a/drivers/staging/iio/Documentation/sysfs-bus-iio-dds-ad9832 b/drivers/staging/iio/Documentation/sysfs-bus-iio-dds-ad9832
new file mode 100644
index 0000000000..5ceea57917
--- /dev/null
+++ b/drivers/staging/iio/Documentation/sysfs-bus-iio-dds-ad9832
@@ -0,0 +1,41 @@
+What: /sys/bus/iio/devices/iio:deviceX/out_altcurrent0_frequencyY
+KernelVersion: 6.19
+Contact: linux-iio@vger.kernel.org
+Description:
+ Frequency in Hz for frequency register Y (0-1). The active
+ frequency register is selected via out_altcurrent0_frequency_symbol.
+
+What: /sys/bus/iio/devices/iio:deviceX/out_altcurrent0_phaseY
+KernelVersion: 6.19
+Contact: linux-iio@vger.kernel.org
+Description:
+ Phase offset in radians for phase register Y (0-3). Valid
+ range is 0 to 2*PI (exclusive) with 12-bit hardware resolution. The
+ active phase register is selected via out_altcurrent0_phase_symbol.
+
+What: /sys/bus/iio/devices/iio:deviceX/out_altcurrent0_frequency_symbol
+KernelVersion: 6.19
+Contact: linux-iio@vger.kernel.org
+Description:
+ Selects which frequency register (0 or 1) is active for output.
+
+What: /sys/bus/iio/devices/iio:deviceX/out_altcurrent0_phase_symbol
+KernelVersion: 6.19
+Contact: linux-iio@vger.kernel.org
+Description:
+ Selects which phase register (0-3) is active for output.
+
+What: /sys/bus/iio/devices/iio:deviceX/out_altcurrent0_enable
+KernelVersion: 6.19
+Contact: linux-iio@vger.kernel.org
+Description:
+ Enables (1) or disables (0) the output. When disabled, the
+ device is held in reset state.
+
+What: /sys/bus/iio/devices/iio:deviceX/out_altcurrent0_pincontrol_en
+KernelVersion: 6.19
+Contact: linux-iio@vger.kernel.org
+Description:
+ Enables (1) or disables (0) hardware pin control for frequency
+ and phase selection. When enabled, external pins control
+ register selection instead of software.
--
2.43.0
next prev parent reply other threads:[~2025-12-15 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 19:08 [PATCH 0/5] staging: ad9832: driver cleanup Tomas Borquez
2025-12-15 19:08 ` [PATCH 1/5] staging: iio: ad9832: clean up whitespace Tomas Borquez
2025-12-18 14:27 ` Marcelo Schmitt
2025-12-21 19:17 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 2/5] staging: iio: ad9832: convert to guard(mutex) Tomas Borquez
2025-12-18 14:34 ` Marcelo Schmitt
2025-12-18 15:16 ` Tomas Borquez
2025-12-21 19:22 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 3/5] staging: iio: ad9832: cleanup dev_err_probe() Tomas Borquez
2025-12-18 14:38 ` Marcelo Schmitt
2025-12-21 19:25 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 4/5] staging: iio: ad9832: convert to iio channels and ext_info attrs Tomas Borquez
2025-12-18 15:04 ` Marcelo Schmitt
2025-12-18 15:46 ` Tomas Borquez
2025-12-21 19:36 ` Jonathan Cameron
2025-12-15 19:08 ` Tomas Borquez [this message]
2025-12-18 15:10 ` [PATCH 5/5] staging: iio: ad9832: add sysfs documentation Marcelo Schmitt
2025-12-21 19:43 ` 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=20251215190806.11003-6-tomasborquez13@gmail.com \
--to=tomasborquez13@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.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 \
/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