Documentation/ABI/testing/sysfs-class-power-rt9467

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-class-power-rt9467

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-class-power-rt9467
Extension: [no extension]
Size: 727 bytes
Lines: 20
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

What:		/sys/class/power_supply/rt9467-*/sysoff_enable
Date:		Feb 2023
KernelVersion:	6.3
Contact:	ChiaEn Wu <chiaen_wu@richtek.com>
Description:
		This entry allows enabling the sysoff mode of rt9467 charger
		devices.
		If enabled and the input is removed, the internal battery FET
		is turned off to reduce the leakage from the BAT pin. See
		device datasheet for details. It's commonly used when the
		product enter shipping stage. After entering shipping mode,
		only 'VBUS' or 'Power key" pressed can make it leave this mode.
		'Disable' also can help to leave it, but it's more like to
		abort the action before the device really enter shipping mode.

		Access: Read, Write
		Valid values:
		- 1: enabled
		- 0: disabled

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.