Documentation/staging/rpmsg.rst

22 its own instance of RTOS in an AMP configuration.
87 Returns 0 on success and an appropriate error value on failure.
97 its length (in bytes), and an explicit destination address.
111 Returns 0 on success and an appropriate error value on failure.
136 Returns 0 on success and an appropriate error value on failure.
153 Returns 0 on success and an appropriate error value on failure.
164 its length (in bytes), and an explicit destination address.
174 Returns 0 on success and an appropriate error value on failure.
195 Returns 0 on success and an appropriate error value on failure.
203 every rpmsg address in the system is bound to an rx callback (so when
205 appropriate callback handler) by means of an rpmsg_endpoint struct.
207 This function allows drivers to create such an endpoint, and by that,
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
216 So things should just work for simple drivers: they already have an
226 to the same remote processor their channel belongs to), an rx callback
227 function, an optional private data (which is provided back when the
228 rx callback is invoked), and an address they want to bind with the
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
249 a pointer to an rpmsg_driver struct, which contains the driver's
250 ->probe() and ->remove() functions, an rx callback, and an id_table
259 unregisters an rpmsg driver from the rpmsg bus. user should provide
261 Returns 0 on success, and an appropriate error value on failure.
267 The following is a simple rpmsg driver, that sends an "hello!" message
268 on probe(), and whenever it receives an incoming message, it dumps its
340 creates and registers an rpmsg channel (which represents the remote service).