drivers/ssb/pcihost_wrapper.c

File Facts

System

Linux kernel

Corpus path

drivers/ssb/pcihost_wrapper.c

Extension

.c

Size

2860 bytes

Lines

131

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/pm.h
• linux/pci.h
• linux/export.h
• linux/slab.h
• linux/ssb/ssb.h

Detected Declarations

• function Copyright
• function ssb_pcihost_resume
• function ssb_pcihost_probe
• function ssb_pcihost_remove
• function ssb_pcihost_register
• export ssb_pcihost_register

Annotated Snippet

int ssb_pcihost_register(struct pci_driver *driver)
{
	driver->probe = ssb_pcihost_probe;
	driver->remove = ssb_pcihost_remove;
#ifdef CONFIG_PM_SLEEP
	driver->driver.pm = &ssb_pcihost_pm_ops;
#endif

	return pci_register_driver(driver);
}
EXPORT_SYMBOL(ssb_pcihost_register);

Annotation

• Immediate include surface: `linux/pm.h`, `linux/pci.h`, `linux/export.h`, `linux/slab.h`, `linux/ssb/ssb.h`.
• Detected declarations: `function Copyright`, `function ssb_pcihost_resume`, `function ssb_pcihost_probe`, `function ssb_pcihost_remove`, `function ssb_pcihost_register`, `export ssb_pcihost_register`.
• 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.