drivers/platform/x86/intel/ifs/core.c
Source file repositories/reference/linux-study-clean/drivers/platform/x86/intel/ifs/core.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/platform/x86/intel/ifs/core.c- Extension
.c- Size
- 3761 bytes
- Lines
- 159
- Domain
- Driver Families
- Bucket
- drivers/platform
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bitfield.hlinux/module.hlinux/kdev_t.hlinux/semaphore.hlinux/slab.hasm/cpu_device_id.hasm/msr.hifs.h
Detected Declarations
function ifs_cleanupfunction ifs_initfunction ifs_exitmodule init ifs_init
Annotated Snippet
module_init(ifs_init);
module_exit(ifs_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Intel In Field Scan (IFS) device");Annotation
- Immediate include surface: `linux/bitfield.h`, `linux/module.h`, `linux/kdev_t.h`, `linux/semaphore.h`, `linux/slab.h`, `asm/cpu_device_id.h`, `asm/msr.h`, `ifs.h`.
- Detected declarations: `function ifs_cleanup`, `function ifs_init`, `function ifs_exit`, `module init ifs_init`.
- Atlas domain: Driver Families / drivers/platform.
- Implementation status: integration 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.