Documentation/hwmon/mc34vr500.rst
Source file repositories/reference/linux-study-clean/Documentation/hwmon/mc34vr500.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/hwmon/mc34vr500.rst- Extension
.rst- Size
- 939 bytes
- Lines
- 33
- 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 mc34vr500
=======================
Supported Chips:
* NXP MC34VR500
Prefix: 'mc34vr500'
Datasheet: https://www.nxp.com/docs/en/data-sheet/MC34VR500.pdf
Author: Mario Kicherer <dev@kicherer.org>
Description
-----------
This driver implements initial support for the NXP MC34VR500 PMIC. The MC34VR500
monitors the temperature, input voltage and output currents and provides
corresponding alarms. For the temperature, the chip can send interrupts if
the temperature rises above one of the following values: 110°, 120°, 125° and
130° Celsius. For the input voltage, an interrupt is sent when the voltage
drops below 2.8V.
Currently, this driver only implements the input voltage and temperature
alarms. The interrupts are mapped as follows:
<= 2.8V -> in0_min_alarm
>110°c -> temp1_max_alarm
>120°c -> temp1_crit_alarm
>130°c -> temp1_emergency_alarmAnnotation
- 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.