include/linux/regulator/mt6359-regulator.h

File Facts

System

Linux kernel

Corpus path

include/linux/regulator/mt6359-regulator.h

Extension

.h

Size

1202 bytes

Lines

62

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

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

#ifndef __LINUX_REGULATOR_MT6359_H
#define __LINUX_REGULATOR_MT6359_H

enum {
	MT6359_ID_VS1 = 0,
	MT6359_ID_VGPU11,
	MT6359_ID_VMODEM,
	MT6359_ID_VPU,
	MT6359_ID_VCORE,
	MT6359_ID_VS2,
	MT6359_ID_VPA,
	MT6359_ID_VPROC2,
	MT6359_ID_VPROC1,
	MT6359_ID_VCORE_SSHUB,
	MT6359_ID_VGPU11_SSHUB = MT6359_ID_VCORE_SSHUB,
	MT6359_ID_VAUD18 = 10,
	MT6359_ID_VSIM1,
	MT6359_ID_VIBR,
	MT6359_ID_VRF12,
	MT6359_ID_VUSB,
	MT6359_ID_VSRAM_PROC2,
	MT6359_ID_VIO18,
	MT6359_ID_VCAMIO,
	MT6359_ID_VCN18,
	MT6359_ID_VFE28,
	MT6359_ID_VCN13,
	MT6359_ID_VCN33_1,
	MT6359_ID_VAUX18,
	MT6359_ID_VSRAM_OTHERS,
	MT6359_ID_VEFUSE,
	MT6359_ID_VXO22,
	MT6359_ID_VRFCK,
	MT6359_ID_VBIF28,
	MT6359_ID_VIO28,
	MT6359_ID_VEMC,
	MT6359_ID_VCN33_2,
	MT6359_ID_VA12,
	MT6359_ID_VA09,
	MT6359_ID_VRF18,
	MT6359_ID_VSRAM_MD,
	MT6359_ID_VUFS,
	MT6359_ID_VM18,
	MT6359_ID_VBBCK,
	MT6359_ID_VSRAM_PROC1,
	MT6359_ID_VSIM2,
	MT6359_ID_VSRAM_OTHERS_SSHUB,
	MT6359_ID_VCN33_1_BT,
	MT6359_ID_VCN33_1_WIFI,
	MT6359_ID_VCN33_2_BT,
	MT6359_ID_VCN33_2_WIFI,
	MT6359_ID_RG_MAX,
};

#define MT6359_MAX_REGULATOR	MT6359_ID_RG_MAX

#endif /* __LINUX_REGULATOR_MT6359_H */

Annotation

• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.

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.