Documentation/devicetree/bindings/iio/humidity/dht11.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/iio/humidity/dht11.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/iio/humidity/dht11.yaml- Extension
.yaml- Size
- 869 bytes
- Lines
- 42
- 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/humidity/dht11.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: DHT11 humidity + temperature sensor
maintainers:
- Harald Geyer <harald@ccbib.org>
description: |
A simple and low cost module providing a non standard single GPIO based
interface. It is believed the part is made by aosong but don't have
absolute confirmation of this, or what the aosong part number is.
properties:
compatible:
const: dht11
reg:
maxItems: 1
gpios:
maxItems: 1
description:
Single, interrupt capable, GPIO used to communicate with the device.
required:
- compatible
- gpios
additionalProperties: false
examples:
- |
humidity-sensor {
compatible = "dht11";
gpios = <&gpio0 6 0>;
};
...
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.