drivers/char/tpm/tpm_atmel.c

File Facts

System

Linux kernel

Corpus path

drivers/char/tpm/tpm_atmel.c

Extension

.c

Size

6754 bytes

Lines

294

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.
• 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

• tpm.h

Detected Declarations

• struct tpm_atmel_priv
• enum tpm_atmel_addr
• enum tpm_atmel_write_status
• enum tpm_atmel_read_status
• function tpm_read_index
• function atmel_verify_tpm11
• function tpm_atml_recv
• function tpm_atml_send
• function tpm_atml_cancel
• function tpm_atml_status
• function tpm_atml_req_canceled
• function atml_plat_remove
• function init_atmel
• function cleanup_atmel
• module init init_atmel

Annotated Snippet

module_init(init_atmel);
module_exit(cleanup_atmel);

MODULE_AUTHOR("Leendert van Doorn <leendert@watson.ibm.com>");
MODULE_DESCRIPTION("TPM Driver");
MODULE_VERSION("2.0");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `tpm.h`.
• Detected declarations: `struct tpm_atmel_priv`, `enum tpm_atmel_addr`, `enum tpm_atmel_write_status`, `enum tpm_atmel_read_status`, `function tpm_read_index`, `function atmel_verify_tpm11`, `function tpm_atml_recv`, `function tpm_atml_send`, `function tpm_atml_cancel`, `function tpm_atml_status`.
• Atlas domain: Driver Families / drivers/char.
• 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.