Documentation/hwmon/powerz.rst
Source file repositories/reference/linux-study-clean/Documentation/hwmon/powerz.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/hwmon/powerz.rst- Extension
.rst- Size
- 672 bytes
- Lines
- 31
- 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 POWERZ
====================
Supported chips:
* ChargerLAB POWER-Z KM003C
Prefix: 'powerz'
Addresses scanned: -
Author:
- Thomas Weißschuh <linux@weissschuh.net>
Description
-----------
This driver implements support for the ChargerLAB POWER-Z USB-C power testing
family.
The device communicates with the custom protocol over USB.
The channel labels exposed via hwmon match the labels used by the on-device
display and the official POWER-Z PC software.
As current can flow in both directions through the tester the sign of the
channel "curr1_input" (label "IBUS") indicates the direction.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.