arch/parisc/kernel/pci.c
Source file repositories/reference/linux-study-clean/arch/parisc/kernel/pci.c
File Facts
- System
- Linux kernel
- Corpus path
arch/parisc/kernel/pci.c- Extension
.c- Size
- 7182 bytes
- Lines
- 272
- Domain
- Architecture Layer
- Bucket
- arch/parisc
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/align.hlinux/eisa.hlinux/init.hlinux/module.hlinux/kernel.hlinux/pci.hlinux/types.hasm/io.hasm/superio.h
Detected Declarations
function pcibios_initfunction pcibios_fixup_busfunction pci_set_masterfunction pcibios_init_bridgefunction resourcesfunction parityfunction pcibios_register_hbamodule init pcibios_init
Annotated Snippet
subsys_initcall(pcibios_init);
Annotation
- Immediate include surface: `linux/align.h`, `linux/eisa.h`, `linux/init.h`, `linux/module.h`, `linux/kernel.h`, `linux/pci.h`, `linux/types.h`, `asm/io.h`.
- Detected declarations: `function pcibios_init`, `function pcibios_fixup_bus`, `function pci_set_master`, `function pcibios_init_bridge`, `function resources`, `function parity`, `function pcibios_register_hba`, `module init pcibios_init`.
- Atlas domain: Architecture Layer / arch/parisc.
- Implementation status: integration 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.