drivers/char/tpm/tpm_ibmvtpm.c

File Facts

System

Linux kernel

Corpus path

drivers/char/tpm/tpm_ibmvtpm.c

Extension

.c

Size

17686 bytes

Lines

751

Domain

Driver Families

Bucket

drivers/char

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/dma-mapping.h
• linux/dmapool.h
• linux/slab.h
• asm/vio.h
• asm/irq.h
• linux/types.h
• linux/list.h
• linux/spinlock.h
• linux/interrupt.h
• linux/wait.h
• asm/prom.h
• tpm.h
• tpm_ibmvtpm.h

Detected Declarations

• function ibmvtpm_send_crq_word
• function ibmvtpm_send_crq
• function tpm_ibmvtpm_recv
• function ibmvtpm_crq_send_init
• function tpm_ibmvtpm_resume
• function tpm_ibmvtpm_send
• function tpm_ibmvtpm_resume
• function tpm_ibmvtpm_cancel
• function tpm_ibmvtpm_status
• function ibmvtpm_crq_get_rtce_size
• function ibmvtpm_crq_get_version
• function ibmvtpm_crq_send_init_complete
• function tpm_ibmvtpm_remove
• function tpm_ibmvtpm_get_desired_dma
• function tpm_ibmvtpm_suspend
• function ibmvtpm_reset_crq
• function tpm_ibmvtpm_req_canceled
• function ibmvtpm_crq_process
• function ibmvtpm_interrupt
• function tpm_ibmvtpm_probe
• function ibmvtpm_module_init
• function ibmvtpm_module_exit
• module init ibmvtpm_module_init

Annotated Snippet

module_init(ibmvtpm_module_init);
module_exit(ibmvtpm_module_exit);

MODULE_AUTHOR("adlai@us.ibm.com");
MODULE_DESCRIPTION("IBM vTPM Driver");
MODULE_VERSION("1.0");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/dma-mapping.h`, `linux/dmapool.h`, `linux/slab.h`, `asm/vio.h`, `asm/irq.h`, `linux/types.h`, `linux/list.h`, `linux/spinlock.h`.
• Detected declarations: `function ibmvtpm_send_crq_word`, `function ibmvtpm_send_crq`, `function tpm_ibmvtpm_recv`, `function ibmvtpm_crq_send_init`, `function tpm_ibmvtpm_resume`, `function tpm_ibmvtpm_send`, `function tpm_ibmvtpm_resume`, `function tpm_ibmvtpm_cancel`, `function tpm_ibmvtpm_status`, `function ibmvtpm_crq_get_rtce_size`.
• Atlas domain: Driver Families / drivers/char.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.