Documentation/hwmon/hac300s.rst

Source file repositories/reference/linux-study-clean/Documentation/hwmon/hac300s.rst

File Facts

System: Linux kernel
Corpus path: Documentation/hwmon/hac300s.rst
Extension: .rst
Size: 939 bytes
Lines: 38
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

Kernel driver hac300s
=====================

Supported chips:

   * HiTRON HAC300S

     Prefix: 'hac300s'

     Datasheet: Publicly available at HiTRON website.

Author:

  - Vasileios Amoiridis <vasileios.amoiridis@cern.ch>

Description
-----------

This driver supports the HiTRON HAC300S PSU. It is a Universal AC input
harmonic correction AC-DC hot-swappable CompactPCI Serial Dual output
(with 5V standby) 312 Watts active current sharing switching power supply.

The device has an input of 90-264VAC and 2 nominal output voltaged at 12V and
5V which they can supplu up to 25A and 2.5A respectively.

Sysfs entries
-------------

======= ==========================================
curr1   Output current
in1     Output voltage
power1  Output power
temp1   Ambient temperature inside the module
temp2   Internal secondary component's temperature
======= ==========================================

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.