Lines Matching full:ipc

545                                                     The IPC service can use this constant to limit
546 the storage space for IPC endpoint names. */
552 @Description Callback function used upon IPC non-blocking transaction completion
556 IPC message to indicate a non-blocking send (see also XX_IpcSendMessage() routine).
557 … Upon completion of an IPC transaction (consisting of a message and an optional reply),
558 … the IPC service invokes this callback routine to return the message buffer to the sender
573 …@Param[in] status - Completion status - E_OK or failure indication, e.g. IPC transact…
587 @Description Callback function used as IPC message handler.
589 The IPC service invokes message handlers for each IPC message received.
602 by the IPC service;
603 … The reply buffer is allocated by the IPC service with size equals to the
607 … the IPC service may set this pointer to NULL and assume that a reply is not needed;
608 … The IPC service is also responsible for freeing the reply buffer after the
614 … this value is set to zero, the IPC service must assume that a reply should
629 @Description IPC mailbox registration.
631 This function is used for registering an IPC message handler in the IPC service.
633 … to handle incoming messages. The IPC service invokes the message handler upon receiving
637 … This address must be unique across the IPC service domain to ensure
640 message; invoked by the IPC service upon receiving a message
646 … may generate; the IPC service provides the message handler with buffer
661 @Description Release IPC mailbox routine.
663 … This function is used for unregistering an IPC message handler from the IPC service.
678 @Description This function is used for creating an IPC session between the source endpoint
681 … The actual implementation and representation of a session is left for the IPC service.
684 … The IPC service assumes that before this function is called, no messages are sent from
687 … The IPC service may use a connection-oriented approach or a connectionless approach (or both)
692 …The IPC service may implement a session in a connection-oriented approach - when this function is…
693 …the IPC service should take the necessary steps to bring up a source-to-destination channel for me…
699 …The IPC service may implement a session in a connectionless approach - when this function is call…
700IPC service should not perform any particular steps, but it must store the pair of source and dest…
702 …called, the IPC service may use this handle to provide the necessary identifiers for routing the m…
716 …@Description This function is used for terminating an existing IPC session between a source endp…
719 … The IPC service assumes that after this function is called, no messages shall be sent from
722 …@Param[in] h_Session - Abstract handle to the IPC session - the same handle as was origi…
732 @Description IPC message send routine.
734 … This function may be used by a source endpoint to send an IPC message to a destination
740 … transaction is not considered complete by the IPC service until the reply has been received.
748 …completion callback function (f_Completion). Upon completion of the IPC transaction (consisting of…
749 …message and an optional reply), the IPC service invokes this callback routine to return the message
755 …expected to block until the IPC transaction is complete - either the reply has been received or (…
758 …@Param[in] h_Session - Abstract handle to the IPC session - the same handle as was orig…
762 …@Param[in] p_Reply - Pointer to reply buffer - if this buffer is not NULL, the IPC se…
770 … [Out] in non-blocking mode this value is updated by the IPC service to the
773 The completion callback is invoked by the IPC service upon
774 … completion of the IPC transaction (consisting of a message and an optional
776 … If this pointer is NULL, the function is expected to block until the IPC