include/linux/mfd/mcp.h

File Facts

System

Linux kernel

Corpus path

include/linux/mfd/mcp.h

Extension

.h

Size

1647 bytes

Lines

64

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h

Detected Declarations

• struct mcp_ops
• struct mcp
• struct mcp_ops
• struct mcp_driver

Annotated Snippet

struct device_driver drv;
	int (*probe)(struct mcp *);
	void (*remove)(struct mcp *);
};

int mcp_driver_register(struct mcp_driver *);
void mcp_driver_unregister(struct mcp_driver *);

#define mcp_get_drvdata(mcp)	dev_get_drvdata(&(mcp)->attached_device)
#define mcp_set_drvdata(mcp,d)	dev_set_drvdata(&(mcp)->attached_device, d)

static inline void *mcp_priv(struct mcp *mcp)
{
	return mcp + 1;
}

#endif

Annotation

• Immediate include surface: `linux/device.h`.
• Detected declarations: `struct mcp_ops`, `struct mcp`, `struct mcp_ops`, `struct mcp_driver`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: pattern 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.