drivers/mmc/core/crypto.h

File Facts

System

Linux kernel

Corpus path

drivers/mmc/core/crypto.h

Extension

.h

Size

820 bytes

Lines

41

Domain

Driver Families

Bucket

drivers/mmc

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct mmc_host
• struct mmc_queue_req
• struct request_queue
• function mmc_crypto_set_initial_state

Annotated Snippet

#ifndef _MMC_CORE_CRYPTO_H
#define _MMC_CORE_CRYPTO_H

struct mmc_host;
struct mmc_queue_req;
struct request_queue;

#ifdef CONFIG_MMC_CRYPTO

void mmc_crypto_set_initial_state(struct mmc_host *host);

void mmc_crypto_setup_queue(struct request_queue *q, struct mmc_host *host);

void mmc_crypto_prepare_req(struct mmc_queue_req *mqrq);

#else /* CONFIG_MMC_CRYPTO */

static inline void mmc_crypto_set_initial_state(struct mmc_host *host)
{
}

static inline void mmc_crypto_setup_queue(struct request_queue *q,
					  struct mmc_host *host)
{
}

static inline void mmc_crypto_prepare_req(struct mmc_queue_req *mqrq)
{
}

#endif /* !CONFIG_MMC_CRYPTO */

#endif /* _MMC_CORE_CRYPTO_H */

Annotation

• Detected declarations: `struct mmc_host`, `struct mmc_queue_req`, `struct request_queue`, `function mmc_crypto_set_initial_state`.
• Atlas domain: Driver Families / drivers/mmc.
• 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.