Lines Matching refs:rpmsg

2 Remote Processor Messaging (rpmsg) Framework
7   This document describes the rpmsg bus and how to write rpmsg drivers.
8   To learn how to add rpmsg support for new platforms, check out remoteproc.txt
41 When writing a driver that exposes rpmsg communication to userland, please
50 desired to limit userland to specific rpmsg channels (see definition below)
54 Every rpmsg device is a communication channel with a remote processor (thus
55 rpmsg devices are called channels). Channels are identified by a textual name
56 and have a local ("source") rpmsg address, and remote ("destination") rpmsg
60 a unique rpmsg local address (a 32-bit integer). This way when inbound messages
61 arrive, the rpmsg core dispatches them to the appropriate driver according
203 every rpmsg address in the system is bound to an rx callback (so when
204 inbound messages arrive, they are dispatched by the rpmsg bus using the
208 bind a callback, and possibly some private data too, to an rpmsg address
212 Simple rpmsg drivers need not call rpmsg_create_ept, because an endpoint
213 is already created for them when they are probed by the rpmsg bus
214 (using the rx callback they provide when they registered to the rpmsg bus).
217 endpoint, their rx callback is bound to their rpmsg address, and when
219 equals to the src address of their rpmsg channel), the driver's handler
223 additional rpmsg addresses, and bind them to different rx callbacks.
230 dynamically assign them an available rpmsg address (drivers should have
240 destroys an existing rpmsg endpoint. user should provide a pointer
241 to an rpmsg endpoint that was previously created with rpmsg_create_ept().
248 registers an rpmsg driver with the rpmsg bus. user should provide
259 unregisters an rpmsg driver from the rpmsg bus. user should provide
267 The following is a simple rpmsg driver, that sends an "hello!" message
275   #include <linux/rpmsg.h>
302 	dev_info(&rpdev->dev, "rpmsg sample client driver is removed\n");
306 	{ .name	= "rpmsg-client-sample" },
309   MODULE_DEVICE_TABLE(rpmsg, rpmsg_driver_sample_id_table);
323    in samples/rpmsg/.
325 Allocations of rpmsg channels
328 At this point we only support dynamic allocations of rpmsg channels.
334 When this feature is enabled, creation of rpmsg devices (i.e. channels)
336 remote rpmsg service by sending a name service message (which contains
337 the name and rpmsg addr of the remote service, see struct rpmsg_ns_msg).
339 This message is then handled by the rpmsg bus, which in turn dynamically
340 creates and registers an rpmsg channel (which represents the remote service).
341 If/when a relevant rpmsg driver is registered, it will be immediately probed
344 The plan is also to add static creation of rpmsg channels via the virtio