drivers/crypto/ccree/cc_driver.c

File Facts

System

Linux kernel

Corpus path

drivers/crypto/ccree/cc_driver.c

Extension

.c

Size

17621 bytes

Lines

677

Domain

Driver Families

Bucket

drivers/crypto

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.
• 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/kernel.h
• linux/module.h
• linux/crypto.h
• linux/moduleparam.h
• linux/types.h
• linux/interrupt.h
• linux/platform_device.h
• linux/slab.h
• linux/spinlock.h
• linux/of.h
• linux/clk.h
• linux/of_address.h
• linux/pm_runtime.h
• cc_driver.h
• cc_request_mgr.h
• cc_buffer_mgr.h
• cc_debugfs.h
• cc_cipher.h
• cc_aead.h
• cc_hash.h
• cc_sram_mgr.h
• cc_pm.h
• cc_fips.h

Detected Declarations

• struct cc_hw_data
• function init_cc_cache_params
• function cc_read_idr
• function __dump_byte_array
• function cc_isr
• function cc_wait_for_reset_completion
• function init_cc_regs
• function init_cc_resources
• function fini_cc_regs
• function cleanup_cc_resources
• function cc_get_default_hash_len
• function ccree_probe
• function ccree_remove
• function ccree_init
• function ccree_exit
• module init ccree_init

Annotated Snippet

module_init(ccree_init);

static void __exit ccree_exit(void)
{
	platform_driver_unregister(&ccree_driver);
	cc_debugfs_global_fini();
}
module_exit(ccree_exit);

/* Module description */
MODULE_DESCRIPTION("ARM TrustZone CryptoCell REE Driver");
MODULE_VERSION(DRV_MODULE_VERSION);
MODULE_AUTHOR("ARM");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/crypto.h`, `linux/moduleparam.h`, `linux/types.h`, `linux/interrupt.h`, `linux/platform_device.h`, `linux/slab.h`.
• Detected declarations: `struct cc_hw_data`, `function init_cc_cache_params`, `function cc_read_idr`, `function __dump_byte_array`, `function cc_isr`, `function cc_wait_for_reset_completion`, `function init_cc_regs`, `function init_cc_resources`, `function fini_cc_regs`, `function cleanup_cc_resources`.
• Atlas domain: Driver Families / drivers/crypto.
• Implementation status: integration implementation candidate.
• 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.