drivers/char/tpm/tpmrm-dev.c

File Facts

System

Linux kernel

Corpus path

drivers/char/tpm/tpmrm-dev.c

Extension

.c

Size

1152 bytes

Lines

55

Domain

Driver Families

Bucket

drivers/char

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.
• 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/slab.h
• tpm-dev.h

Detected Declarations

• struct tpmrm_priv
• function tpmrm_open
• function tpmrm_release

Annotated Snippet

const struct file_operations tpmrm_fops = {
	.owner = THIS_MODULE,
	.open = tpmrm_open,
	.read = tpm_common_read,
	.write = tpm_common_write,
	.poll = tpm_common_poll,
	.release = tpmrm_release,
};

Annotation

• Immediate include surface: `linux/slab.h`, `tpm-dev.h`.
• Detected declarations: `struct tpmrm_priv`, `function tpmrm_open`, `function tpmrm_release`.
• Atlas domain: Driver Families / drivers/char.
• 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.