Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/iio/dac/adi,ad7303.yaml- Extension
.yaml- Size
- 979 bytes
- Lines
- 51
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
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
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/iio/dac/adi,ad7303.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Analog Devices AD7303 DAC
maintainers:
- Lars-Peter Clausen <lars@metafoo.de>
properties:
compatible:
const: adi,ad7303
reg:
maxItems: 1
Vdd-supply:
description:
Used to calculate output channel scalling if REF-supply not specified.
REF-supply:
description:
If not provided, Vdd/2 is used as the reference voltage.
spi-max-frequency:
maximum: 30000000
required:
- compatible
- reg
- Vdd-supply
additionalProperties: false
examples:
- |
spi {
#address-cells = <1>;
#size-cells = <0>;
dac@4 {
compatible = "adi,ad7303";
reg = <4>;
spi-max-frequency = <10000000>;
Vdd-supply = <&vdd_supply>;
REF-supply = <&vref_supply>;
};
};
...
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- 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.