drivers/hwmon/i5500_temp.c

File Facts

System

Linux kernel

Corpus path

drivers/hwmon/i5500_temp.c

Extension

.c

Size

3394 bytes

Lines

140

Domain

Driver Families

Bucket

drivers/hwmon

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/bitops.h
• linux/module.h
• linux/init.h
• linux/device.h
• linux/pci.h
• linux/hwmon.h
• linux/err.h

Detected Declarations

• function Copyright
• function i5500_temp_probe

Annotated Snippet

static struct pci_driver i5500_temp_driver = {
	.name = "i5500_temp",
	.id_table = i5500_temp_ids,
	.probe = i5500_temp_probe,
};

module_pci_driver(i5500_temp_driver);

MODULE_AUTHOR("Jean Delvare <jdelvare@suse.de>");
MODULE_DESCRIPTION("Intel 5500/5520/X58 chipset thermal sensor driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/bitops.h`, `linux/module.h`, `linux/init.h`, `linux/device.h`, `linux/pci.h`, `linux/hwmon.h`, `linux/err.h`.
• Detected declarations: `function Copyright`, `function i5500_temp_probe`.
• Atlas domain: Driver Families / drivers/hwmon.
• 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.