arch/arm/mach-orion5x/common.h

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-orion5x/common.h

Extension

.h

Size

2777 bytes

Lines

93

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/reboot.h

Detected Declarations

• struct mv643xx_eth_platform_data
• struct mv_sata_platform_data
• struct pci_bus
• struct pci_host_bridge
• struct pci_sys_data
• struct pci_dev
• struct tag
• function mss2_init
• function d2net_init

Annotated Snippet

static inline void mss2_init(void) {}
#endif

#ifdef CONFIG_MACH_D2NET_DT
void d2net_init(void);
#else
static inline void d2net_init(void) {}
#endif

/*****************************************************************************
 * Helpers to access Orion registers
 ****************************************************************************/
/*
 * These are not preempt-safe.  Locks, if needed, must be taken
 * care of by the caller.
 */
#define orion5x_setbits(r, mask)	writel(readl(r) | (mask), (r))
#define orion5x_clrbits(r, mask)	writel(readl(r) & ~(mask), (r))

#endif

Annotation

• Immediate include surface: `linux/reboot.h`.
• Detected declarations: `struct mv643xx_eth_platform_data`, `struct mv_sata_platform_data`, `struct pci_bus`, `struct pci_host_bridge`, `struct pci_sys_data`, `struct pci_dev`, `struct tag`, `function mss2_init`, `function d2net_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.