include/linux/platform_data/mmc-pxamci.h

File Facts

System

Linux kernel

Corpus path

include/linux/platform_data/mmc-pxamci.h

Extension

.h

Size

882 bytes

Lines

28

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/mmc/host.h
• linux/interrupt.h

Detected Declarations

• struct device
• struct mmc_host
• struct property_entry
• struct pxamci_platform_data

Annotated Snippet

struct pxamci_platform_data {
	unsigned int ocr_mask;			/* available voltages */
	unsigned long detect_delay_ms;		/* delay in millisecond before detecting cards after interrupt */
	int (*init)(struct device *, irq_handler_t , void *);
	int (*get_ro)(struct device *);
	int (*setpower)(struct device *, unsigned int);
	void (*exit)(struct device *, void *);
	bool gpio_card_ro_invert;		/* gpio ro is inverted */
};

extern void pxa_set_mci_info(const struct pxamci_platform_data *info,
			     const struct property_entry *props);
extern void pxa3xx_set_mci2_info(struct pxamci_platform_data *info);
extern void pxa3xx_set_mci3_info(struct pxamci_platform_data *info);

#endif

Annotation

• Immediate include surface: `linux/mmc/host.h`, `linux/interrupt.h`.
• Detected declarations: `struct device`, `struct mmc_host`, `struct property_entry`, `struct pxamci_platform_data`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.