Documentation/hwmon/tc654.rst

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

File Facts

System: Linux kernel
Corpus path: Documentation/hwmon/tc654.rst
Extension: .rst
Size: 1047 bytes
Lines: 35
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

Kernel driver tc654
===================

Supported chips:

  * Microchip TC654 and TC655

    Prefix: 'tc654'
    Datasheet: http://ww1.m
    icrochip.com/downloads/en/DeviceDoc/20001734C.pdf

Authors:
      - Chris Packham <chris.packham@alliedtelesis.co.nz>
      - Masahiko Iwamoto <iwamoto@allied-telesis.co.jp>

Description
-----------
This driver implements support for the Microchip TC654 and TC655.

The TC654 uses the 2-wire interface compatible with the SMBUS 2.0
specification. The TC654 has two (2) inputs for measuring fan RPM and
one (1) PWM output which can be used for fan control.

Configuration Notes
-------------------
Ordinarily the pwm1_mode ABI is used for controlling the pwm output
mode.  However, for this chip the output is always pwm, and the
pwm1_mode determines if the pwm output is controlled via the pwm1 value
or via the Vin analog input.


Setting pwm1_mode to 1 will cause the pwm output to be driven based on
the pwm1 value. Setting pwm1_mode to 0 will cause the pwm output to be
driven based on the Vin input.

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.