Lines Matching full:rpmsg
20 #include <linux/rpmsg/byteorder.h>
21 #include <uapi/linux/rpmsg.h>
41 * rpmsg_device - device that belong to the rpmsg bus
43 * @id: device id (used to match between rpmsg drivers and devices)
49 * @ept: the rpmsg endpoint of this channel
50 * @announce: if set, rpmsg will announce the creation/removal of this channel
70 * struct rpmsg_endpoint - binds a local rpmsg address to its user
71 * @rpdev: rpmsg channel device
76 * @addr: local rpmsg address
79 * In essence, an rpmsg endpoint represents a listener on the rpmsg bus, as
80 * it binds an rpmsg address with an rx callback handler.
82 * Simple rpmsg drivers shouldn't use this struct directly, because
83 * things just work: every rpmsg driver provides an rx callback upon
84 * registering to the bus, and that callback is then bound to its rpmsg
87 * the rpmsg channel), the driver's handler is invoked to process it.
89 * More complicated drivers though, that do need to allocate additional rpmsg
106 * struct rpmsg_driver - rpmsg driver struct
108 * @id_table: rpmsg ids serviced by this driver
109 * @probe: invoked when a matching rpmsg channel (i.e. device) is found
110 * @remove: invoked when the rpmsg channel is removed
341 * module_rpmsg_driver() - Helper macro for registering an rpmsg driver
344 * Helper macro for rpmsg drivers which do not do anything special in module