include/linux/mfd/cgbc.h

File Facts

System

Linux kernel

Corpus path

include/linux/mfd/cgbc.h

Extension

.h

Size

1229 bytes

Lines

45

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

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

Detected Declarations

• struct cgbc_version
• struct cgbc_device_data

Annotated Snippet

struct cgbc_version {
	unsigned char feature;
	unsigned char major;
	unsigned char minor;
};

/**
 * struct cgbc_device_data - Internal representation of the Board Controller device
 * @io_session:		Pointer to the session IO memory
 * @io_cmd:		Pointer to the command IO memory
 * @session:		Session id returned by the Board Controller
 * @dev:		Pointer to kernel device structure
 * @version:		Board Controller version structure
 * @lock:		Board Controller mutex
 */
struct cgbc_device_data {
	void __iomem		*io_session;
	void __iomem		*io_cmd;
	u8			session;
	struct device		*dev;
	struct cgbc_version	version;
	struct mutex		lock;
};

int cgbc_command(struct cgbc_device_data *cgbc, void *cmd, unsigned int cmd_size,
		 void *data, unsigned int data_size, u8 *status);

#endif /*_LINUX_MFD_CGBC_H_*/

Annotation

• Detected declarations: `struct cgbc_version`, `struct cgbc_device_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.