arch/mips/include/asm/mach-bcm47xx/bcm47xx.h
Source file repositories/reference/linux-study-clean/arch/mips/include/asm/mach-bcm47xx/bcm47xx.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/include/asm/mach-bcm47xx/bcm47xx.h- Extension
.h- Size
- 757 bytes
- Lines
- 39
- 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
linux/ssb/ssb.hlinux/bcma/bcma.hlinux/bcma/bcma_soc.hlinux/bcm47xx_nvram.hlinux/bcm47xx_sprom.h
Detected Declarations
enum bcm47xx_bus_type
Annotated Snippet
#ifndef __ASM_BCM47XX_H
#define __ASM_BCM47XX_H
#include <linux/ssb/ssb.h>
#include <linux/bcma/bcma.h>
#include <linux/bcma/bcma_soc.h>
#include <linux/bcm47xx_nvram.h>
#include <linux/bcm47xx_sprom.h>
enum bcm47xx_bus_type {
#ifdef CONFIG_BCM47XX_SSB
BCM47XX_BUS_TYPE_SSB,
#endif
#ifdef CONFIG_BCM47XX_BCMA
BCM47XX_BUS_TYPE_BCMA,
#endif
};
union bcm47xx_bus {
#ifdef CONFIG_BCM47XX_SSB
struct ssb_bus ssb;
#endif
#ifdef CONFIG_BCM47XX_BCMA
struct bcma_soc bcma;
#endif
};
extern union bcm47xx_bus bcm47xx_bus;
extern enum bcm47xx_bus_type bcm47xx_bus_type;
void bcm47xx_set_system_type(u16 chip_id);
#endif /* __ASM_BCM47XX_H */
Annotation
- Immediate include surface: `linux/ssb/ssb.h`, `linux/bcma/bcma.h`, `linux/bcma/bcma_soc.h`, `linux/bcm47xx_nvram.h`, `linux/bcm47xx_sprom.h`.
- Detected declarations: `enum bcm47xx_bus_type`.
- 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.