Documentation/devicetree/bindings/iio/amplifiers/adi,ada4250.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/iio/amplifiers/adi,ada4250.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/iio/amplifiers/adi,ada4250.yaml- Extension
.yaml- Size
- 976 bytes
- Lines
- 52
- 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-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/iio/amplifiers/adi,ada4250.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: ADA4250 Programmable Gain Instrumentation Amplifier
maintainers:
- Antoniu Miclaus <antoniu.miclaus@analog.com>
description: |
Precision Low Power, 110kHz, 26uA, Programmable Gain Instrumentation Amplifier.
properties:
compatible:
enum:
- adi,ada4250
reg:
maxItems: 1
avdd-supply: true
adi,refbuf-enable:
description:
Enable internal buffer to drive the reference pin.
type: boolean
required:
- compatible
- reg
- avdd-supply
allOf:
- $ref: /schemas/spi/spi-peripheral-props.yaml#
unevaluatedProperties: false
examples:
- |
spi {
#address-cells = <1>;
#size-cells = <0>;
amplifier@0 {
compatible = "adi,ada4250";
reg = <0>;
avdd-supply = <&avdd>;
};
};
...
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.