| /linux/arch/powerpc/include/asm/ |
| H A D | mpic_msgr.h | 23 /* Get a message register
25 * @reg_num: the MPIC message register to get
27 * A pointer to the message register is returned. If
28 * the message register asked for is already in use, then
30 * with an actual message register, then ENODEV is returned.
35 /* Relinquish a message register
37 * @msgr: the message register to return
39 * Disables the given message register and marks it as free.
40 * After this call has completed successully the message
46 /* Enable a message register
[all …]
|
| /linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_protocol_ops.h | 33 * enum ipc_mem_msg_cs - Completion status of IPC Message
35 * @IPC_MEM_MSG_CS_SUCCESS: IPC Message completion success.
36 * @IPC_MEM_MSG_CS_ERROR: Message send error.
45 * struct ipc_msg_prep_args_pipe - struct for pipe args for message preparation
53 * struct ipc_msg_prep_args_sleep - struct for sleep args for message
65 * message preparation
73 * struct ipc_msg_prep_map - struct for map argument for message preparation
85 * struct ipc_msg_prep_unmap - struct for unmap argument for message preparation
93 * struct ipc_msg_prep_args - Union to handle different message types
94 * @pipe_open: Pipe open message preparation struct
[all …]
|
| /linux/drivers/misc/sgi-gru/ |
| H A D | grukservices.h | 11 * Message queues using the GRU to send/receive messages.
13 * These function allow the user to create a message queue for
17 * the message. This is transparent to the caller.
24 * - cross partition message
32 void *mq; /* message queue vaddress */
42 * a message queue. The caller must ensure that the queue is
45 * Message queue size is the total number of bytes allocated
50 * mqd pointer to message queue descriptor
52 * bytes size of message queue in bytes
65 * Send a message to a message queue.
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi-raw | 1 What: /sys/kernel/debug/scmi/<n>/raw/message
5 Description: SCMI Raw synchronous message injection/snooping facility; write
6 a complete SCMI synchronous command message (header included)
12 and sent while the replies are read back one message at time
13 (receiving an EOF at each message boundary).
20 Description: SCMI Raw asynchronous message injection/snooping facility; write
21 a complete SCMI asynchronous command message (header included)
30 and sent while the replies are read back one message at time
31 (receiving an EOF at each message boundary).
38 Description: SCMI Raw message errors facility; any kind of timed-out or
[all …]
|
| /linux/drivers/scsi/arm/ |
| H A D | msgqueue.h | 7 * message queue handling
12 struct message { struct
19 struct message msg; argument
33 * Purpose : initialise a message queue
47 * Purpose : calculate the total length of all messages on the message queue
54 * Function: struct message *msgqueue_getmsg(MsgQueue_t *msgq, int msgno)
55 * Purpose : return a message & its length
56 * Params : msgq - queue to obtain message from
57 * : msgno - message number
58 * Returns : pointer to message string, or NULL
[all …]
|
| H A D | msgqueue.c | 7 * message queue handling
18 * Purpose : Allocate a message queue entry
19 * Params : msgq - message queue to claim entry for
20 * Returns : message queue entry or NULL.
34 * Purpose : free a message queue entry
35 * Params : msgq - message queue to free entry from
36 * mq - message queue entry to free
48 * Purpose : initialise a message queue
76 * Purpose : calculate the total length of all messages on the message queue
92 * Function: struct message *msgqueue_getmsg(MsgQueue_t *msgq, int msgno)
[all …]
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | locking.rst | 11 - Message lock
26 Message lock
29 SoundWire message transfer lock. This mutex is part of
30 Bus data structure (sdw_bus). This lock is used to serialize the message
38 Message transfer.
40 1. For every message transfer
42 a. Acquire Message lock.
44 b. Transfer message (Read/Write) to Slave1 or broadcast message on
47 c. Release Message lock
59 <-------------------------------+ a. Acquire Message lock
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-dust.rst | 9 the user can send a message to the target to start failing read
93 $ sudo dmsetup message dust1 0 addbadblock 60
96 $ sudo dmsetup message dust1 0 addbadblock 67
99 $ sudo dmsetup message dust1 0 addbadblock 72
111 To enable the "fail read on bad block" behavior, send the "enable" message::
113 $ sudo dmsetup message dust1 0 enable
144 result in an "Invalid argument" error, as well as a helpful message::
146 $ sudo dmsetup message dust1 0 addbadblock 88
147 device-mapper: message ioctl on dust1 failed: Invalid argument
151 result in an "Invalid argument" error, as well as a helpful message::
[all …]
|
| /linux/drivers/net/ethernet/meta/fbnic/ |
| H A D | fbnic_tlv.c | 14 * fbnic_tlv_msg_alloc - Allocate page and initialize FW message header
15 * @msg_id: Identifier for new message we are starting
17 * Return: pointer to start of message, or NULL on failure.
19 * Allocates a page and initializes message header at start of page.
20 * Initial message size is 1 DWORD which is just the header.
36 /* Copy header into start of message */ in fbnic_tlv_msg_alloc()
43 * fbnic_tlv_attr_put_flag - Add flag value to message
44 * @msg: Message header we are adding flag attribute to
45 * @attr_id: ID of flag attribute we are adding to message
49 * Adds a 1 DWORD flag attribute to the message. The presence of this
[all …]
|
| /linux/Documentation/networking/ |
| H A D | mctp.rst | 42 Since MCTP is message-based, only ``SOCK_DGRAM`` sockets are supported.
99 match the network, address, and message type will be received by this socket.
101 messages with the TO bit set, to indicate an incoming request message, rather
118 The ``smctp_type`` field specifies which message types to receive. Only the
121 receiving packets with and without a message integrity check footer.
123 ``sendto()``, ``sendmsg()``, ``send()`` : transmit an MCTP message
126 An MCTP message is transmitted using one of the ``sendto()``, ``sendmsg()`` or
135 /* set message destination */
142 /* arbitrary message to send, with message-type header */
152 EID. If ``MCTP_TAG_OWNER`` is not set, the message will be sent with the tag
[all …]
|
| /linux/drivers/greybus/ |
| H A D | operation.c | 113 * If no error occurs before sending the request message the only
215 static int gb_message_send(struct gb_message *message, gfp_t gfp) in gb_message_send() argument
217 struct gb_connection *connection = message->operation->connection; in gb_message_send()
219 trace_gb_message_send(message); in gb_message_send()
222 message, in gb_message_send()
227 * Cancel a message we have passed to the host device layer to be sent.
229 static void gb_message_cancel(struct gb_message *message) in gb_message_cancel() argument
231 struct gb_host_device *hd = message->operation->connection->hd; in gb_message_cancel()
233 hd->driver->message_cancel(message); in gb_message_cancel()
284 /* Cancel request message if scheduled by timeout. */ in gb_operation_work()
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | um_timetravel.h | 10 * struct um_timetravel_msg - UM time travel message
12 * This is the basic message type, going in both directions.
14 * This is the message passed between the host (user-mode Linux instance)
30 * @seq: sequence number for the message - shall be reflected in
42 /* max number of file descriptors that can be sent/received in a message */
46 * enum um_timetravel_shared_mem_fds - fds sent in ACK message for START message
51 * descriptor in the control message
56 * in the control message
63 * enum um_timetravel_start_ack - ack-time mask for start message
77 * @UM_TIMETRAVEL_ACK: response (ACK) to any previous message,
[all …]
|
| H A D | msg.h | 13 #define MSG_NOERROR 010000 /* no error if message is too big */
20 struct msg *msg_first; /* first message on queue,unused */
21 struct msg *msg_last; /* last message in queue,unused */
37 /* message buffer for msgsnd and msgrcv calls */
39 __kernel_long_t mtype; /* type of message */
40 char mtext[1]; /* message text */
65 * MSGMNB is the default size of a new message queue. Non-root tasks can
71 * MAXMAX is the maximum size of an individual message, it's a global
72 * (per-namespace) limit that applies for all message queues.
78 #define MSGMAX 8192 /* <= INT_MAX */ /* max size of message (bytes) */
[all …]
|
| /linux/tools/testing/selftests/user_events/ |
| H A D | user_events_selftests.h | 19 static inline bool tracefs_enabled(char **message, bool *fail, bool *umount) in tracefs_enabled() argument
24 *message = ""; in tracefs_enabled()
32 *message = "Tracefs is not installed"; in tracefs_enabled()
41 *message = "Cannot mount tracefs"; in tracefs_enabled()
52 *message = "Cannot access tracefs"; in tracefs_enabled()
60 static inline bool user_events_enabled(char **message, bool *fail, bool *umount) in user_events_enabled() argument
65 *message = ""; in user_events_enabled()
70 *message = "Must be run as root"; in user_events_enabled()
75 if (!tracefs_enabled(message, fail, umount)) in user_events_enabled()
84 *message = "user_events is not installed"; in user_events_enabled()
[all …]
|
| /linux/drivers/input/keyboard/ |
| H A D | applespi.c | 29 * The device and driver exchange messages (struct message); each message is
32 * message can be read from the device. A write exchange consists of writing a
33 * command message, immediately reading a short status packet, and then, upon
34 * receiving a GPE, reading the response message. Write exchanges cannot be
36 * write exchange is complete. Whether a received message is part of a read or
39 * A single message may be too large to fit in a single packet (which has a
114 * struct keyboard_protocol - keyboard message.
115 * message.type = 0x0110, message.length = 0x000a
122 * @crc16: crc over the whole message struct (message header +
150 * @crc16: on last finger: crc over the whole message struct
[all …]
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-receive.rst | 14 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message
39 To receive a CEC message the application has to fill in the
45 is non-zero and no message arrived within ``timeout`` milliseconds, then
48 A received message can be:
50 1. a message received from another CEC device (the ``sequence`` field will
58 To send a CEC message the application has to fill in the struct
72 the reply will arrive in a later message. The ``sequence`` field can
102 - Timestamp in ns of when the last byte of the message was transmitted.
107 - Timestamp in ns of when the last byte of the message was received.
112 - The length of the message. For :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>` this is filled in
[all …]
|
| /linux/include/crypto/ |
| H A D | hash.h | 22 * DOC: Message Digest Algorithm Definitions
24 * These data structures define modular message digest algorithm
31 * struct hash_alg_common - define properties of message digest
69 * struct ahash_alg - asynchronous message digest definition
79 * final message digest as this only adds more data into the
110 * is only needed for keyed message digests. SHAx/MDx/CRCx do NOT
180 * struct shash_alg - synchronous message digest definition
201 * @descsize: Size of the operational state for the message digest. This state
246 * DOC: Asynchronous Message Digest API
248 * The asynchronous message digest API is used with the ciphers of type
[all …]
|
| /linux/drivers/net/ethernet/intel/fm10k/ |
| H A D | fm10k_tlv.c | 7 * fm10k_tlv_msg_init - Initialize message block for TLV data storage
8 * @msg: Pointer to message block
9 * @msg_id: Message ID indicating message type
11 * This function return success if provided with a valid message pointer
25 * fm10k_tlv_attr_put_null_string - Place null terminated string on message
26 * @msg: Pointer to message block
48 /* write data to message */ in fm10k_tlv_attr_put_null_string()
61 /* write last piece of data to message */ in fm10k_tlv_attr_put_null_string()
64 /* record attribute header, update message length */ in fm10k_tlv_attr_put_null_string()
102 * fm10k_tlv_attr_put_mac_vlan - Store MAC/VLAN attribute in message
[all …]
|
| /linux/drivers/net/ethernet/intel/igb/ |
| H A D | e1000_mbx.c | 7 * igb_read_mbx - Reads a message from the mailbox
9 * @msg: The message buffer
14 * returns SUCCESS if it successfully read message from buffer
33 * igb_write_mbx - Write a message to the mailbox
35 * @msg: The message buffer
39 * returns SUCCESS if it successfully copied message into the buffer
128 * igb_poll_for_msg - Wait for message notification
132 * returns SUCCESS if it successfully received a message notification
157 * igb_poll_for_ack - Wait for message acknowledgement
161 * returns SUCCESS if it successfully received a message acknowledgement
[all …]
|
| /linux/drivers/crypto/intel/qat/qat_common/ |
| H A D | adf_pfvf_msg.h | 34 * | | Message Origin
35 * | Message Type
36 * Message-specific Data/Reserved
45 * | | Message Origin
46 * | Message Type
47 * Message-specific Data/Reserved
49 * Message Origin (Should always be 1)
53 * When a PF or VF attempts to send a message in the lower or upper 16 bits,
66 * Both the Interrupt bit and the Message Origin bit retain the same position
77 * | | Message Origin
[all …]
|
| H A D | adf_pfvf_vf_proto.c | 25 * adf_send_vf2pf_msg() - send VF to PF message
27 * @msg: Message to send
29 * This function allows the VF to send a message to the PF.
43 * adf_recv_pf2vf_msg() - receive a PF to VF message
46 * This function allows the VF to receive a message from the PF.
48 * Return: a valid message on success, zero otherwise.
59 * adf_send_vf2pf_req() - send VF2PF request message
61 * @msg: Request message to send
64 * This function sends a message that requires a response from the VF to the PF
100 dev_err(&GET_DEV(accel_dev), "PFVF response message timeout\n"); in adf_send_vf2pf_req()
[all …]
|
| /linux/tools/testing/selftests/drivers/net/ |
| H A D | netcons_fragmented_msg.sh | 4 # Test netconsole's message fragmentation functionality.
6 # When a message exceeds the maximum packet size, netconsole splits it into
42 # We have two headers in the message. Remove both to get the full message,
43 # and extract the full message.
51 # Remove the two headers from the received message
52 # This will return the message without any header, similarly to what
57 # Validate the message, which has two messages glued together.
60 # 13,468,514729715,-,ncfrag=0/1135;<message>
63 # Discard the netconsole headers, and assemble the full message
66 # check for the main message
[all …]
|
| /linux/Documentation/driver-api/md/ |
| H A D | md-cluster.rst | 57 2.2 Message passing locks
62 managed through three locks: "token", "message", and "ack", together
63 with the Lock Value Block (LVB) of one of the "message" lock.
76 other nodes to acknowledge the message before proceeding. Only one
77 message can be processed at a time.
79 3.1 Message Types
96 RESYNCING message identifies a range of the devices that the
105 the array. Message contains an identifier for that device. See
112 array. The slot-number of the device is included in the message.
137 3.2.2 message
[all …]
|
| /linux/drivers/gpu/drm/xe/abi/ |
| H A D | guc_relay_communication_abi.h | 22 * action that takes the `Relay Message`_ as opaque payload and requires the
23 * relay message identifier (RID) as additional parameter.
27 * The GuC forwards this `Relay Message`_ and its identifier to the PF driver
28 * in `GUC2PF_RELAY_FROM_VF`_ action. This event message additionally contains
32 * `VF2GUC_RELAY_TO_PF`_ action that in addition to the `Relay Message`_
33 * and the relay message identifier (RID) also takes the target VF identifier.
35 * The GuC uses this target VFID from the message to select where to send the
36 * `GUC2VF_RELAY_FROM_PF`_ with the embedded `Relay Message`_ with response::
77 * DOC: Relay Message
79 * The `Relay Message`_ is used by Physical Function (PF) driver and Virtual
[all …]
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | netlink-raw.rst | 71 [OUTER NEST OR MESSAGE LEVEL]
84 the wrapper attr has very similar characteristics to a netlink message. It may
87 a sub-message.
89 A sub-message attribute uses the value of another attribute as a selector key to
90 choose the right sub-message format. For example if the following attribute has
103 type: sub-message
104 sub-message: linkinfo-data-msg
107 Then we look for a sub-message definition called ``linkinfo-data-msg`` and use
109 correct format for the sub-message:
126 This would decode the attribute value as a sub-message with the attribute-set
[all …]
|