| /Linux-v4.19/drivers/media/pci/bt8xx/ |
| D | dst_ca.c | 146 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info()
153 state->messages[7], (state->messages[8] << 8) | state->messages[9], in ca_get_app_info()
154 (state->messages[10] << 8) | state->messages[11], __func__, (char *)(&state->messages[12])); in ca_get_app_info()
158 length = state->messages[5]; in ca_get_app_info()
166 put_command_and_length(&state->messages[0], CA_APP_INFO, length); in ca_get_app_info()
169 memmove(&state->messages[4], &state->messages[7], 5); in ca_get_app_info()
172 state->messages[9] = str_length; in ca_get_app_info()
173 memmove(&state->messages[10], &state->messages[12], str_length); in ca_get_app_info()
185 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info()
193 for (i = 0; i < state->messages[0] + 1; i++) { in ca_get_ca_info()
[all …]
|
| /Linux-v4.19/tools/testing/selftests/ipc/ |
| D | msgque.c | 31 struct msg1 *messages; member
66 if (msgsnd(msgque->msq_id, &msgque->messages[i].mtype, in restore_queue()
67 msgque->messages[i].msize, IPC_NOWAIT) != 0) { in restore_queue()
96 if (ret != msgque->messages[cnt].msize) { in check_and_destroy_queue()
98 msgque->messages[cnt].msize); in check_and_destroy_queue()
102 if (message.mtype != msgque->messages[cnt].mtype) { in check_and_destroy_queue()
107 if (memcmp(message.mtext, msgque->messages[cnt].mtext, ret)) { in check_and_destroy_queue()
150 msgque->messages = malloc(sizeof(struct msg1) * ds.msg_qnum); in dump_queue()
151 if (msgque->messages == NULL) { in dump_queue()
161 ret = msgrcv(msgque->msq_id, &msgque->messages[i].mtype, in dump_queue()
[all …]
|
| /Linux-v4.19/net/mac80211/ |
| D | Kconfig | 103 bool "Trace all mac80211 debug messages"
108 collect all debugging messages, independent of
111 The overhead in this option is that all the messages
142 many debugging messages. It should not be selected
143 on production systems as some of the messages are
153 debugging messages for the managed-mode MLME. It
155 of the messages are remotely triggerable.
164 debugging messages for station addition/removal.
176 of the messages are remotely triggerable.
185 very verbose OCB debugging messages. It should not
[all …]
|
| /Linux-v4.19/arch/sh/kernel/cpu/sh2/ |
| D | smp-j2.c | 28 unsigned messages, i; in j2_ipi_interrupt_handler() local
30 do messages = *pmsg; in j2_ipi_interrupt_handler()
31 while (cmpxchg(pmsg, messages, 0) != messages); in j2_ipi_interrupt_handler()
33 if (!messages) return IRQ_NONE; in j2_ipi_interrupt_handler()
36 if (messages & (1U<<i)) in j2_ipi_interrupt_handler()
|
| /Linux-v4.19/sound/usb/line6/ |
| D | driver.c | 557 line6->messages.active = 1; in line6_hwdep_open()
567 line6->messages.active = 0; in line6_hwdep_release()
581 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read()
584 while (kfifo_len(&line6->messages.fifo) == 0) { in line6_hwdep_read()
585 mutex_unlock(&line6->messages.read_lock); in line6_hwdep_read()
588 line6->messages.wait_queue, in line6_hwdep_read()
589 kfifo_len(&line6->messages.fifo) != 0); in line6_hwdep_read()
593 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read()
597 if (kfifo_peek_len(&line6->messages.fifo) > count) { in line6_hwdep_read()
601 rv = kfifo_to_user(&line6->messages.fifo, buf, count, &out_count); in line6_hwdep_read()
[all …]
|
| /Linux-v4.19/Documentation/networking/ |
| D | netif-msg.txt | 20 to shed the more verbose level messages as they matured.
21 0 Minimal messages, only essential information on fatal errors.
22 1 Standard messages, initialization status. No run-time messages
23 2 Special media selection messages, generally timer-driver.
24 3 Interface starts and stops, including normal status messages
25 4 Tx and Rx frame error messages, and abnormal driver operation
41 More selective control over the type of messages emitted.
|
| D | kcm.txt | 6 can efficiently send and receive application protocol messages over TCP using
42 The multiplexor provides the message steering. In the transmit path, messages
44 Similarly, in the receive path, messages are constructed on each TCP socket
45 (Psock) and complete messages are steered to a KCM socket.
52 messages on receive as well as other connection specific information for KCM.
60 can be used to send and receive messages from the KCM socket.
71 format that typically includes a header which frames the messages. The length
99 socket. The BPF program may also enforce a maximum messages size and report an
102 A timeout may be set for assembling messages on a receive socket. The timeout
189 When receive is disabled, any pending messages in the socket's
[all …]
|
| D | batman-adv.rst | 136 All error messages, warnings and information messages are sent to the kernel
139 the files ``/var/log/kern.log`` or ``/var/log/syslog``. All batman-adv messages
140 are prefixed with "batman-adv:" So to see just these messages try::
145 see more detail debug messages. This must be enabled when compiling the
150 Those additional debug messages can be accessed using a special file in
163 - Enable messages related to routing / flooding / broadcasting
165 - Enable messages related to route added / changed / deleted
167 - Enable messages related to translation table operations
169 - Enable messages related to bridge loop avoidance
171 - Enable messages related to DAT, ARP snooping and parsing
[all …]
|
| D | tls.txt | 107 Send TLS control messages
110 Other than application data, TLS has control messages such as alert
111 messages (record type 21) and handshake messages (record type 22), etc.
112 These messages can be sent over the socket by providing the TLS record type
146 Receiving TLS control messages
149 TLS control messages are passed in the userspace buffer, with message
151 returned if a control message is received. Data messages may be
195 messages are not supported:
|
| /Linux-v4.19/Documentation/isdn/ |
| D | README.avmb1 | 97 recvqueuelen: number of messages on receive queue
104 recvctlmsg: capi messages received without DATA_B3_IND
106 sentctlmsg: capi messages sent without DATA_B3_REQ
115 nrecvdropmsg: capi messages dropped (messages in recvqueue in close)
116 nrecvctlmsg: capi messages received without DATA_B3_IND
118 nsentctlmsg: capi messages sent without DATA_B3_REQ
124 /proc/capi/capidrv: statistics of capidrv.o (capi messages)
126 nrecvctlmsg: capi messages received without DATA_B3_IND
128 nsentctlmsg: capi messages sent without DATA_B3_REQ
142 nrecvctlmsg: capi messages received without DATA_B3_IND
[all …]
|
| /Linux-v4.19/sound/firewire/motu/ |
| D | amdtp-motu-trace.h | 76 __dynamic_array(u64, messages, data_blocks)
82 copy_message(__get_dynamic_array(messages), buffer, data_blocks, s->data_block_quadlets);
89 __print_array(__get_dynamic_array(messages), __entry->data_blocks, 8)
100 __dynamic_array(u64, messages, data_blocks)
106 copy_message(__get_dynamic_array(messages), buffer, data_blocks, s->data_block_quadlets);
113 __print_array(__get_dynamic_array(messages), __entry->data_blocks, 8)
|
| /Linux-v4.19/drivers/hwtracing/stm/ |
| D | Kconfig | 26 messages to trace hosts over STM devices.
28 If you want to send kernel console messages over STM devices,
35 heartbeat messages to trace hosts over STM devices. It is
39 If you want to send heartbeat messages over STM devices,
50 If you want to send kernel Ftrace messages over STM devices,
|
| /Linux-v4.19/Documentation/media/uapi/cec/ |
| D | cec-ioc-g-mode.rst | 39 used to initiate messages, i.e. it commands other CEC devices. The
40 follower is the filehandle that receives messages sent to the CEC
57 The CEC framework will process core messages unless requested otherwise
59 case, the CEC framework will pass on most core messages without
60 processing them and the follower will have to implement those messages.
61 There are some messages that the core will always process, regardless of
85 - This is not an initiator, i.e. it cannot transmit CEC messages or
92 it can transmit CEC messages and make changes to the CEC adapter,
99 only one that can transmit CEC messages and make changes to the
127 - This is a follower and it will receive CEC messages unless there
[all …]
|
| /Linux-v4.19/Documentation/acpi/ |
| D | debug.txt | 11 option is turned off, the debug messages are not even built into the
17 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages
21 the debug messages.
70 The "debug_level" is a mask that selects different types of messages, e.g.,
71 those related to initialization, method execution, informational messages, etc.
134 Enable PCI and PCI interrupt routing debug messages:
138 Enable all ACPI hardware-related messages:
142 Enable all ACPI_DB_INFO messages after boot:
|
| /Linux-v4.19/fs/ntfs/ |
| D | Kconfig | 35 performed by the driver as well as additional debugging messages to
36 be written to the system log. Note that debugging messages are
40 you can enable debugging messages by doing (as root):
42 Replacing the "1" with "0" would disable debug messages.
44 If you leave debugging messages disabled, this results in little
45 overhead, but enabling debug messages results in very significant
49 debugging messages while the misbehaviour was occurring.
|
| /Linux-v4.19/drivers/pnp/ |
| D | Kconfig | 25 bool "PNP debugging messages"
29 messages if needed. The messages can be enabled at boot-time with
33 the messages to even be built into the kernel.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | dev-kmsg | 8 Injecting messages:
19 is not possible to inject messages from userspace with the
21 the messages can always be reliably determined.
37 there are never partial messages received by read().
39 In case messages get overwritten in the circular buffer while
46 messages, in case the buffer gets overwritten. And they allow
96 unrelated messages, but merging the lines in the output
98 logic is used internally when messages are printed to the
|
| D | sysfs-bus-pci-devices-aer_stats | 100 collectors) that are AER capable. These indicate the number of error messages as
102 (internally) the ERR_* messages for errors seen by the internal rootport PCI
104 messages on the PCI hierarchy originating at that root port.
110 Description: Total number of ERR_COR messages reported to rootport.
116 Description: Total number of ERR_FATAL messages reported to rootport.
122 Description: Total number of ERR_NONFATAL messages reported to rootport.
|
| /Linux-v4.19/arch/arm/ |
| D | Kconfig.debug | 79 bool "Verbose user fault messages"
114 bool "Kernel low-level debugging messages via Alpine UART0"
216 bool "Kernel low-level debugging messages via BCM KONA UART"
248 messages to appear over the UART, select this option.
251 bool "Kernel low-level debugging messages via UART1"
258 bool "Kernel low-level debugging messages via UART2"
297 bool "Kernel low-level debugging messages via footbridge serial port"
304 bool "Kernel low-level debugging messages via Digicolor UA0"
311 bool "Kernel low-level debugging messages via ep93xx UART"
319 bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"
[all …]
|
| /Linux-v4.19/net/dccp/ccids/ |
| D | Kconfig | 4 bool "CCID-2 debugging messages"
6 Enable CCID-2 specific debugging messages.
39 bool "CCID-3 debugging messages"
42 Enable CCID-3 specific debugging messages.
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | perf.txt | 22 verbose - general debug messages
23 ordered-events - ordered events object debug messages
24 data-convert - data convert command debug messages
|
| /Linux-v4.19/security/integrity/ |
| D | Kconfig | 61 controls the level of integrity auditing messages.
62 0 - basic integrity auditing messages (default)
63 1 - additional integrity auditing messages
65 Additional informational integrity auditing messages would
|
| /Linux-v4.19/Documentation/nfc/ |
| D | nfc-pn544.txt | 24 HCI messages consist of an eight bit header and the message body. The
26 33. In HCI mode sent messages are tested for a correct
27 checksum. Firmware update messages have the length in the second (MSB)
|
| /Linux-v4.19/Documentation/misc-devices/ |
| D | ibmvmc.rst | 49 The set of HMC to hypervisor messages supported by the management
76 sending/receiving any of the protocol messages.
78 This driver also utilizes Transport Event CRQs. CRQ messages are sent
81 Two new classes of CRQ messages are introduced for the VMC device. VMC
82 Administrative messages are used for each partition using the VMC to
83 communicate capabilities to their partner. HMC Interface messages are used
84 for the actual flow of HMC messages between the management partition and
85 the hypervisor. As most HMC messages far exceed the size of a CRQ buffer,
153 hypervisor receives this information, it sends Add Buffer messages to the
177 exchange HMC messages via the Signal VMC message and RDMA operations. When
[all …]
|
| /Linux-v4.19/drivers/atm/ |
| D | Kconfig | 222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
226 messages is controlled by a bitmap. This may be specified as a
230 When active, these messages can have a significant impact on the
257 bool "Enable debugging messages"
260 Somewhat useful debugging messages are available. The choice of
261 messages is controlled by a bitmap. This may be specified as a
268 When active, these messages can have a significant impact on the
281 bool "Enable debugging messages"
284 Somewhat useful debugging messages are available. The choice of
[all …]
|
