include/linux/rpmsg/ns.h

File Facts

System

Linux kernel

Corpus path

include/linux/rpmsg/ns.h

Extension

.h

Size

1309 bytes

Lines

46

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

• linux/mod_devicetable.h
• linux/rpmsg.h
• linux/rpmsg/byteorder.h
• linux/types.h

Detected Declarations

• struct rpmsg_ns_msg
• enum rpmsg_ns_flags

Annotated Snippet

struct rpmsg_ns_msg {
	char name[RPMSG_NAME_SIZE];
	__rpmsg32 addr;
	__rpmsg32 flags;
} __packed;

/**
 * enum rpmsg_ns_flags - dynamic name service announcement flags
 *
 * @RPMSG_NS_CREATE: a new remote service was just created
 * @RPMSG_NS_DESTROY: a known remote service was just destroyed
 */
enum rpmsg_ns_flags {
	RPMSG_NS_CREATE		= 0,
	RPMSG_NS_DESTROY	= 1,
};

/* Address 53 is reserved for advertising remote services */
#define RPMSG_NS_ADDR			(53)

int rpmsg_ns_register_device(struct rpmsg_device *rpdev);

#endif

Annotation

• Immediate include surface: `linux/mod_devicetable.h`, `linux/rpmsg.h`, `linux/rpmsg/byteorder.h`, `linux/types.h`.
• Detected declarations: `struct rpmsg_ns_msg`, `enum rpmsg_ns_flags`.
• 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.