arch/arm/mach-sa1100/generic.h

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-sa1100/generic.h

Extension

.h

Size

1530 bytes

Lines

56

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/cpufreq.h
• linux/reboot.h

Detected Declarations

• struct flash_platform_data
• struct resource
• struct mcp_plat_data
• struct sa1100fb_mach_info
• struct gpiod_lookup_table
• struct fixed_voltage_config
• struct regulator_consumer_supply
• function sa11x0_pm_init

Annotated Snippet

static inline int sa11x0_pm_init(void) { return 0; }
#endif

int sa11xx_clk_init(void);

struct gpiod_lookup_table;
void sa11x0_register_pcmcia(int socket, struct gpiod_lookup_table *);

struct fixed_voltage_config;
struct regulator_consumer_supply;
int sa11x0_register_fixed_regulator(int n, struct fixed_voltage_config *cfg,
	struct regulator_consumer_supply *supplies, unsigned num_supplies,
	bool uses_gpio);

Annotation

• Immediate include surface: `linux/cpufreq.h`, `linux/reboot.h`.
• Detected declarations: `struct flash_platform_data`, `struct resource`, `struct mcp_plat_data`, `struct sa1100fb_mach_info`, `struct gpiod_lookup_table`, `struct fixed_voltage_config`, `struct regulator_consumer_supply`, `function sa11x0_pm_init`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.