include/linux/regulator/mt6331-regulator.h

File Facts

System

Linux kernel

Corpus path

include/linux/regulator/mt6331-regulator.h

Extension

.h

Size

900 bytes

Lines

47

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_MT6331_H
#define __LINUX_REGULATOR_MT6331_H

enum {
	/* BUCK */
	MT6331_ID_VDVFS11 = 0,
	MT6331_ID_VDVFS12,
	MT6331_ID_VDVFS13,
	MT6331_ID_VDVFS14,
	MT6331_ID_VCORE2,
	MT6331_ID_VIO18,
	/* LDO */
	MT6331_ID_VTCXO1,
	MT6331_ID_VTCXO2,
	MT6331_ID_AVDD32_AUD,
	MT6331_ID_VAUXA32,
	MT6331_ID_VCAMA,
	MT6331_ID_VIO28,
	MT6331_ID_VCAM_AF,
	MT6331_ID_VMC,
	MT6331_ID_VMCH,
	MT6331_ID_VEMC33,
	MT6331_ID_VGP1,
	MT6331_ID_VSIM1,
	MT6331_ID_VSIM2,
	MT6331_ID_VMIPI,
	MT6331_ID_VIBR,
	MT6331_ID_VGP4,
	MT6331_ID_VCAMD,
	MT6331_ID_VUSB10,
	MT6331_ID_VCAM_IO,
	MT6331_ID_VSRAM_DVFS1,
	MT6331_ID_VGP2,
	MT6331_ID_VGP3,
	MT6331_ID_VRTC,
	MT6331_ID_VDIG18,
	MT6331_ID_VREG_MAX
};

#endif /* __LINUX_REGULATOR_MT6331_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.