drivers/mmc/core/sdio_ops.h

File Facts

System

Linux kernel

Corpus path

drivers/mmc/core/sdio_ops.h

Extension

.h

Size

932 bytes

Lines

39

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

• linux/types.h
• linux/mmc/sdio.h

Detected Declarations

• struct mmc_host
• struct mmc_card
• struct work_struct
• function sdio_is_io_busy

Annotated Snippet

#ifndef _MMC_SDIO_OPS_H
#define _MMC_SDIO_OPS_H

#include <linux/types.h>
#include <linux/mmc/sdio.h>

struct mmc_host;
struct mmc_card;
struct work_struct;

int mmc_send_io_op_cond(struct mmc_host *host, u32 ocr, u32 *rocr);
int mmc_io_rw_direct(struct mmc_card *card, int write, unsigned fn,
	unsigned addr, u8 in, u8* out);
int mmc_io_rw_extended(struct mmc_card *card, int write, unsigned fn,
	unsigned addr, int incr_addr, u8 *buf, unsigned blocks, unsigned blksz);
int sdio_reset(struct mmc_host *host);
void sdio_irq_work(struct work_struct *work);

static inline bool sdio_is_io_busy(u32 opcode, u32 arg)
{
	u32 addr;

	addr = (arg >> 9) & 0x1FFFF;

	return (opcode == SD_IO_RW_EXTENDED ||
		(opcode == SD_IO_RW_DIRECT &&
		!(addr == SDIO_CCCR_ABORT || addr == SDIO_CCCR_SUSPEND)));
}

#endif

Annotation

• Immediate include surface: `linux/types.h`, `linux/mmc/sdio.h`.
• Detected declarations: `struct mmc_host`, `struct mmc_card`, `struct work_struct`, `function sdio_is_io_busy`.
• 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.