Home
last modified time | relevance | path

Searched refs:message (Results 1 – 25 of 705) sorted by relevance

12345678910>>...29

/Linux-v4.19/drivers/s390/crypto/
Dzcrypt_msgtype50.c79 unsigned char message[128]; member
89 unsigned char message[256]; member
99 unsigned char message[512]; member
112 unsigned char message[128]; member
125 unsigned char message[256]; member
138 unsigned char message[512]; member
212 struct type50_meb1_msg *meb1 = ap_msg->message; in ICAMEX_msg_to_type50MEX_msg()
221 inp = meb1->message + sizeof(meb1->message) - mod_len; in ICAMEX_msg_to_type50MEX_msg()
223 struct type50_meb2_msg *meb2 = ap_msg->message; in ICAMEX_msg_to_type50MEX_msg()
232 inp = meb2->message + sizeof(meb2->message) - mod_len; in ICAMEX_msg_to_type50MEX_msg()
[all …]
Dzcrypt_msgtype6.c272 } __packed * msg = ap_msg->message; in ICAMEX_msg_to_type6MEX_msgX()
342 } __packed * msg = ap_msg->message; in ICACRT_msg_to_type6CRT_msgX()
406 } __packed * msg = ap_msg->message; in XCRB_msg_to_type6CPRB_msgX()
410 char *req_data = ap_msg->message + sizeof(struct type6_hdr) + rcblen; in XCRB_msg_to_type6CPRB_msgX()
518 } __packed * msg = ap_msg->message; in xcrb_msg_to_type6_ep11cprb_msgx()
641 struct type86x_reply *msg = reply->message; in convert_type86_ica()
725 struct type86_fmt2_msg *msg = reply->message; in convert_type86_xcrb()
726 char *data = reply->message; in convert_type86_xcrb()
756 struct type86_fmt2_msg *msg = reply->message; in convert_type86_ep11_xcrb()
757 char *data = reply->message; in convert_type86_ep11_xcrb()
[all …]
Dzcrypt_cex2a.h51 unsigned char message[128]; member
61 unsigned char message[256]; member
71 unsigned char message[512]; member
84 unsigned char message[128]; member
97 unsigned char message[256]; member
110 unsigned char message[512]; member
/Linux-v4.19/drivers/mtd/devices/
Dmchp23k256.c69 struct spi_message message; in mchp23k256_write() local
73 spi_message_init(&message); in mchp23k256_write()
80 spi_message_add_tail(&transfer[0], &message); in mchp23k256_write()
84 spi_message_add_tail(&transfer[1], &message); in mchp23k256_write()
88 ret = spi_sync(flash->spi, &message); in mchp23k256_write()
95 if (retlen && message.actual_length > sizeof(command)) in mchp23k256_write()
96 *retlen += message.actual_length - sizeof(command); in mchp23k256_write()
106 struct spi_message message; in mchp23k256_read() local
110 spi_message_init(&message); in mchp23k256_read()
118 spi_message_add_tail(&transfer[0], &message); in mchp23k256_read()
[all …]
/Linux-v4.19/include/trace/events/
Dintel_ish.h12 TP_PROTO(const char *message),
14 TP_ARGS(message),
17 __string(message, message)
21 __assign_str(message, message);
24 TP_printk("%s", __get_str(message))
/Linux-v4.19/drivers/hv/
Dhv_kvp.c200 struct hv_kvp_msg *message = (struct hv_kvp_msg *)msg; in kvp_on_msg() local
204 if (len < sizeof(*message)) in kvp_on_msg()
213 return kvp_handle_handshake(message); in kvp_on_msg()
227 data = &message->body.kvp_enum_data; in kvp_on_msg()
243 error = message->error; in kvp_on_msg()
252 kvp_respond_to_host(message, error); in kvp_on_msg()
373 struct hv_kvp_msg *message; in kvp_send_key() local
385 message = kzalloc(sizeof(*message), GFP_KERNEL); in kvp_send_key()
386 if (!message) in kvp_send_key()
389 message->kvp_hdr.operation = operation; in kvp_send_key()
[all …]
/Linux-v4.19/Documentation/driver-api/soundwire/
Dlocking.rst29 SoundWire message transfer lock. This mutex is part of
30 Bus data structure (sdw_bus). This lock is used to serialize the message
40 1. For every message transfer
44 b. Transfer message (Read/Write) to Slave1 or broadcast message on
58 | | b. Transfer message
72 2. For every message transfer in Prepare operation
76 b. Transfer message (Read/Write) to Slave1 or broadcast message on
97 | | b. Transfer message
/Linux-v4.19/lib/
Dglobtest.c30 char const *message; in test() local
33 message = msg_error; in test()
35 message = msg_ok; in test()
39 printk(message, pat, str, mismatch + 3*match); in test()
134 static char const message[] __initconst = in glob_init() local
154 printk(message, successes, n); in glob_init()
/Linux-v4.19/tools/testing/selftests/futex/include/
Dlogging.h129 #define info(message, vargs...) \ argument
132 fprintf(stderr, "\t%s: "message, INFO, ##vargs); \
135 #define error(message, err, args...) \ argument
139 fprintf(stderr, "\t%s: %s: "message, \
142 fprintf(stderr, "\t%s: "message, ERROR, ##args); \
146 #define fail(message, args...) \ argument
149 fprintf(stderr, "\t%s: "message, FAIL, ##args); \
/Linux-v4.19/drivers/staging/greybus/
Doperation.c215 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()
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()
310 struct gb_message *message, u16 operation_id, in gb_operation_message_init() argument
315 header = message->buffer; in gb_operation_message_init()
317 message->header = header; in gb_operation_message_init()
[all …]
/Linux-v4.19/Documentation/media/uapi/cec/
Dcec-ioc-receive.rst13 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message
37 To receive a CEC message the application has to fill in the
43 is non-zero and no message arrived within ``timeout`` milliseconds, then
46 A received message can be:
48 1. a message received from another CEC device (the ``sequence`` field will
53 To send a CEC message the application has to fill in the struct
98 - Timestamp in ns of when the last byte of the message was transmitted.
103 - Timestamp in ns of when the last byte of the message was received.
108 - The length of the message. For :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>` this is filled in
111 filled in by the driver with the length of the reply message if ``reply`` was set.
[all …]
/Linux-v4.19/drivers/acpi/acpica/
Duterror.c175 const char *message; in acpi_ut_prefixed_namespace_error() local
186 message = "Failure creating"; in acpi_ut_prefixed_namespace_error()
192 message = "Could not resolve"; in acpi_ut_prefixed_namespace_error()
198 message = "Failure resolving"; in acpi_ut_prefixed_namespace_error()
207 acpi_os_printf("%s [%s], %s", message, in acpi_ut_prefixed_namespace_error()
301 const char *message, in acpi_ut_method_error() argument
319 acpi_ns_print_node_pathname(node, message); in acpi_ut_method_error()
/Linux-v4.19/drivers/input/misc/
Dkeyspan_remote.c186 struct keyspan_message message; in keyspan_check_data() local
251 message.system = 0; in keyspan_check_data()
256 message.system = message.system << 1; in keyspan_check_data()
260 message.system = (message.system << 1) + 1; in keyspan_check_data()
272 message.button = 0; in keyspan_check_data()
277 message.button = message.button << 1; in keyspan_check_data()
281 message.button = (message.button << 1) + 1; in keyspan_check_data()
295 message.toggle = 0; in keyspan_check_data()
299 message.toggle = 1; in keyspan_check_data()
321 __func__, message.system, message.button, message.toggle); in keyspan_check_data()
[all …]
/Linux-v4.19/drivers/mailbox/
Dmailbox-test.c44 char *message; member
117 tdev->message = kzalloc(MBOX_MAX_MSG_LEN, GFP_KERNEL); in mbox_test_message_write()
118 if (!tdev->message) in mbox_test_message_write()
121 ret = copy_from_user(tdev->message, userbuf, count); in mbox_test_message_write()
137 data = tdev->message; in mbox_test_message_write()
140 tdev->message, MBOX_MAX_MSG_LEN); in mbox_test_message_write()
148 kfree(tdev->message); in mbox_test_message_write()
280 static void mbox_test_receive_message(struct mbox_client *client, void *message) in mbox_test_receive_message() argument
290 } else if (message) { in mbox_test_receive_message()
292 message, MBOX_MAX_MSG_LEN); in mbox_test_receive_message()
[all …]
/Linux-v4.19/drivers/spi/
Dspi-mpc52xx.c81 struct spi_message *message; /* current message */ member
101 cs = ms->message->spi->chip_select; in mpc52xx_spi_chipsel()
159 ms->message = list_first_entry(&ms->queue, struct spi_message, queue); in mpc52xx_spi_fsmstate_idle()
160 list_del_init(&ms->message->queue); in mpc52xx_spi_fsmstate_idle()
164 spi = ms->message->spi; in mpc52xx_spi_fsmstate_idle()
176 sppr = ((ms->ipb_freq / ms->message->spi->max_speed_hz) + 1) >> 1; in mpc52xx_spi_fsmstate_idle()
193 ms->transfer = container_of(ms->message->transfers.next, in mpc52xx_spi_fsmstate_idle()
236 ms->message->status = -EIO; in mpc52xx_spi_fsmstate_transfer()
237 if (ms->message->complete) in mpc52xx_spi_fsmstate_transfer()
238 ms->message->complete(ms->message->context); in mpc52xx_spi_fsmstate_transfer()
[all …]
/Linux-v4.19/Documentation/infiniband/
Dtag_matching.txt11 message envelopes may match, the pair that includes the earliest posted-send
17 When a message is sent from the sender to the receiver, the communication
20 this is an expected message, otherwise it is called an unexpected message.
27 1. The Eager protocol- the complete message is sent when the send is
35 A fin message needs to be received in order for the buffer to be reused.
40 unexpected message list. The application posts receive buffers through calls
46 pre-posted receive for this arriving message, it is passed to the software and
47 placed in the unexpected message list. Otherwise the match is processed,
52 When a receive-message is posted, the communication library will first check
53 the software unexpected message list for a matching receive. If a match is
[all …]
/Linux-v4.19/Documentation/nfc/
Dnfc-pn544.txt17 write functions behave a bit differently because the message formats
24 HCI messages consist of an eight bit header and the message body. The
25 header contains the message length. Maximum size for an HCI message is
28 and third (LSB) bytes of the message. The maximum FW message length is
/Linux-v4.19/drivers/misc/ibmasm/
Ddot_command.c31 void ibmasm_receive_message(struct service_processor *sp, void *message, int message_size) in ibmasm_receive_message() argument
34 struct dot_command_header *header = (struct dot_command_header *)message; in ibmasm_receive_message()
39 size = get_dot_command_size(message); in ibmasm_receive_message()
48 ibmasm_receive_event(sp, message, size); in ibmasm_receive_message()
51 ibmasm_receive_command_response(sp, message, size); in ibmasm_receive_message()
54 ibmasm_receive_heartbeat(sp, message, size); in ibmasm_receive_message()
/Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/
Dgt215.c31 u32 process, u32 message, u32 data0, u32 data1) in gt215_pmu_send() argument
54 pmu->recv.message = message; in gt215_pmu_send()
67 nvkm_wr32(device, 0x10a1c4, message); in gt215_pmu_send()
91 u32 process, message, data0, data1; in gt215_pmu_recv() local
107 message = nvkm_rd32(device, 0x10a1c4); in gt215_pmu_recv()
118 message == pmu->recv.message) { in gt215_pmu_recv()
135 process, message, data0, data1); in gt215_pmu_recv()
/Linux-v4.19/Documentation/md/
Dmd-cluster.txt54 managed through three locks: "token", "message", and "ack", together
55 with the Lock Value Block (LVB) of one of the "message" lock.
66 other nodes to acknowledge the message before proceeding. Only one
67 message can be processed at a time.
80 RESYNCING message identifies a range of the devices that the
90 array. The slot-number of the device is included in the message.
108 3.2.2 message: The lock resource which carries the data to
111 3.2.3 ack: The resource, acquiring which means the message has been
124 sender get EX on "message"
127 "message":EX
[all …]
/Linux-v4.19/Documentation/connector/
Dconnector.txt10 When the driver receives a special netlink message with the appropriate
38 callback function which will be called when a message with above idx.val
78 Sends message to the specified groups. It can be safely called from
82 struct cn_msg * - message header(with attached data).
85 If non-zero the message will be sent to the
91 and message will be delivered to the group which was
93 If __group is not zero, then message will be delivered
107 msg->seq and msg->ack are used to determine message genealogy. When
108 someone sends a message, they use a locally unique sequence and random
112 The sequence number is incremented with each message sent.
[all …]
/Linux-v4.19/drivers/fpga/
Dice40-spi.c49 struct spi_message message; in ice40_fpga_ops_write_init() local
70 spi_message_init(&message); in ice40_fpga_ops_write_init()
71 spi_message_add_tail(&assert_cs_then_reset_delay, &message); in ice40_fpga_ops_write_init()
72 ret = spi_sync_locked(dev, &message); in ice40_fpga_ops_write_init()
89 spi_message_init(&message); in ice40_fpga_ops_write_init()
90 spi_message_add_tail(&housekeeping_delay_then_release_cs, &message); in ice40_fpga_ops_write_init()
91 ret = spi_sync_locked(dev, &message); in ice40_fpga_ops_write_init()
/Linux-v4.19/drivers/staging/vc04_services/interface/vchi/
Dvchi.h111 void *message; member
266 extern void *vchi_held_msg_ptr( const VCHI_HELD_MSG_T *message );
269 extern int32_t vchi_held_msg_size( const VCHI_HELD_MSG_T *message );
272 extern uint32_t vchi_held_msg_tx_timestamp( const VCHI_HELD_MSG_T *message );
275 extern uint32_t vchi_held_msg_rx_timestamp( const VCHI_HELD_MSG_T *message );
278 extern int32_t vchi_held_msg_release( VCHI_HELD_MSG_T *message );
295 VCHI_HELD_MSG_T *message );
301 VCHI_HELD_MSG_T *message );
/Linux-v4.19/Documentation/networking/
Dnetif-msg.txt5 The design of the network interface message level setting.
9 The design of the debugging message interface was guided and
15 integer variable that controls the debug message level. The message
18 The message level was not precisely defined past level 3, but were
30 Initially this message level variable was uniquely named in each driver
40 Per-interface rather than per-driver message level setting.
64 The set of message levels is named
/Linux-v4.19/Documentation/devicetree/bindings/powerpc/fsl/
Dmpic-msgr.txt4 representation of the message register blocks found in some FSL MPIC
9 - compatible: Specifies the compatibility list for the message register
12 the MPIC containing the message registers.
15 message register block's addressable register space. The type shall be
27 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 block
34 An alias should be created for every message register block. They are not

12345678910>>...29