Lines Matching refs:an

17 its own instance of RTOS in an AMP configuration.
76      Returns 0 on success and an appropriate error value on failure.
82      its length (in bytes), and an explicit destination address.
93      Returns 0 on success and an appropriate error value on failure.
111      Returns 0 on success and an appropriate error value on failure.
123      Returns 0 on success and an appropriate error value on failure.
129      its length (in bytes), and an explicit destination address.
137      Returns 0 on success and an appropriate error value on failure.
152      Returns 0 on success and an appropriate error value on failure.
157    - every rpmsg address in the system is bound to an rx callback (so when
159      appropriate callback handler) by means of an rpmsg_endpoint struct.
161      This function allows drivers to create such an endpoint, and by that,
162      bind a callback, and possibly some private data too, to an rpmsg address
166      Simple rpmsg drivers need not call rpmsg_create_ept, because an endpoint
170      So things should just work for simple drivers: they already have an
180      to the same remote processor their channel belongs to), an rx callback
181      function, an optional private data (which is provided back when the
182      rx callback is invoked), and an address they want to bind with the
184      dynamically assign them an available rpmsg address (drivers should have
190    - destroys an existing rpmsg endpoint. user should provide a pointer
191      to an rpmsg endpoint that was previously created with rpmsg_create_ept().
194    - registers an rpmsg driver with the rpmsg bus. user should provide
195      a pointer to an rpmsg_driver struct, which contains the driver's
196      ->probe() and ->remove() functions, an rx callback, and an id_table
201    - unregisters an rpmsg driver from the rpmsg bus. user should provide
203      Returns 0 on success, and an appropriate error value on failure.
208 The following is a simple rpmsg driver, that sends an "hello!" message
209 on probe(), and whenever it receives an incoming message, it dumps its
288 creates and registers an rpmsg channel (which represents the remote service).