drivers/mfd/rdc321x-southbridge.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/rdc321x-southbridge.c

Extension

.c

Size

2415 bytes

Lines

97

Domain

Driver Families

Bucket

drivers/mfd

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

• linux/module.h
• linux/kernel.h
• linux/platform_device.h
• linux/pci.h
• linux/mfd/core.h
• linux/mfd/rdc321x.h

Detected Declarations

• function rdc321x_sb_probe

Annotated Snippet

static struct pci_driver rdc321x_sb_driver = {
	.name		= "RDC321x Southbridge",
	.id_table	= rdc321x_sb_table,
	.probe		= rdc321x_sb_probe,
};

module_pci_driver(rdc321x_sb_driver);

MODULE_AUTHOR("Florian Fainelli <florian@openwrt.org>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("RDC R-321x MFD southbridge driver");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/platform_device.h`, `linux/pci.h`, `linux/mfd/core.h`, `linux/mfd/rdc321x.h`.
• Detected declarations: `function rdc321x_sb_probe`.
• Atlas domain: Driver Families / drivers/mfd.
• 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.