drivers/firmware/arm_scmi/transports/virtio.c

File Facts

System

Linux kernel

Corpus path

drivers/firmware/arm_scmi/transports/virtio.c

Extension

.c

Size

28768 bytes

Lines

980

Domain

Driver Families

Bucket

drivers/firmware

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.
• 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/completion.h
• linux/errno.h
• linux/platform_device.h
• linux/refcount.h
• linux/slab.h
• linux/virtio.h
• linux/virtio_config.h
• uapi/linux/virtio_ids.h
• uapi/linux/virtio_scmi.h
• ../common.h

Detected Declarations

• struct scmi_vio_channel
• struct scmi_vio_msg
• enum poll_states
• function scmi_vio_channel_ready
• function scmi_vio_channel_acquire
• function scmi_vio_channel_release
• function scmi_vio_channel_cleanup_sync
• function scmi_virtio_get_free_msg
• function scmi_vio_msg_acquire
• function scmi_vio_msg_release
• function scmi_vio_have_vq_rx
• function scmi_vio_feed_vq_rx
• function scmi_finalize_message
• function scmi_vio_complete_cb
• function scmi_vio_deferred_tx_worker
• function virtio_get_max_msg
• function virtio_chan_available
• function scmi_destroy_tx_workqueue
• function virtio_chan_setup
• function virtio_chan_free
• function virtio_send_message
• function virtio_fetch_response
• function virtio_fetch_notification
• function discarded
• function loop
• function scmi_vio_probe
• function scmi_vio_remove
• function scmi_vio_validate
• function scmi_transport_virtio_init
• function scmi_transport_virtio_exit
• module init scmi_transport_virtio_init

Annotated Snippet

module_init(scmi_transport_virtio_init);

static void __exit scmi_transport_virtio_exit(void)
{
	platform_driver_unregister(&scmi_virtio_driver);
	unregister_virtio_driver(&virtio_scmi_driver);
}
module_exit(scmi_transport_virtio_exit);

MODULE_AUTHOR("Igor Skalkin <igor.skalkin@opensynergy.com>");
MODULE_AUTHOR("Peter Hilber <peter.hilber@opensynergy.com>");
MODULE_AUTHOR("Cristian Marussi <cristian.marussi@arm.com>");
MODULE_DESCRIPTION("SCMI VirtIO Transport driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/completion.h`, `linux/errno.h`, `linux/platform_device.h`, `linux/refcount.h`, `linux/slab.h`, `linux/virtio.h`, `linux/virtio_config.h`, `uapi/linux/virtio_ids.h`.
• Detected declarations: `struct scmi_vio_channel`, `struct scmi_vio_msg`, `enum poll_states`, `function scmi_vio_channel_ready`, `function scmi_vio_channel_acquire`, `function scmi_vio_channel_release`, `function scmi_vio_channel_cleanup_sync`, `function scmi_virtio_get_free_msg`, `function scmi_vio_msg_acquire`, `function scmi_vio_msg_release`.
• Atlas domain: Driver Families / drivers/firmware.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.