drivers/crypto/caam/jr.c

File Facts

System

Linux kernel

Corpus path

drivers/crypto/caam/jr.c

Extension

.c

Size

22132 bytes

Lines

843

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.
• 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/of_irq.h
• linux/of_address.h
• linux/platform_device.h
• compat.h
• ctrl.h
• regs.h
• jr.h
• desc.h
• intern.h

Detected Declarations

• struct jr_driver_data
• function register_algs
• function unregister_algs
• function caam_jr_crypto_engine_exit
• function caam_jr_stop_processing
• function caam_jr_flush
• function caam_jr_restart_processing
• function caam_reset_hw_jr
• function caam_jr_shutdown
• function caam_jr_remove
• function caam_jr_remove
• function caam_jr_interrupt
• function queue
• function caam_jr_dequeue
• function caam_jr_alloc
• function list_for_each_entry
• function caam_jr_free
• function caam_jr_enqueue
• function caam_jr_init_hw
• function caam_jr_reset_index
• function caam_jr_init
• function caam_jr_irq_dispose_mapping
• function caam_jr_probe
• function caam_jr_get_hw_state
• function caam_jr_suspend
• function caam_jr_resume
• function jr_driver_init
• function jr_driver_exit
• module init jr_driver_init
• export caam_jr_alloc
• export caam_jr_free
• export caam_jr_enqueue

Annotated Snippet

module_init(jr_driver_init);
module_exit(jr_driver_exit);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("FSL CAAM JR request backend");
MODULE_AUTHOR("Freescale Semiconductor - NMG/STC");

Annotation

• Immediate include surface: `linux/of_irq.h`, `linux/of_address.h`, `linux/platform_device.h`, `compat.h`, `ctrl.h`, `regs.h`, `jr.h`, `desc.h`.
• Detected declarations: `struct jr_driver_data`, `function register_algs`, `function unregister_algs`, `function caam_jr_crypto_engine_exit`, `function caam_jr_stop_processing`, `function caam_jr_flush`, `function caam_jr_restart_processing`, `function caam_reset_hw_jr`, `function caam_jr_shutdown`, `function caam_jr_remove`.
• Atlas domain: Driver Families / drivers/crypto.
• 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.