Lines Matching full:rpmsg

42  * rpmsg_device - device that belong to the rpmsg bus
44  * @id: device id (used to match between rpmsg drivers and devices)
48  * @ept: the rpmsg endpoint of this channel
49  * @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
73  * @addr: local rpmsg address
76  * In essence, an rpmsg endpoint represents a listener on the rpmsg bus, as
77  * it binds an rpmsg address with an rx callback handler.
79  * Simple rpmsg drivers shouldn't use this struct directly, because
80  * things just work: every rpmsg driver provides an rx callback upon
81  * registering to the bus, and that callback is then bound to its rpmsg
84  * the rpmsg channel), the driver's handler is invoked to process it.
86  * More complicated drivers though, that do need to allocate additional rpmsg
103  * struct rpmsg_driver - rpmsg driver struct
105  * @id_table: rpmsg ids serviced by this driver
106  * @probe: invoked when a matching rpmsg channel (i.e. device) is found
107  * @remove: invoked when the rpmsg channel is removed
279  * module_rpmsg_driver() - Helper macro for registering an rpmsg driver
282  * Helper macro for rpmsg drivers which do not do anything special in module