drivers/ufs/core/ufshcd-crypto.h

File Facts

System

Linux kernel

Corpus path

drivers/ufs/core/ufshcd-crypto.h

Extension

.h

Size

2814 bytes

Lines

114

Domain

Driver Families

Bucket

drivers/ufs

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• scsi/scsi_cmnd.h
• ufs/ufshcd.h
• ufs/ufshci.h

Detected Declarations

• function ufshcd_prepare_lrbp_crypto
• function ufshcd_prepare_req_desc_hdr_crypto
• function ufshcd_crypto_fill_prdt
• function ufshcd_crypto_clear_prdt
• function ufshcd_prepare_lrbp_crypto
• function ufshcd_crypto_clear_prdt
• function ufshcd_hba_init_crypto_capabilities
• function ufshcd_init_crypto

Annotated Snippet

static inline void ufshcd_init_crypto(struct ufs_hba *hba) { }

static inline void ufshcd_crypto_register(struct ufs_hba *hba,
					  struct request_queue *q) { }

#endif /* CONFIG_SCSI_UFS_CRYPTO */

#endif /* _UFSHCD_CRYPTO_H */

Annotation

• Immediate include surface: `scsi/scsi_cmnd.h`, `ufs/ufshcd.h`, `ufs/ufshci.h`.
• Detected declarations: `function ufshcd_prepare_lrbp_crypto`, `function ufshcd_prepare_req_desc_hdr_crypto`, `function ufshcd_crypto_fill_prdt`, `function ufshcd_crypto_clear_prdt`, `function ufshcd_prepare_lrbp_crypto`, `function ufshcd_crypto_clear_prdt`, `function ufshcd_hba_init_crypto_capabilities`, `function ufshcd_init_crypto`.
• Atlas domain: Driver Families / drivers/ufs.
• Implementation status: source 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.