drivers/crypto/tegra/tegra-se-key.c
Source file repositories/reference/linux-study-clean/drivers/crypto/tegra/tegra-se-key.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/crypto/tegra/tegra-se-key.c- Extension
.c- Size
- 4499 bytes
- Lines
- 180
- Domain
- Driver Families
- Bucket
- drivers/crypto
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/bitops.hlinux/module.hcrypto/aes.htegra-se.h
Detected Declarations
function tegra_keyslot_allocfunction tegra_keyslot_freefunction tegra_key_prep_ins_cmdfunction tegra_key_in_ksltfunction tegra_key_insertfunction tegra_key_invalidatefunction tegra_key_invalidate_reservedfunction tegra_key_submit_reservedfunction tegra_key_submit
Annotated Snippet
if (!(*keyid)) {
dev_dbg(se->dev, "failed to allocate key slot\n");
return -ENOMEM;
}
}
ret = tegra_key_insert(se, key, keylen, *keyid, alg);
if (ret)
return ret;
return 0;
}
Annotation
- Immediate include surface: `linux/bitops.h`, `linux/module.h`, `crypto/aes.h`, `tegra-se.h`.
- Detected declarations: `function tegra_keyslot_alloc`, `function tegra_keyslot_free`, `function tegra_key_prep_ins_cmd`, `function tegra_key_in_kslt`, `function tegra_key_insert`, `function tegra_key_invalidate`, `function tegra_key_invalidate_reserved`, `function tegra_key_submit_reserved`, `function tegra_key_submit`.
- Atlas domain: Driver Families / drivers/crypto.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.