drivers/firmware/arm_scmi/raw_mode.h

File Facts

System

Linux kernel

Corpus path

drivers/firmware/arm_scmi/raw_mode.h

Extension

.h

Size

821 bytes

Lines

32

Domain

Driver Families

Bucket

drivers/firmware

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

• common.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _SCMI_RAW_MODE_H
#define _SCMI_RAW_MODE_H

#include "common.h"

enum {
	SCMI_RAW_REPLY_QUEUE,
	SCMI_RAW_NOTIF_QUEUE,
	SCMI_RAW_ERRS_QUEUE,
	SCMI_RAW_MAX_QUEUE
};

void *scmi_raw_mode_init(const struct scmi_handle *handle,
			 struct dentry *top_dentry, int instance_id,
			 u8 *channels, int num_chans,
			 const struct scmi_desc *desc, int tx_max_msg);
void scmi_raw_mode_cleanup(void *raw);

void scmi_raw_message_report(void *raw, struct scmi_xfer *xfer,
			     unsigned int idx, unsigned int chan_id);
void scmi_raw_error_report(void *raw, struct scmi_chan_info *cinfo,
			   u32 msg_hdr, void *priv);

#endif /* _SCMI_RAW_MODE_H */

Annotation

• Immediate include surface: `common.h`.
• Atlas domain: Driver Families / drivers/firmware.
• 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.