include/drm/intel/intel_lb_mei_interface.h

File Facts

System

Linux kernel

Corpus path

include/drm/intel/intel_lb_mei_interface.h

Extension

.h

Size

4656 bytes

Lines

105

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bits.h
• linux/types.h

Detected Declarations

• struct device
• struct intel_lb_component_ops
• enum intel_lb_type
• enum intel_lb_status

Annotated Snippet

struct intel_lb_component_ops {
	/**
	 * @push_payload: Sends a payload to the authentication firmware
	 *
	 * @dev: Device struct corresponding to the mei device
	 * @type: Payload type (see &enum intel_lb_type)
	 * @flags: Payload flags bitmap (e.g. %INTEL_LB_FLAGS_IS_PERSISTENT)
	 * @payload: Pointer to payload buffer
	 * @payload_size: Payload buffer size in bytes
	 *
	 * Return: 0 success, negative errno value on transport failure,
	 *         positive error status returned by firmware
	 */
	int (*push_payload)(struct device *dev, u32 type, u32 flags,
			    const void *payload, size_t payload_size);
};

#endif /* _INTEL_LB_MEI_INTERFACE_H_ */

Annotation

• Immediate include surface: `linux/bits.h`, `linux/types.h`.
• Detected declarations: `struct device`, `struct intel_lb_component_ops`, `enum intel_lb_type`, `enum intel_lb_status`.
• Atlas domain: Repository Root And Misc / include.
• 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.