arch/sparc/include/asm/pbm.h
Source file repositories/reference/linux-study-clean/arch/sparc/include/asm/pbm.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/include/asm/pbm.h- Extension
.h- Size
- 1505 bytes
- Lines
- 49
- Domain
- Architecture Layer
- Bucket
- arch/sparc
- 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/pci.hasm/oplib.hasm/prom.h
Detected Declarations
struct linux_pbm_infostruct pcidev_cookie
Annotated Snippet
struct linux_pbm_info {
int prom_node;
char prom_name[64];
/* struct linux_prom_pci_ranges pbm_ranges[PROMREG_MAX]; */
/* int num_pbm_ranges; */
/* Now things for the actual PCI bus probes. */
unsigned int pci_first_busno; /* Can it be nonzero? */
struct pci_bus *pci_bus; /* Was inline, MJ allocs now */
};
/* PCI devices which are not bridges have this placed in their pci_dev
* sysdata member. This makes OBP aware PCI device drivers easier to
* code.
*/
struct pcidev_cookie {
struct linux_pbm_info *pbm;
struct device_node *prom_node;
};
#endif /* !(__SPARC_PBM_H) */
Annotation
- Immediate include surface: `linux/pci.h`, `asm/oplib.h`, `asm/prom.h`.
- Detected declarations: `struct linux_pbm_info`, `struct pcidev_cookie`.
- Atlas domain: Architecture Layer / arch/sparc.
- 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.