drivers/ssb/b43_pci_bridge.c

File Facts

System

Linux kernel

Corpus path

drivers/ssb/b43_pci_bridge.c

Extension

.c

Size

1879 bytes

Lines

61

Domain

Driver Families

Bucket

drivers/ssb

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• ssb_private.h
• linux/pci.h
• linux/module.h
• linux/ssb/ssb.h

Detected Declarations

• function b43_pci_ssb_bridge_init
• function b43_pci_ssb_bridge_exit

Annotated Snippet

static struct pci_driver b43_pci_bridge_driver = {
	.name = "b43-pci-bridge",
	.id_table = b43_pci_bridge_tbl,
};


int __init b43_pci_ssb_bridge_init(void)
{
	return ssb_pcihost_register(&b43_pci_bridge_driver);
}

void __exit b43_pci_ssb_bridge_exit(void)
{
	ssb_pcihost_unregister(&b43_pci_bridge_driver);
}

Annotation

• Immediate include surface: `ssb_private.h`, `linux/pci.h`, `linux/module.h`, `linux/ssb/ssb.h`.
• Detected declarations: `function b43_pci_ssb_bridge_init`, `function b43_pci_ssb_bridge_exit`.
• Atlas domain: Driver Families / drivers/ssb.
• Implementation status: pattern 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.