include/linux/ssbi.h
Source file repositories/reference/linux-study-clean/include/linux/ssbi.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/ssbi.h- Extension
.h- Size
- 726 bytes
- Lines
- 36
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.h
Detected Declarations
function ssbi_reg_readfunction ssbi_reg_write
Annotated Snippet
#ifndef _LINUX_SSBI_H
#define _LINUX_SSBI_H
#include <linux/types.h>
int ssbi_write(struct device *dev, u16 addr, const u8 *buf, int len);
int ssbi_read(struct device *dev, u16 addr, u8 *buf, int len);
static inline int
ssbi_reg_read(void *context, unsigned int reg, unsigned int *val)
{
int ret;
u8 v;
ret = ssbi_read(context, reg, &v, 1);
if (!ret)
*val = v;
return ret;
}
static inline int
ssbi_reg_write(void *context, unsigned int reg, unsigned int val)
{
u8 v = val;
return ssbi_write(context, reg, &v, 1);
}
#endif
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `function ssbi_reg_read`, `function ssbi_reg_write`.
- 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.