drivers/power/reset/piix4-poweroff.c

File Facts

System

Linux kernel

Corpus path

drivers/power/reset/piix4-poweroff.c

Extension

.c

Size

2760 bytes

Lines

111

Domain

Driver Families

Bucket

drivers/power

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/delay.h
• linux/io.h
• linux/module.h
• linux/pci.h
• linux/pm.h

Detected Declarations

• enum piix4_pm_io_reg
• function piix4_poweroff
• function piix4_poweroff_probe
• function piix4_poweroff_remove

Annotated Snippet

static struct pci_driver piix4_poweroff_driver = {
	.name		= "piix4-poweroff",
	.id_table	= piix4_poweroff_ids,
	.probe		= piix4_poweroff_probe,
	.remove		= piix4_poweroff_remove,
};

module_pci_driver(piix4_poweroff_driver);
MODULE_AUTHOR("Paul Burton <paul.burton@mips.com>");
MODULE_DESCRIPTION("Intel PIIX4 power-off driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/delay.h`, `linux/io.h`, `linux/module.h`, `linux/pci.h`, `linux/pm.h`.
• Detected declarations: `enum piix4_pm_io_reg`, `function piix4_poweroff`, `function piix4_poweroff_probe`, `function piix4_poweroff_remove`.
• Atlas domain: Driver Families / drivers/power.
• 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.