drivers/platform/x86/intel/atomisp2/pm.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/intel/atomisp2/pm.c

Extension

.c

Size

3821 bytes

Lines

144

Domain

Driver Families

Bucket

drivers/platform

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/module.h
• linux/mod_devicetable.h
• linux/pci.h
• linux/pm_runtime.h
• asm/iosf_mbi.h

Detected Declarations

• function Copyright
• function isp_probe
• function isp_remove
• function isp_pci_suspend
• function isp_pci_resume

Annotated Snippet

static struct pci_driver isp_pci_driver = {
	.name = "intel_atomisp2_pm",
	.id_table = isp_id_table,
	.probe = isp_probe,
	.remove = isp_remove,
	.driver.pm = &isp_pm_ops,
};

module_pci_driver(isp_pci_driver);

MODULE_DESCRIPTION("Intel AtomISP2 dummy / power-management drv (for suspend)");
MODULE_AUTHOR("Hans de Goede <hdegoede@redhat.com>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/delay.h`, `linux/module.h`, `linux/mod_devicetable.h`, `linux/pci.h`, `linux/pm_runtime.h`, `asm/iosf_mbi.h`.
• Detected declarations: `function Copyright`, `function isp_probe`, `function isp_remove`, `function isp_pci_suspend`, `function isp_pci_resume`.
• Atlas domain: Driver Families / drivers/platform.
• 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.