arch/powerpc/include/asm/ibmebus.h

File Facts

System

Linux kernel

Corpus path

arch/powerpc/include/asm/ibmebus.h

Extension

.h

Size

2235 bytes

Lines

63

Domain

Architecture Layer

Bucket

arch/powerpc

Inferred role

Architecture Layer: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h
• linux/interrupt.h
• linux/mod_devicetable.h
• linux/of_device.h
• linux/of_platform.h

Detected Declarations

• struct platform_driver

Annotated Snippet

extern const struct bus_type ibmebus_bus_type;

int ibmebus_register_driver(struct platform_driver *drv);
void ibmebus_unregister_driver(struct platform_driver *drv);

int ibmebus_request_irq(u32 ist, irq_handler_t handler,
			unsigned long irq_flags, const char *devname,
			void *dev_id);
void ibmebus_free_irq(u32 ist, void *dev_id);

#endif /* __KERNEL__ */
#endif /* _ASM_IBMEBUS_H */

Annotation

• Immediate include surface: `linux/device.h`, `linux/interrupt.h`, `linux/mod_devicetable.h`, `linux/of_device.h`, `linux/of_platform.h`.
• Detected declarations: `struct platform_driver`.
• Atlas domain: Architecture Layer / arch/powerpc.
• Implementation status: pattern implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.