Documentation/hwmon/htu31.rst
Source file repositories/reference/linux-study-clean/Documentation/hwmon/htu31.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/hwmon/htu31.rst- Extension
.rst- Size
- 994 bytes
- Lines
- 45
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- 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-later
Kernel driver HTU31
====================
Supported chips:
* Measurement Specialties HTU31
Prefix: 'htu31'
Addresses scanned: -
Datasheet: Publicly available from https://www.te.com/en/product-CAT-HSC0007.html
Author:
- Andrei Lalaev <andrey.lalaev@gmail.com>
Description
-----------
HTU31 is a humidity and temperature sensor.
Supported temperature range is from -40 to 125 degrees Celsius.
Communication with the device is performed via I2C protocol. Sensor's default address
is 0x40.
sysfs-Interface
---------------
=================== =================
temp1_input: temperature input
humidity1_input: humidity input
heater_enable: heater control
=================== =================
debugfs-Interface
-----------------
=================== =========================================
serial_number: unique serial number of the sensor
=================== =========================================
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.