arch/mips/pci/pci-bcm63xx.h
Source file repositories/reference/linux-study-clean/arch/mips/pci/pci-bcm63xx.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/pci/pci-bcm63xx.h- Extension
.h- Size
- 730 bytes
- Lines
- 34
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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
bcm63xx_cpu.hbcm63xx_io.hbcm63xx_regs.hbcm63xx_dev_pci.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef PCI_BCM63XX_H_
#define PCI_BCM63XX_H_
#include <bcm63xx_cpu.h>
#include <bcm63xx_io.h>
#include <bcm63xx_regs.h>
#include <bcm63xx_dev_pci.h>
/*
* Cardbus shares the PCI bus, but has no IDSEL, so a special id is
* reserved for it. If you have a standard PCI device at this id, you
* need to change the following definition.
*/
#define CARDBUS_PCI_IDSEL 0x8
#define PCIE_BUS_BRIDGE 0
#define PCIE_BUS_DEVICE 1
/*
* defined in ops-bcm63xx.c
*/
extern struct pci_ops bcm63xx_pci_ops;
extern struct pci_ops bcm63xx_cb_ops;
extern struct pci_ops bcm63xx_pcie_ops;
/*
* defined in pci-bcm63xx.c
*/
extern void __iomem *pci_iospace_start;
#endif /* ! PCI_BCM63XX_H_ */
Annotation
- Immediate include surface: `bcm63xx_cpu.h`, `bcm63xx_io.h`, `bcm63xx_regs.h`, `bcm63xx_dev_pci.h`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.