include/linux/soc/apple/tunable.h
Source file repositories/reference/linux-study-clean/include/linux/soc/apple/tunable.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/soc/apple/tunable.h- Extension
.h- Size
- 2009 bytes
- Lines
- 63
- 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.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/device.hlinux/types.h
Detected Declarations
struct apple_tunable
Annotated Snippet
struct apple_tunable {
size_t sz;
struct {
u32 offset;
u32 mask;
u32 value;
} values[] __counted_by(sz);
};
/**
* Parse an array of hardware tunables from the device tree.
*
* @dev: Device node used for devm_kzalloc internally.
* @np: Device node which contains the tunable array.
* @name: Name of the device tree property which contains the tunables.
* @res: Resource to which the tunables will be applied, used for bound checking
*
* @return: devres allocated struct on success or PTR_ERR on failure.
*/
struct apple_tunable *devm_apple_tunable_parse(struct device *dev,
struct device_node *np,
const char *name,
struct resource *res);
/**
* Apply a previously loaded hardware tunable.
*
* @param regs: MMIO to which the tunable will be applied.
* @param tunable: Pointer to the tunable.
*/
void apple_tunable_apply(void __iomem *regs, struct apple_tunable *tunable);
#endif
Annotation
- Immediate include surface: `linux/device.h`, `linux/types.h`.
- Detected declarations: `struct apple_tunable`.
- 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.