Lines Matching refs:an
22 its own instance of RTOS in an AMP configuration.
86 Returns 0 on success and an appropriate error value on failure.
96 its length (in bytes), and an explicit destination address.
109 Returns 0 on success and an appropriate error value on failure.
133 Returns 0 on success and an appropriate error value on failure.
149 Returns 0 on success and an appropriate error value on failure.
160 its length (in bytes), and an explicit destination address.
170 Returns 0 on success and an appropriate error value on failure.
191 Returns 0 on success and an appropriate error value on failure.
199 every rpmsg address in the system is bound to an rx callback (so when
201 appropriate callback handler) by means of an rpmsg_endpoint struct.
203 This function allows drivers to create such an endpoint, and by that,
204 bind a callback, and possibly some private data too, to an rpmsg address
208 Simple rpmsg drivers need not call rpmsg_create_ept, because an endpoint
212 So things should just work for simple drivers: they already have an
222 to the same remote processor their channel belongs to), an rx callback
223 function, an optional private data (which is provided back when the
224 rx callback is invoked), and an address they want to bind with the
226 dynamically assign them an available rpmsg address (drivers should have
236 destroys an existing rpmsg endpoint. user should provide a pointer
237 to an rpmsg endpoint that was previously created with rpmsg_create_ept().
244 registers an rpmsg driver with the rpmsg bus. user should provide
245 a pointer to an rpmsg_driver struct, which contains the driver's
246 ->probe() and ->remove() functions, an rx callback, and an id_table
255 unregisters an rpmsg driver from the rpmsg bus. user should provide
257 Returns 0 on success, and an appropriate error value on failure.
263 The following is a simple rpmsg driver, that sends an "hello!" message
264 on probe(), and whenever it receives an incoming message, it dumps its
336 creates and registers an rpmsg channel (which represents the remote service).