include/linux/remoteproc/pruss.h

File Facts

System

Linux kernel

Corpus path

include/linux/remoteproc/pruss.h

Extension

.h

Size

1671 bytes

Lines

84

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/device.h
• linux/types.h

Detected Declarations

• struct device_node
• struct rproc
• enum pruss_pru_id
• enum pru_ctable_idx
• function pru_rproc_get
• function pru_rproc_put
• function is_pru_rproc

Annotated Snippet

static inline void pru_rproc_put(struct rproc *rproc) { }

static inline int pru_rproc_set_ctable(struct rproc *rproc,
				       enum pru_ctable_idx c, u32 addr)
{
	return -EOPNOTSUPP;
}

#endif /* CONFIG_PRU_REMOTEPROC */

static inline bool is_pru_rproc(struct device *dev)
{
	const char *drv_name = dev_driver_string(dev);

	if (strncmp(drv_name, PRU_RPROC_DRVNAME, sizeof(PRU_RPROC_DRVNAME)))
		return false;

	return true;
}

#endif /* __LINUX_PRUSS_H */

Annotation

• Immediate include surface: `linux/device.h`, `linux/types.h`.
• Detected declarations: `struct device_node`, `struct rproc`, `enum pruss_pru_id`, `enum pru_ctable_idx`, `function pru_rproc_get`, `function pru_rproc_put`, `function is_pru_rproc`.
• 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.