Lines Matching full:reply

55 3. the reply to an earlier non-blocking transmit (the ``sequence`` field will
64 of 2-byte messages). Note that the CEC kernel framework will also reply
71 If a non-blocking transmit also specified waiting for a reply, then
72 the reply will arrive in a later message. The ``sequence`` field can
115 	filled in by the driver with the length of the reply message if ``reply`` was set.
122 	then it will be replaced by 1000 if the ``reply`` is non-zero or
123 	ignored if ``reply`` is 0.
131 	In addition, if a non-blocking transmit will wait for a reply (ii.e. ``timeout``
132 	was not 0), then the ``sequence`` field of the reply will be set to the sequence
143 	the payload of the reply message if ``timeout`` was set.
145       - ``reply``
146       - Wait until this message is replied. If ``reply`` is 0 and the
147 	``timeout`` is 0, then don't wait for a reply but return after
149 	The case where ``reply`` is 0 (this is the opcode for the Feature Abort
152 	Feature Abort reply. In this case ``rx_status`` will either be set
156 	If the transmitter message is ``CEC_MSG_INITIATE_ARC`` then the ``reply``
161 	``reply`` field will be updated with the actual reply so that it is
211     * .. _`CEC-MSG-FL-REPLY-TO-FOLLOWERS`:
215       - If a CEC transmit expects a reply, then by default that reply is only sent to
217 	flag is set, then the reply is also sent to all followers, if any. If the
219 	follower, then that filehandle will receive the reply twice: once as the
235     * .. _`CEC-MSG-FL-REPLY-VENDOR-ID`:
240 	is set. If this flag is set, then the reply is expected to consist of
243 	``reply`` field.
337       - The reply to an earlier transmitted message timed out.
342       - The message was received successfully but the reply was
344 	was the reply to an earlier transmitted message.
349       - The wait for a reply to an earlier transmitted message was aborted
352 	reply was interrupted.