arch/mips/include/asm/mach-bcm63xx/board_bcm963xx.h

File Facts

System

Linux kernel

Corpus path

arch/mips/include/asm/mach-bcm63xx/board_bcm963xx.h

Extension

.h

Size

1172 bytes

Lines

55

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/types.h
• linux/gpio.h
• linux/leds.h
• bcm63xx_dev_enet.h
• bcm63xx_dev_usb_usbd.h

Detected Declarations

• struct board_info

Annotated Snippet

struct board_info {
	u8		name[16];
	unsigned int	expected_cpu_id;

	/* enabled feature/device */
	unsigned int	has_enet0:1;
	unsigned int	has_enet1:1;
	unsigned int	has_enetsw:1;
	unsigned int	has_pci:1;
	unsigned int	has_pccard:1;
	unsigned int	has_ohci0:1;
	unsigned int	has_ehci0:1;
	unsigned int	has_usbd:1;
	unsigned int	has_uart0:1;
	unsigned int	has_uart1:1;

	/* ethernet config */
	struct bcm63xx_enet_platform_data enet0;
	struct bcm63xx_enet_platform_data enet1;
	struct bcm63xx_enetsw_platform_data enetsw;

	/* USB config */
	struct bcm63xx_usbd_platform_data usbd;

	/* GPIO LEDs */
	struct gpio_led leds[5];

	/* External PHY reset GPIO */
	unsigned int ephy_reset_gpio;

	/* External PHY reset GPIO flags from gpio.h */
	unsigned long ephy_reset_gpio_flags;
};

#endif /* ! BOARD_BCM963XX_H_ */

Annotation

• Immediate include surface: `linux/types.h`, `linux/gpio.h`, `linux/leds.h`, `bcm63xx_dev_enet.h`, `bcm63xx_dev_usb_usbd.h`.
• Detected declarations: `struct board_info`.
• 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.