arch/microblaze/include/asm/pci-bridge.h

File Facts

System

Linux kernel

Corpus path

arch/microblaze/include/asm/pci-bridge.h

Extension

.h

Size

1040 bytes

Lines

50

Domain

Architecture Layer

Bucket

arch/microblaze

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.h
• linux/list.h
• linux/ioport.h

Detected Declarations

• struct device_node
• struct pci_controller
• function pcibios_vaddr_is_ioport
• function isa_vaddr_is_ioport

Annotated Snippet

struct pci_controller {
	struct pci_bus *bus;
	struct list_head list_node;

	void __iomem *io_base_virt;

	/* Currently, we limit ourselves to 1 IO range and 3 mem
	 * ranges since the common pci_bus structure can't handle more
	 */
	struct resource io_resource;
};

#ifdef CONFIG_PCI
static inline int isa_vaddr_is_ioport(void __iomem *address)
{
	/* No specific ISA handling on ppc32 at this stage, it
	 * all goes through PCI
	 */
	return 0;
}
#endif /* CONFIG_PCI */

#endif	/* __KERNEL__ */
#endif	/* _ASM_MICROBLAZE_PCI_BRIDGE_H */

Annotation

• Immediate include surface: `linux/pci.h`, `linux/list.h`, `linux/ioport.h`.
• Detected declarations: `struct device_node`, `struct pci_controller`, `function pcibios_vaddr_is_ioport`, `function isa_vaddr_is_ioport`.
• Atlas domain: Architecture Layer / arch/microblaze.
• 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.