arch/powerpc/sysdev/fsl_soc.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/sysdev/fsl_soc.h

Extension

.h

Size

1265 bytes

Lines

49

Domain

Architecture Layer

Bucket

arch/powerpc

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

• asm/mmu.h

Detected Declarations

• struct spi_device
• struct spi_board_info
• struct device_node
• struct platform_diu_data_ops
• enum fsl_diu_monitor_port
• function get_brgfreq
• function get_baudrate

Annotated Snippet

struct platform_diu_data_ops {
	u32 (*get_pixel_format)(enum fsl_diu_monitor_port port,
		unsigned int bpp);
	void (*set_gamma_table)(enum fsl_diu_monitor_port port,
		char *gamma_table_base);
	void (*set_monitor_port)(enum fsl_diu_monitor_port port);
	void (*set_pixel_clock)(unsigned int pixclock);
	enum fsl_diu_monitor_port (*valid_monitor_port)
		(enum fsl_diu_monitor_port port);
	void (*release_bootmem)(void);
};

extern struct platform_diu_data_ops diu_ops;

void __noreturn fsl_hv_restart(char *cmd);
void __noreturn fsl_hv_halt(void);

#endif
#endif

Annotation

• Immediate include surface: `asm/mmu.h`.
• Detected declarations: `struct spi_device`, `struct spi_board_info`, `struct device_node`, `struct platform_diu_data_ops`, `enum fsl_diu_monitor_port`, `function get_brgfreq`, `function get_baudrate`.
• Atlas domain: Architecture Layer / arch/powerpc.
• 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.