drivers/mfd/vx855.c

File Facts

System

Linux kernel

Corpus path

drivers/mfd/vx855.c

Extension

.c

Size

3238 bytes

Lines

124

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/kernel.h
• linux/module.h
• linux/device.h
• linux/platform_device.h
• linux/pci.h
• linux/mfd/core.h

Detected Declarations

• function vx855_probe
• function vx855_remove

Annotated Snippet

static struct pci_driver vx855_pci_driver = {
	.name		= "vx855",
	.id_table	= vx855_pci_tbl,
	.probe		= vx855_probe,
	.remove		= vx855_remove,
};

module_pci_driver(vx855_pci_driver);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Harald Welte <HaraldWelte@viatech.com>");
MODULE_DESCRIPTION("Driver for the VIA VX855 chipset");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/device.h`, `linux/platform_device.h`, `linux/pci.h`, `linux/mfd/core.h`.
• Detected declarations: `function vx855_probe`, `function vx855_remove`.
• 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.