drivers/staging/iio/Documentation/sysfs-bus-iio-dds
Source file repositories/reference/linux-study-clean/drivers/staging/iio/Documentation/sysfs-bus-iio-dds
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/iio/Documentation/sysfs-bus-iio-dds- Extension
[no extension]- Size
- 3761 bytes
- Lines
- 97
- Domain
- Driver Families
- Bucket
- drivers/staging
- Inferred role
- Driver Families: drivers/staging
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
What: /sys/bus/iio/devices/.../out_altvoltageX_frequencyY
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Stores frequency into tuning word Y.
There will be more than one out_altvoltageX_frequencyY file,
which allows for pin controlled FSK Frequency Shift Keying
(out_altvoltageX_pincontrol_frequency_en is active) or the user
can control the desired active tuning word by writing Y to the
out_altvoltageX_frequencysymbol file.
What: /sys/bus/iio/devices/.../out_altvoltageX_frequencyY_scale
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Scale to be applied to out_altvoltageX_frequencyY in order to
obtain the desired value in Hz. If shared across all frequency
registers Y is not present. It is also possible X is not present
if shared across all channels.
What: /sys/bus/iio/devices/.../out_altvoltageX_frequencysymbol
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Specifies the active output frequency tuning word. The value
corresponds to the Y in out_altvoltageX_frequencyY.
To exit this mode the user can write
out_altvoltageX_pincontrol_frequency_en or
out_altvoltageX_out_enable file.
What: /sys/bus/iio/devices/.../out_altvoltageX_phaseY
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Stores phase into Y.
There will be more than one out_altvoltageX_phaseY file, which
allows for pin controlled PSK Phase Shift Keying
(out_altvoltageX_pincontrol_phase_en is active) or the user can
control the desired phase Y which is added to the phase
accumulator output by writing Y to the phase_en file.
What: /sys/bus/iio/devices/.../out_altvoltageX_phaseY_scale
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Scale to be applied to out_altvoltageX_phaseY in order to obtain
the desired value in rad. If shared across all phase registers
Y is not present. It is also possible X is not present if
shared across all channels.
What: /sys/bus/iio/devices/.../out_altvoltageX_phasesymbol
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
Specifies the active phase Y which is added to the phase
accumulator output. The value corresponds to the Y in
out_altvoltageX_phaseY. To exit this mode the user can write
out_altvoltageX_pincontrol_phase_en or disable file.
What: /sys/bus/iio/devices/.../out_altvoltageX_pincontrol_en
What: /sys/bus/iio/devices/.../out_altvoltageX_pincontrol_frequency_en
What: /sys/bus/iio/devices/.../out_altvoltageX_pincontrol_phase_en
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
Description:
out_altvoltageX_pincontrol_en: Both, the active frequency and
phase is controlled by the respective phase and frequency
control inputs. In case the device in features independent
controls, then there are dedicated files
(out_altvoltageX_pincontrol_frequency_en,
Annotation
- Atlas domain: Driver Families / drivers/staging.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.