include/linux/mtd/spear_smi.h
Source file repositories/reference/linux-study-clean/include/linux/mtd/spear_smi.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mtd/spear_smi.h- Extension
.h- Size
- 1793 bytes
- Lines
- 67
- 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.hlinux/mtd/mtd.hlinux/mtd/partitions.hlinux/platform_device.hlinux/of.h
Detected Declarations
struct spear_smi_flash_infostruct spear_smi_plat_data
Annotated Snippet
struct spear_smi_flash_info {
char *name;
unsigned long mem_base;
unsigned long size;
struct mtd_partition *partitions;
int nr_partitions;
u8 fast_mode;
};
/**
* struct spear_smi_plat_data - platform structure for configuring smi
*
* @clk_rate: clk rate at which SMI must operate
* @num_flashes: number of flashes present on board
* @board_flash_info: specific details of each flash present on board
* @np: array of DT node pointers for all possible flash chip devices
*/
struct spear_smi_plat_data {
unsigned long clk_rate;
int num_flashes;
struct spear_smi_flash_info *board_flash_info;
struct device_node *np[MAX_NUM_FLASH_CHIP];
};
#endif /* __MTD_SPEAR_SMI_H */
Annotation
- Immediate include surface: `linux/types.h`, `linux/mtd/mtd.h`, `linux/mtd/partitions.h`, `linux/platform_device.h`, `linux/of.h`.
- Detected declarations: `struct spear_smi_flash_info`, `struct spear_smi_plat_data`.
- 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.