include/linux/rpmsg/qcom_smd.h
Source file repositories/reference/linux-study-clean/include/linux/rpmsg/qcom_smd.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/rpmsg/qcom_smd.h- Extension
.h- Size
- 595 bytes
- Lines
- 32
- 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
Detected Declarations
struct qcom_smd_edgefunction qcom_smd_register_edgefunction qcom_smd_unregister_edge
Annotated Snippet
#ifndef _LINUX_RPMSG_QCOM_SMD_H
#define _LINUX_RPMSG_QCOM_SMD_H
#include <linux/device.h>
struct qcom_smd_edge;
#if IS_ENABLED(CONFIG_RPMSG_QCOM_SMD)
struct qcom_smd_edge *qcom_smd_register_edge(struct device *parent,
struct device_node *node);
void qcom_smd_unregister_edge(struct qcom_smd_edge *edge);
#else
static inline struct qcom_smd_edge *
qcom_smd_register_edge(struct device *parent,
struct device_node *node)
{
return NULL;
}
static inline void qcom_smd_unregister_edge(struct qcom_smd_edge *edge)
{
}
#endif
#endif
Annotation
- Immediate include surface: `linux/device.h`.
- Detected declarations: `struct qcom_smd_edge`, `function qcom_smd_register_edge`, `function qcom_smd_unregister_edge`.
- 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.