include/linux/regulator/mt6315-regulator.h

File Facts

System

Linux kernel

Corpus path

include/linux/regulator/mt6315-regulator.h

Extension

.h

Size

1102 bytes

Lines

45

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_MT6315_H
#define __LINUX_REGULATOR_MT6315_H

#define MT6315_RP	3
#define MT6315_PP	6
#define MT6315_SP	7

enum {
	MT6315_VBUCK1 = 0,
	MT6315_VBUCK2,
	MT6315_VBUCK3,
	MT6315_VBUCK4,
	MT6315_VBUCK_MAX,
};

/* Register */
#define MT6315_TOP2_ELR7			0x139
#define MT6315_TOP_TMA_KEY			0x39F
#define MT6315_TOP_TMA_KEY_H			0x3A0
#define MT6315_BUCK_TOP_CON0			0x1440
#define MT6315_BUCK_TOP_CON1			0x1443
#define MT6315_BUCK_TOP_ELR0			0x1449
#define MT6315_BUCK_TOP_ELR2			0x144B
#define MT6315_BUCK_TOP_ELR4			0x144D
#define MT6315_BUCK_TOP_ELR6			0x144F
#define MT6315_VBUCK1_DBG0			0x1499
#define MT6315_VBUCK1_DBG4			0x149D
#define MT6315_VBUCK2_DBG0			0x1519
#define MT6315_VBUCK2_DBG4			0x151D
#define MT6315_VBUCK3_DBG0			0x1599
#define MT6315_VBUCK3_DBG4			0x159D
#define MT6315_VBUCK4_DBG0			0x1619
#define MT6315_VBUCK4_DBG4			0x161D
#define MT6315_BUCK_TOP_4PHASE_ANA_CON42	0x16B1

#define PROTECTION_KEY_H			0x9C
#define PROTECTION_KEY				0xEA

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