drivers/misc/mei/mkhi.h

File Facts

System

Linux kernel

Corpus path

drivers/misc/mei/mkhi.h

Extension

.h

Size

1089 bytes

Lines

56

Domain

Driver Families

Bucket

drivers/misc

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

Detected Declarations

• struct mkhi_rule_id
• struct mkhi_fwcaps
• struct mkhi_msg_hdr
• struct mkhi_msg
• struct mkhi_gfx_mem_ready

Annotated Snippet

struct mkhi_rule_id {
	__le16 rule_type;
	u8 feature_id;
	u8 reserved;
} __packed;

struct mkhi_fwcaps {
	struct mkhi_rule_id id;
	u8 len;
	u8 data[];
} __packed;

struct mkhi_msg_hdr {
	u8  group_id;
	u8  command;
	u8  reserved;
	u8  result;
} __packed;

struct mkhi_msg {
	struct mkhi_msg_hdr hdr;
	u8 data[];
} __packed;

struct mkhi_gfx_mem_ready {
	struct mkhi_msg_hdr hdr;
	u32    flags;
} __packed;

#endif /* _MEI_MKHI_H_ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct mkhi_rule_id`, `struct mkhi_fwcaps`, `struct mkhi_msg_hdr`, `struct mkhi_msg`, `struct mkhi_gfx_mem_ready`.
• Atlas domain: Driver Families / drivers/misc.
• 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.