drivers/rpmsg/virtio_rpmsg_bus.c

File Facts

System

Linux kernel

Corpus path

drivers/rpmsg/virtio_rpmsg_bus.c

Extension

.c

Size

28849 bytes

Lines

1026

Domain

Driver Families

Bucket

drivers/rpmsg

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/dma-mapping.h
• linux/idr.h
• linux/jiffies.h
• linux/kernel.h
• linux/module.h
• linux/mutex.h
• linux/rpmsg.h
• linux/rpmsg/byteorder.h
• linux/rpmsg/ns.h
• linux/scatterlist.h
• linux/slab.h
• linux/sched.h
• linux/virtio.h
• linux/virtio_ids.h
• linux/virtio_config.h
• linux/wait.h
• rpmsg_internal.h

Detected Declarations

• struct virtproc_info
• struct rpmsg_hdr
• struct virtio_rpmsg_channel
• function location
• function __ept_release
• function virtio_rpmsg_release_channel
• function __rpmsg_destroy_ept
• function virtio_rpmsg_destroy_ept
• function virtio_rpmsg_announce_create
• function virtio_has_feature
• function virtio_rpmsg_announce_destroy
• function virtio_has_feature
• function virtio_rpmsg_release_device
• function rpmsg_send_offchannel_raw
• function virtio_rpmsg_send
• function virtio_rpmsg_sendto
• function virtio_rpmsg_trysend
• function virtio_rpmsg_trysendto
• function virtio_rpmsg_poll
• function virtio_rpmsg_get_mtu
• function rpmsg_recv_single
• function rpmsg_recv_done
• function rpmsg_xmit_done
• function rpmsg_virtio_del_ctrl_dev
• function rpmsg_probe
• function rpmsg_remove_device
• function rpmsg_remove
• function rpmsg_init
• function rpmsg_fini
• module init rpmsg_init

Annotated Snippet

subsys_initcall(rpmsg_init);

static void __exit rpmsg_fini(void)
{
	unregister_virtio_driver(&virtio_ipc_driver);
}
module_exit(rpmsg_fini);

MODULE_DEVICE_TABLE(virtio, id_table);
MODULE_DESCRIPTION("Virtio-based remote processor messaging bus");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/dma-mapping.h`, `linux/idr.h`, `linux/jiffies.h`, `linux/kernel.h`, `linux/module.h`, `linux/mutex.h`, `linux/rpmsg.h`, `linux/rpmsg/byteorder.h`.
• Detected declarations: `struct virtproc_info`, `struct rpmsg_hdr`, `struct virtio_rpmsg_channel`, `function location`, `function __ept_release`, `function virtio_rpmsg_release_channel`, `function __rpmsg_destroy_ept`, `function virtio_rpmsg_destroy_ept`, `function virtio_rpmsg_announce_create`, `function virtio_has_feature`.
• Atlas domain: Driver Families / drivers/rpmsg.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.