Searched full:message (Results 1 – 25 of 332) sorted by relevance
12345678910>>...14
11 - Message lock26 Message lock29 SoundWire message transfer lock. This mutex is part of30 Bus data structure (sdw_bus). This lock is used to serialize the message38 Message transfer.40 1. For every message transfer42 a. Acquire Message lock.44 b. Transfer message (Read/Write) to Slave1 or broadcast message on47 c. Release Message lock59 <-------------------------------+ a. Acquire Message lock[all …]
9 the user can send a message to the target to start failing read79 $ sudo dmsetup message dust1 0 addbadblock 6082 $ sudo dmsetup message dust1 0 addbadblock 6785 $ sudo dmsetup message dust1 0 addbadblock 7297 To enable the "fail read on bad block" behavior, send the "enable" message:99 $ sudo dmsetup message dust1 0 enable130 result in an "Invalid argument" error, as well as a helpful message:132 $ sudo dmsetup message dust1 0 addbadblock 88133 device-mapper: message ioctl on dust1 failed: Invalid argument137 result in an "Invalid argument" error, as well as a helpful message:[all …]
16 def warn(app, message): argument18 logger.warning(message)20 app.warn(message)22 def verbose(app, message): argument24 logger.verbose(message)26 app.verbose(message)
1 * FSL MPIC Message Registers4 representation of the message register blocks found in some FSL MPIC9 - compatible: Specifies the compatibility list for the message register12 the MPIC containing the message registers.15 message register block's addressable register space. The type shall be27 bit at bit 'n' indicates that message register 'n' can receive interrupts.29 be <u32>. If not present, then all of the message registers in the block34 An alias should be created for every message register block. They are not50 // Message registers 0 and 2 in this block can receive interrupts on59 // Message registers 0 and 2 in this block can receive interrupts on
1 Message unit node:3 For SRIO controllers that implement the message unit as part of the controller22 length of the SRIO configuration registers for message units39 Message Unit:53 length of the SRIO configuration registers for message units83 length of the SRIO configuration registers for message units113 length of the SRIO configuration registers for message units137 message-unit@0 {144 message-unit@100 {
20 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message44 To receive a CEC message the application has to fill in the50 is non-zero and no message arrived within ``timeout`` milliseconds, then53 A received message can be:55 1. a message received from another CEC device (the ``sequence`` field will60 To send a CEC message the application has to fill in the struct105 - Timestamp in ns of when the last byte of the message was transmitted.110 - Timestamp in ns of when the last byte of the message was received.115 - The length of the message. For :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>` this is filled in118 filled in by the driver with the length of the reply message if ``reply`` was set.[all …]
50 # <op>[,<mode>] rx-nack NACK the message instead of sending an ACK52 # <op>[,<mode>] rx-add-byte add a spurious byte to the received CEC message53 # <op>[,<mode>] rx-remove-byte remove the last byte from the received CEC message54 # <op>[,<mode>] rx-arb-lost <poll> generate a POLL message to trigger an arbitration lost65 # <op>[,<mode>] tx-add-bytes <num> append <num> (1-255) spurious bytes to the message66 # <op>[,<mode>] tx-remove-byte drop the last byte from the message76 # <op> CEC message opcode (0-255) or 'any'78 # <bit> CEC message bit (0-159)80 # <poll> CEC poll message used to test arbitration lost (0x00-0xff, default 0x0f)106 received or transmitted message, ``always`` to always trigger the error[all …]
51 When a CEC message is received, then the CEC framework will decide how52 it will be processed. If the message is a reply to an earlier53 transmitted message, then the reply is sent back to the filehandle that56 If the message is not a reply, then the CEC framework will process it57 first. If there is no follower, then the message is just discarded and a59 process it. If there is a follower, then the message is passed on to the61 the new message. The framework expects the follower to make the right204 Core message processing details:210 .. flat-table:: Core Message Processing221 does nothing and this message has to be handled by a follower[all …]
15 message envelopes may match, the pair that includes the earliest posted-send21 When a message is sent from the sender to the receiver, the communication24 this is an expected message, otherwise it is called an unexpected message.31 1. The Eager protocol- the complete message is sent when the send is39 A fin message needs to be received in order for the buffer to be reused.45 unexpected message list. The application posts receive buffers through calls51 pre-posted receive for this arriving message, it is passed to the software and52 placed in the unexpected message list. Otherwise the match is processed,57 When a receive-message is posted, the communication library will first check58 the software unexpected message list for a matching receive. If a match is[all …]
21 outside source. Message are parsed and delivered as the sequence is32 that is called when a full message has been completed.48 Temporarily pause a stream parser. Message parsing is suspended76 parser will parse. timeo is timeout for completing a message.84 buffer and message timeout is the receive timeout for the socket.99 parse_msg is called to determine the length of the next message102 next application layer message in the stream.106 where the message starts in the skb.110 >0 : indicates length of successfully parsed message111 0 : indicates more data must be received to parse the message[all …]
5 The design of the network interface message level setting.9 The design of the debugging message interface was guided and15 integer variable that controls the debug message level. The message18 The message level was not precisely defined past level 3, but were30 Initially this message level variable was uniquely named in each driver40 Per-interface rather than per-driver message level setting.64 The set of message levels is named
4 Kernel Connection Multiplexor (KCM) is a mechanism that provides a message based42 The multiplexor provides the message steering. In the transmit path, messages67 Message delineation70 Messages are sent over a TCP stream with some application protocol message72 of a received message can be deduced from the application protocol header75 A TCP stream must be parsed to determine message boundaries. Berkeley Packet78 a new message and is given an skbuff that contains the bytes received so far.79 It parses the message header and returns the length of the message. Given this80 information, KCM will construct the message of the stated length and deliver it95 KCM limits the maximum receive message size to be the size of the receive[all …]
13 0x10 Inbound Message Register 014 0x14 Inbound Message Register 115 0x18 Outbound Message Register 016 0x1C Outbound Message Register 128 0x10 Inbound Message Register 029 0x14 Inbound Message Register 130 0x18 Outbound Message Register 031 0x1C Outbound Message Register 153 0x10 Inbound Message Register54 0x14 Outbound Message Register[all …]
57 2.2 Message passing locks62 managed through three locks: "token", "message", and "ack", together63 with the Lock Value Block (LVB) of one of the "message" lock.76 other nodes to acknowledge the message before proceeding. Only one77 message can be processed at a time.79 3.1 Message Types96 RESYNCING message identifies a range of the devices that the105 the array. Message contains an identifier for that device. See112 array. The slot-number of the device is included in the message.137 3.2.2 message[all …]
1 Message-based devices4 Fusion message devices7 .. kernel-doc:: drivers/message/fusion/mptbase.c10 .. kernel-doc:: drivers/message/fusion/mptscsih.c
12 When the driver receives a special netlink message with the appropriate40 callback function which will be called when a message with above idx.val70 msg->seq and msg->ack are used to determine message genealogy. When71 someone sends a message, they use a locally unique sequence and random75 The sequence number is incremented with each message sent.77 If you expect a reply to the message, then the sequence number in the78 received message MUST be the same as in the original message, and the81 If we receive a message and its sequence number is not equal to one we82 are expecting, then it is a new message. If we receive a message and85 message + 1, then it is a new message.[all …]
1 Message Digest Algorithm Definitions5 :doc: Message Digest Algorithm Definitions10 Asynchronous Message Digest API14 :doc: Asynchronous Message Digest API28 Synchronous Message Digest API32 :doc: Synchronous Message Digest API
1 Texas Instruments' Message Manager Driver4 The Texas Instruments' Message Manager is a mailbox controller that has5 configurable queues selectable at SoC(System on Chip) integration. The Message10 Message Manager Device Node:14 - compatible: Shall be: "ti,k2g-message-manager"24 For ti,k2g-message-manager, this shall contain:33 compatible = "ti,k2g-message-manager";
7 registers map and Message RAM18 - bosch,mram-cfg : Message RAM configuration data.19 Multiple M_CAN instances can share the same Message21 number in Message RAM is also configurable,23 private Message RAM are used by this M_CAN controller.28 The 'offset' is an address offset of the Message RAM30 usually set to 0x0 if you're using a private Message43 Please refer to 2.4.1 Message RAM Configuration in
19 write functions behave a bit differently because the message formats26 HCI messages consist of an eight bit header and the message body. The27 header contains the message length. Maximum size for an HCI message is30 and third (LSB) bytes of the message. The maximum FW message length is
5 Message types24 __u8 type - message type.65 Each connector message can include one or more w1_netlink_msg with87 Replies to W1_LIST_MASTERS should send a message back to the userspace97 Each message is at most 4k in size, so if number of master devices111 [cn_msg, ack = 1 and increasing, 0 means the last message,119 w1_netlink_cmd->len = N * 8; where N is number of IDs in this message.142 as request message except that length parameters do not account for data155 request message (except lengths as described above).162 even if there were errors, only length mismatch interrupts message processing.[all …]
63 with the payload of the inbound message).73 sends a message across to the remote processor on a given channel.75 and its length (in bytes). The message will be sent on the specified92 sends a message across to the remote processor on a given channel,98 The message will then be sent to the remote processor to which the117 sends a message across to the remote processor, using the src and dst122 The message will then be sent to the remote processor to which the139 sends a message across to the remote processor on a given channel.141 and its length (in bytes). The message will be sent on the specified156 sends a message across to the remote processor on a given channel,[all …]
180 To transmit a new message:186 This transmits a new message. The attempts argument is the suggested number of190 wait when the line is free before attempting to send a message. This value191 depends on whether this transmit is a retry, a message from a new initiator or192 a new message for the same initiator. Most hardware will handle this240 the message was nacked (for a directed message) or241 acked (for a broadcast message). A retransmission is needed.257 could not transmit the message after trying multiple times.260 doesn't have to make another attempt to transmit the message282 When a CEC message was received:[all …]
6 SoC has it's own block of message RAM and IRQ for communication with the AOSS.7 The protocol used to communicate in the message RAM is known as Qualcomm26 Definition: the base address and size of the message RAM for this32 Definition: should specify the AOSS message IRQ for this client66 The following example represents the AOSS side-channel message RAM and the
68 CAPI's capi_ctr_handle_message() function to pass a received CAPI message to157 pointer to a callback function for sending a CAPI message to the168 to accepting or queueing the message. Errors occurring during the169 actual processing of the message should be signaled with an170 appropriate reply message.212 (skb). Each skb contains a single CAPI message coded according to the CAPI 2.0216 payload data immediately follows the CAPI message itself within the same skb.218 parameter may be omitted by setting the length field of the CAPI message to 22227 The _cmsg structure stores the contents of a CAPI 2.0 message in an easily241 Only those parameters appearing in the message type currently being processed[all …]