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)
47  * @ept: the rpmsg endpoint of this channel
48  * @announce: if set, rpmsg will announce the creation/removal of this channel
67  * struct rpmsg_endpoint - binds a local rpmsg address to its user
68  * @rpdev: rpmsg channel device
72  * @addr: local rpmsg address
75  * In essence, an rpmsg endpoint represents a listener on the rpmsg bus, as
76  * it binds an rpmsg address with an rx callback handler.
78  * Simple rpmsg drivers shouldn't use this struct directly, because
79  * things just work: every rpmsg driver provides an rx callback upon
80  * registering to the bus, and that callback is then bound to its rpmsg
83  * the rpmsg channel), the driver's handler is invoked to process it.
85  * More complicated drivers though, that do need to allocate additional rpmsg
101  * struct rpmsg_driver - rpmsg driver struct
103  * @id_table: rpmsg ids serviced by this driver
104  * @probe: invoked when a matching rpmsg channel (i.e. device) is found
105  * @remove: invoked when the rpmsg channel is removed
306  * module_rpmsg_driver() - Helper macro for registering an rpmsg driver
309  * Helper macro for rpmsg drivers which do not do anything special in module